Tiny animated walkers above your taskbar. Click any one to open a chat popover wired straight to a real provider CLI — Claude, Gemini, Codex, Copilot & more. Spawn extras. Share a channel. Watch them pass work between each other.
Claude·Bruce·app session
Ready
/channel join dev
#dev — Jazz is here too.
/tell Jazz review the auth module & flag risks
gemini
Gemini·Jazz·app session
Ready
auth/session.py — sending notes back.
claude
Every feature lives on your machine. The walkers are dumb-cute on the outside, but each one is a real CLI session under the hood.
Lives in the Windows notification area. Open chat from the tray, never break your flow.
One primary walker by default. Spawn more from the tray or run /spawn.
Walkers join the same room. Use /tell or auto-collab to pass work between providers.
Markdown and syntax-highlighted code right in the popover.
Or hand off to Cursor, VS Code, or Windows Terminal — your call.
Peach. Midnight. Cloud. Moss. Pick a vibe, change it whenever.
LilWin talks to the same provider CLIs you'd use in a normal terminal. Install the CLIs you need, confirm they work in PowerShell or Command Prompt, and make sure they're on your PATH. Without that, the app cannot reach those providers.
Bruce on Claude. Jazz on Gemini. Human on Codex. They share a channel and a workspace — pass tasks between them like teammates.
No accounts, no cloud, no telemetry. The walker is a thin native shell over the same CLIs you'd use in PowerShell.
Clone & pip install, or grab the prebuilt zip. Tray icon shows up.
Make sure claude, gemini, codex etc. are on your PATH.
Right-click the tray icon, pick a provider, name your buddy.
The walker opens a tiny popover. Markdown, code, the whole thing.
LilWin is a front end. Whatever provider you already use in a terminal, you can wire to a walker — and have walkers pass work between them.
A desktop pet that actually earns its keep.
Tray-resident PyQt6 app. Chat view uses QtWebEngine for rich rendering. Runs on Windows.
A standalone Windows build may be available via the project's build script — check the README for exact paths and filenames.
Already have it? git pull && pip install -r requirements.txt
If you hit something this list doesn't cover, the issues page is the right spot.
/tell or auto-collab to pass work between them.%LOCALAPPDATA%\lilwin\. Either way, it stays on your machine.One-time download. No account. Free forever, MIT-licensed. The walkers are waiting.