Docs13 of 14
How it fits together
A window, a main process, and one adapter per vendor. The window never touches a vendor CLI.
The shape
- The window (
src/ui) — projects, chats, the permission bar. React. It speaks typed IPC and nothing else. - Electron main (
electron/) — owns the adapters, prompts, credentials and the working directory. It journals queues, schedules and goals, and recovers dispatched work after a restart. - Adapters — Grok, Claude and Cursor speak ACP over stdio to their own CLI; Codex adds an App Server; custom bots are plain HTTP. Each vendor runs as its own process under the login you already hold.
- Credential store — OS-encrypted. Terminal and managed git worktree — the chat's execution directory.
- A provider capability registry drives the controls, so the window never implies a vendor supports something it does not.
The README carries the diagram and the layout of the tree: How it fits together.
Run it from source
npm install
npm run devnpm run dev opens the Go7 Workhorse window with isolated development data and session-only credentials. npm run dist:mac and npm run dist:win build the installers; release builds need the signing and notarization secrets. npm test runs the adapter and shell suite. Everything is MIT.