all your coding agents, living on the board.
A personal AI on machines you own — any agent, loops that run overnight, boards, memory, and git control. Client/server split, always-on, open source end to end.
- Use the major coding agents. Frontier labs are investing heavily in coding agents and benchmarks. Jaz should reuse that work, not reinvent it.
- Bring your existing plans. Sign in with the ChatGPT, Claude, Kimi, Grok, Google, or Meta account you already have, with API keys and open-source agents alongside them.
- Unified memory that you control and can export.
- Connect core apps. Telegram, WhatsApp, Gmail, Calendar, and Slack should plug into the same owned context.
- Open source.
Ultrathink
jaz-ultrathink.mov
Familiar chat UI
Interactive visualisations
Board with live artifacts
Customize
Track usage
Connect your coding agents and reuse your subscriptions
Connect your apps (Slack, Gmail, Google Calendar, WhatsApp, Telegram, Deployink)
Side panel
side-panel-switch.mp4
Grab the latest desktop build from Releases, or run it from source.
Jaz runs seven coding agents over ACP, and you pick one per thread:
| Agent | Provider | Sign in with |
|---|---|---|
| Codex | OpenAI | ChatGPT plan, or OpenAI or OpenRouter API key |
| Claude Code | Anthropic | Claude Pro/Max plan, or Anthropic API key |
| Kimi Code | Moonshot AI | kimi.ai account |
| Antigravity | Google account | |
| Grok | xAI | Grok account, or xAI API key |
| Muse Code | Meta | Meta account, or Meta API key |
| OpenCode | Open source | OpenRouter or OpenAI API key |
- Pick the agent per thread — any agent in the table above.
- Loops — scheduled prompts that run overnight.
- Boards — multi-window dashboards of live artifacts.
- Memory — survives the thread.
- Ship from the thread — built-in git control.
- MCP servers & skills, token-usage tracking, and an always-on mode for 24/7 work.
Client/server split — the backend owns everything, clients are control surfaces. By default you run both together on your own machine; the backend can also live on a remote server you connect to over HTTP.
- Backend (
backend/, Go) — the always-on core. Runs agent sessions, loops, memory, and tools; owns your credentials and workspaces. REST + SSE; drives agents over ACP and tools over MCP. - Desktop (
frontend/, Electron + React) — the control surface. Runs the backend locally by default, or connects to a remote one over HTTP with a per-device token.
Running the backend on a server: see docs/remote-backend.md.
Requirements: Go 1.26, Bun 1.3.5.
Backend:
cd backend
OPENROUTER_API_KEY=... go run ./cmd/jaz # serves on :5299
go test ./...Desktop app:
cd frontend
bun install
bun run dev # JAZ_API_URL=https://host to target a remote backend
bun run lint && bun run typecheck
bun run build # package the desktop appCutting a release: docs/RELEASE.md.
Augustinas Malinauskas — @amgauge · amguage.com