Jaz

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.

Guiding Principles

• 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 Pro plans. Carry Claude and Codex plans forward, with API-key support 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.

Download

Examples

Ultrathink

https://github.com/user-attachments/assets/16062e29-f4ae-4484-87ca-3a5977fac88b

Familiar chat UI

Interactive visualisations

Board with live artifacts

Customize

Track usage

Connect your coding agent and reuse subscription (Codex, Claude Code, Open Code, Antigravity, Kimi)

Connect your apps (Slack, Gmail, Google Calendar, WhatsApp, Telegram, Deployink)

Side panel

https://github.com/user-attachments/assets/de550dc1-75cc-43bb-aca0-f34c99573d47

Get Started

Grab the latest desktop build from Releases, or run it from source.

Jaz ships with three coding agents, and you pick one per thread:

Agent	How it connects
Codex	Sign in with your ChatGPT Pro plan to use its discounted tokens, or an OpenAI API key
Claude	Sign in with your Claude Pro/Max plan to use its discounted tokens, or an Anthropic API key
OpenCode	Connects to OpenAI, OpenRouter, or Anthropic by API token

You can also connect OpenRouter, OpenAI, or Anthropic directly and pay per token.

Features

• Pick the agent per thread — Codex, Claude, or OpenCode.
• 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.

Architecture

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.

Development

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 app

Cutting a release: docs/RELEASE.md.

Author

Augustinas Malinauskas — @amgauge · amguage.com

License

Apache 2.0.