About
Platforms and limits
Built and tested on macOS. Linux and Windows work with a few caveats. Some limits are by design.
Platform support
| Platform | Status | Notes |
|---|---|---|
| macOS | Primary | Built and tested here |
| Linux | Works | Chromium auto-install via Playwright is sometimes flaky in headless sandboxes; run playwright install-deps chromium once on a fresh distro |
| Windows, native | Works through Git Bash (Claude Code) | Git Bash supplies the POSIX environment the hooks, server, and skills expect. Needs bun and git on PATH. Codex on native Windows is unverified |
| Windows, WSL2 | Works | Closest to a Linux production target; run everything inside the distro |
Native Windows rough edges: MSYS path-mangling can bite commands that pass colon-paths (MSYS_NO_PATHCONV=1 is the escape hatch); the OS sandbox is unavailable, so that block is omitted; a few pack-gated skills assume tools Git Bash lacks (serpapi pipes through jq). The core loop of tasks, compile, memory, briefings, worktrees, and dashboard runs natively.
Platform-specific fixes and install notes are welcome as pull requests.
Known limitations
- The host must open in the home for the static identity to load. Outside, you get nothing, silently. See the one convention.
- A host sandbox can block
.claude/skills/writes duringconfigure-skills. Pre-create the directory from a normal terminal if it hits the wall. - Browser launch can fail in sandboxed subprocesses on macOS. Install Playwright's Chromium once from a normal terminal so it caches.
- No live GUI. The dashboard is a static snapshot regenerated on sync; between syncs it can drift from task frontmatter.
- Single-user. Team isolation is not built in; use separate homes per person, or a shared repo where everyone gets the same identity.
- No proactive Kevin. You start every session. External schedulers can run a headless host, but those calls bill the API, not your plan. See The host does the thinking.