AgentDock unifies provider management, model routing, skills, MCP servers, instructions, hooks, and subagents across Windows and WSL. Stop juggling configurations between environments—manage everything from one tray app.
-
Engine —
engine/, agit subtreeof magpie (MIT), built-tags noguiand run as a sidecar (serve --web). It owns the gateway (127.0.0.1:3425), routing, the Library and every agent's config. AgentDock's changes are listed inengine/AGENTDOCK_PATCHES.md. -
Shell —
shell/, a minimal Tauri 2 app extracted from cc-switch (MIT): tray, single instance, autostart, window state, and the engine's lifecycle (Job Object, restart on crash). Its window shows the engine's own UI.
On the Environments page:
- Side-by-side environment view — this computer and each WSL distro visible together; probe gateway connectivity from inside each running distro (stopped distros never started just to check)
- Per-distro gateway control — enable/disable each distro individually
- Cross-environment sync — copy one agent's setup (connection, model, Library bindings) to the same agent in other environments with preview
.wslconfigautomation — switch to mirrored networking (backed up, restorable), thenwsl --shutdownafter confirmation; no admin rights required- Provider import — bring in providers from CC Switch or from magpie instances running in distros
- Conflict warnings — alerts when another magpie instance would overwrite shared agent files
Hooks and subagents from the Library work in WSL too:
- Windows drive paths automatically convert to
/mnt/<drive>/… - Windows-only hooks (native programs) gracefully refuse execution in distro context with clear error messages
- Standard mode:
%APPDATA%\AgentDock\(engine data in…\magpie, logs in…\logs) - Portable mode: Place a
.portablefile next to the executable; data stores in<exe_dir>\data\ - WSL configs (
~/.config/magpie) remain untouched
Download AgentDock_1.0.0_x64_en-US.exe from Releases, run the installer, and launch from Start Menu or Desktop shortcut.
- Download
AgentDock_1.0.0_x64_portable.zipfrom Releases - Extract to any folder
- Data is stored in
data/subfolder (portable between systems)
- Go 1.23+ (per
engine/go.mod) - Rust 1.95+ (stable)
- Node.js 20+ with pnpm
- Visual Studio Build Tools (for Rust linking)
# Build engine (Go binary)
powershell -ExecutionPolicy Bypass -File scripts\build-engine.ps1
# Build shell (Tauri app)
cd shell
pnpm install
pnpm tauri buildOutput locations:
- NSIS installer:
shell/src-tauri/target/release/bundle/nsis/ - Portable build: run
scripts/make-portable.ps1(creates zip with.portablemarker)
China users: build-engine.ps1 automatically uses goproxy.cn when GOPROXY is unset.
# Engine tests
cd engine
go vet ./...
go test -tags nogui ./...
# Shell tests
cd shell/src-tauri
cargo clippy -- -D warnings
cargo fmt --check# Terminal 1: Engine
cd engine
go run -tags nogui . serve --web
# Terminal 2: Shell
cd shell
pnpm tauri dev- Fork the repository
- Create a feature branch:
git checkout -b feature/your-feature - Commit changes:
git commit -m 'Add some feature' - Push to branch:
git push origin feature/your-feature - Open a Pull Request
Follow the existing code style and ensure tests pass before submitting.
- AgentDock: MIT License (see
LICENSE) - magpie (engine subtree): MIT License (
LICENSES/magpie-MIT.txt) - cc-switch (shell base): MIT License (
LICENSES/cc-switch-MIT.txt)
Built on top of:
Special thanks to the open-source community for making cross-platform development accessible.