Skip to content

About

A floating dock for Windows 11 with a Rust/Tauri core and a Svelte frontend.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Stem

Stem

A floating dock for Windows 11.

A rounded panel on an edge of the screen shows your pinned and running apps, one icon per app. Icons grow as the pointer passes over them, dots mark running apps, and an icon bounces while its app starts. Stem is written in Rust with Tauri 2 and Svelte 5.

The dock in the dark theme with the pointer over Notepad: the icons next to it grow and a tooltip above it names the app

license: AGPL-3.0

Rust Tauri Svelte TypeScript Windows 11

Magnification · running dots · drag to pin · auto-hide · any screen edge · multi-monitor · theme sync

What is Stem? · Features · In action · How it works · Install · Build from source · Development · Documentation · License

What is Stem?

Stem is a dock for Windows 11. It is a floating, centred, rounded panel on the bottom edge of the screen by default, or on the left, right or top edge. It shows Start, your pinned apps, the other running apps and the Recycle Bin, and the windows of one app share one icon. Stem can hide the stock taskbar while it runs, or work beside it.

Stem runs on Windows 11 only. Windows 10, macOS and Linux are not supported. It does not replace the notification area: the tray icons and the input indicators stay on the stock taskbar.

Features

Apps. Pinned and running apps share the dock, grouped per app: a pinned app and its windows are one icon, with the app's real name and icon. Packaged (Store) apps are recognised as well as classic ones. Drag a pinned icon to reorder it, or drop an .exe or a shortcut from File Explorer onto the dock to pin it. Hide from Stem removes a running app that is not pinned from the dock until you show it again from the settings window.

Clicks, menus and the wheel. A click starts an app, brings its window to the front, minimises it or cycles through its windows. Whether a click on the app in front minimises it is a setting. A right-click opens a native Windows menu: the app's windows, New window, Pin to Stem or Unpin from Stem, Hide from Stem, Close all windows, settings and quit. The mouse wheel over an app can cycle through its windows (off by default).

Look. Icons grow near the pointer, tooltips name the app, and an icon bounces while its app starts. Up to three dots per app show its open windows, dimmed while all of them are minimised. An app that asks for attention gets an orange pill in place of its dots and wiggles until you switch to it. Three themes (Standard, Solid and Minimal) and a dock.css of your own set how the panel is drawn. The dock follows the Windows accent colour, light and dark mode, transparency effects and contrast themes, with a light or dark override. The settings window offers one backdrop, which the page draws itself (css, named Blur (built in)). acrylic or mica, written into the settings file, turns on an experimental native backdrop behind the primary dock's panel on Windows 11 22H2 or later.

Fixed items. Start and the Recycle Bin are on by default. Task View, Show Desktop, Quick Settings, Notification Center, volume, battery and clock items can be turned on. The Recycle Bin item shows whether the bin is full, opens or empties it, and moves files dropped on it to the bin. The mouse wheel over the volume item turns the volume up or down.

Auto-hide and fullscreen. The dock can hide always, or only while a window overlaps it. Move the pointer to the screen edge the dock sits on to bring it back. Fullscreen apps (games, videos, presentations) hide the dock of their monitor. By default, clicks outside the panel go to the desktop and the windows behind it.

Edges and monitors. The dock sits on the bottom, left, right or top edge. While auto-hide is off, it can reserve its band of the screen, as the stock taskbar does, so maximised windows stop short of it. With many items, it draws its icons smaller until it fits its edge. You can have one dock per monitor, following monitors as they are plugged in and out, with an option to list only each monitor's windows on its dock. A change of display scale applies without a restart. By default the dock lists only the windows on the current virtual desktop.

Taskbar, keyboard and tray. Stem can hide the stock taskbar while it runs, and puts it back on quit. It can start when you sign in. By default, Ctrl+Alt+D shows or hides the dock from any app, and Ctrl+Alt+Shift+D moves the keyboard into it. A left click on the tray icon shows or hides the dock, and the tray menu opens the settings, restarts Stem or quits it. Starting Stem again shows the running dock. After a crash, the next start says so once and offers to open the log folder.

Settings. The settings window applies every change at once. It lists the pinned apps and the hidden apps, has Reset to defaults, and ends with an About section that shows the version and the paths of the settings and log files and opens their folders.

Every setting is described in the user guide, and every key of the settings file, with its type, range and default, in the settings reference.

In action

The captures below, like the one at the top, are mock-mode renders from the project's Playwright suite: demo apps with placeholder letter icons, not a real desktop. The one at the top shows the dark theme with the pointer over Notepad: the icons near it grow and a tooltip names the app.

The dock in the light theme at rest: Start, five pinned apps, two other running apps and the Recycle Bin, with thin separators between the groups and dots under the running apps
The light theme at rest: Start, the pinned apps, the other running apps and the Recycle Bin.
The settings window in the dark theme, at the top of its Appearance section: icon size, magnification, maximum scale, range, theme and panel opacity
The settings window, where every change applies at once.

How it works

flowchart TB
    subgraph page["Svelte 5 page in WebView2 · src/"]
        DOCK["dock.html<br>one per dock window"]
        SET["settings.html"]
    end
    APP["Tauri app · src-tauri<br>windows · tray · menus · shortcuts"]
    SVC["stem-service<br>engine thread · identity · settings file"]
    CORE["stem-core<br>DockEngine · model · rules"]
    PLAT["stem-platform<br>Platform trait · Win32 · mock"]
    WIN[("Windows<br>WinEvents · shell hook · Win32")]

    page -->|"commands: primary_click · get_icon · update_settings · set_dock_*"| APP
    APP -->|"events: dock://state · dock://settings · dock://theme · dock://monitors"| page
    APP -->|"DockService calls"| SVC
    SVC -->|"ServiceEvent: State · Settings · Theme · Monitors · Bounce"| APP
    SVC -->|"EngineInput"| CORE
    CORE -->|"DockState · ItemAction"| SVC
    SVC -->|"launch · window_action · identify_*"| PLAT
    PLAT -->|"PlatformEvent"| SVC
    APP -->|"window styles · hit region · AppBar"| PLAT
    PLAT <--> WIN
Loading

Rust decides and the page renders. stem-core holds the pure model and the rules: what a click does, and how items are ordered and grouped. It never calls the OS. stem-platform is the only code that calls Win32 and the only place with unsafe code, and its mock implements the same Platform trait on any host. stem-service runs the engine on its own thread, passes it the platform's events, resolves app names and icons, and saves the settings file. The Tauri app in src-tauri creates the windows, the tray and the menus, and passes commands and events between the service and the Svelte page. The page draws the DockState snapshot it receives and reports what the user did. docs/architecture/ describes every part, and docs/ipc/ lists every command and event.

Install

Every run of the CI workflow on GitHub builds the installer. A pushed v<version> tag also builds it and attaches it to a draft GitHub release, which is published by hand (docs/RELEASING.md). To take the installer from CI:

  1. Open the repository's Actions tab, then the CI workflow, and pick the latest run on master with a green tick.
  2. Download the stem-installer artifact (GitHub asks you to sign in for artifacts) and unzip it.
  3. Run the Stem_<version>_x64-setup.exe inside, such as Stem_0.1.0_x64-setup.exe.

Neither the installer nor stem.exe is code-signed, so SmartScreen may stop the installer: choose More info → Run anyway. Where Smart App Control is on, it can block the unsigned files with no way to run them. Stem has no automatic update.

The installer is per-user: it needs no administrator rights and installs to %LOCALAPPDATA%\Stem. Windows 11 already has the WebView2 runtime Stem needs.

Where Stem keeps its files:

What Where
Settings %APPDATA%\dev.davidcristian.stem\settings.json
Your styles %APPDATA%\dev.davidcristian.stem\dock.css
Log %LOCALAPPDATA%\dev.davidcristian.stem\logs\stem.log
Icon cache %LOCALAPPDATA%\dev.davidcristian.stem\icons\
Taskbar and crash notes %LOCALAPPDATA%\dev.davidcristian.stem\ (taskbar.json, crash.json, run.json)

Quitting. Right-click the tray icon → Quit, or right-click the dock → Quit Stem.

Hiding the taskbar. Hide the Windows taskbar (Settings → System) turns on Windows' own Automatically hide the taskbar while Stem runs. The taskbar is not removed: it still slides up from the bottom edge beside the dock, so the tray and the clock stay reachable. Stem stores your own setting in taskbar.json and puts it back when you turn the option off or quit Stem. After a crash, the taskbar stays hidden until Stem starts again, which puts it back (or keeps it hidden while the option is still on). The user guide has the details.

Uninstalling. Quit Stem first (tray → Quit), so it puts your taskbar setting back. Then remove Stem from Windows Settings → Apps → Installed apps. The uninstaller also removes Stem's startup entry. Its Delete the application data box, unticked by default, deletes both dev.davidcristian.stem folders: the settings, your dock.css, the log, the icon cache, the notes and WebView2's data. Leave it unticked to keep your settings.

Build from source

You need Windows 11 with:

  • Rust through rustup. rust-toolchain.toml sets the toolchain to an exact version; rustup toolchain install, run in the repository, installs it if it is missing.
  • Node.js 22 or newer, and pnpm at the version ui/package.json names (corepack enable provides it with Node 22 and 24).
  • The Tauri prerequisites for Windows: the Microsoft C++ Build Tools with the Windows SDK, and the WebView2 runtime (part of Windows 11).

Then:

cd ui
pnpm install
pnpm tauri dev

pnpm tauri runs the Tauri CLI at the version ui/package.json names. pnpm tauri build builds the release stem.exe and the NSIS installer under target/release/.

Development

Read AGENTS.md first: it holds the rules for every change, by people and agents alike. Most of the code (everything except the final binary) can be developed and tested on Linux: stem-core, the mock platform and stem-service run their tests there, a lint for the x86_64-pc-windows-msvc target type-checks the Windows code, and the page runs in a browser against MockBackend. The development hosts page explains how.

Command (pnpm in ui/) What it does
pnpm dev Serves the page alone at http://localhost:1420/dock.html and http://localhost:1420/settings.html, against the mock backend, in any browser
pnpm tauri dev Builds and starts the app in debug, with the page served by pnpm dev
set STEM_PLATFORM=mock && pnpm tauri dev Starts the app on the mock platform, which shows demo data and saves nothing, so your real windows and settings are untouched (Command Prompt; in PowerShell, set $env:STEM_PLATFORM = 'mock' first)
scripts/check-all.sh The verification ladder on Linux or macOS: formatting, lints, tests, the generated TypeScript bindings and settings reference, the Windows-target lint, frontend checks and the Playwright suite
scripts/check-all.ps1 The same ladder on Windows, then pnpm tauri build --debug
pnpm e2e:screenshots The Playwright suite in mock mode: screenshots in ui/e2e/output/ and the idle checks of the dock page

Documentation

The FAQ in the user guide answers common questions about the dock.

Where What
docs/user-guide/ Every part of the settings window and how the dock behaves
docs/SETTINGS.md Every key of settings.json with its type, range and default, generated from the source
docs/THEMING.md The theme presets and the variables and selectors a dock.css can use
docs/architecture/ Layers, data flow, threads, app identity, icons, the dock window, settings, error handling, performance budgets and security
docs/ipc/ The contract between Rust and the page: every command and event
docs/PLAN.md The milestones and the non-goals
docs/RELEASING.md How a release is built, and what the installer and the uninstaller do
docs/code-signing/ The options for signing stem.exe and the installer, and what SmartScreen shows
docs/adr/ The architecture decisions, one record each
docs/research/backdrop/ Acrylic or Mica behind the dock panel: the options and the prototype
docs/research/jump-lists/ Jump lists and recent documents in the dock's menu
docs/research/notification-area/ What replacing or mirroring the notification area would take, and why Stem does not
docs/research/thumbnail-probe/ The probe that tests DWM window thumbnails before window previews are built
AGENTS.md and docs/development/ The rules every change in this repository follows, and the detail behind them

License

Stem is licensed under the GNU Affero General Public License v3.0.

About

A floating dock for Windows 11 with a Rust/Tauri core and a Svelte frontend.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages