Your code never leaves your machine.

Start with private desktop boards, local repositories and credentials in the operating system keyring. Turn on shared workspaces only when the project actually becomes a team effort.

Choose your download

Watch it work

Works fully offline
Credentials in the OS keyring
Sharing is opt-in, per workspace

Offline: by default, no account needed
OS keyring: for every credential
Opt-in: sync, per workspace

LOCAL, THEN SHARED

Private on this machine. Shared when you decide.

Configure agents and credentials locally, keep the command policy enforced on your device, then promote a workspace online and invite the people who need it.

01 / 04

Use the right agent for every job.

Bring your preferred coding agents into one operating layer and route work by column, role or tag.

Six supported agent families
Per-task model choice
Board-level routing rules

PaymentsAcme workspace

Search tasks, agents, tags…⌘K

New task LR

Payments

Offline · 2 repositories

Filter by title, code or description… Type: all Priority: all Agent: all

Backlog

Manual

Add invoice export

TP-171 Medium

frontend

No agent

Migrate webhook retries

TP-168 Low

backend

No agent

In progress

Claude Code, Codex

Harden command approvals

TP-142 Urgent

securitybackend

COCodex

Refactor billing service

TP-151 High

backend

CCClaude Code

Needs input

Manual

Choose retry policy

TP-166 High

backend

CCClaude Code

Review

Codex

Add repository tests

TP-158 Medium

tests

GRGrok

Improve empty states

TP-163 Low

frontend

OCIn queue

Queue #2

CodexClaude CodeGrokOpenCodeOpenAI-compatible

Local execution, optional coordination

Coding agents need your source code, your commands and your credentials. A local-first workflow keeps those surfaces on the developer machine instead of forcing every project into a hosted runner you do not control.

cadre.rocks runs the supported coding CLIs on your computer, stores secrets in the OS keyring, and works with no account at all. Online workspaces are additive: they sync the board activity you choose while repositories, worktrees and execution stay exactly where they are.

WHAT STAYS LOCAL

Repositories stay put

Agents work against the source and worktrees already on your disk. Nothing is uploaded to run a task.

Local SQLite for offline boards
Worktrees created inside your own repository folders
Repository paths are never synced, even on online boards

Credentials use the OS keyring

Keys live in Keychain, Credential Manager or Secret Service — not in config files, logs or browser storage.

Secrets redacted before logging, not just before display
Scoped per agent, per column
Remove the credential and the column falls back to the CLI

Sharing is a choice

Begin with a private board. Promote a workspace online when you need sync, roles and invitations.

Cross-device board sync on Pro and Team
Owner, admin and dev roles
Only workspace activity syncs — never your code

HOW IT RUNS

From a defined task to an approved result.

01
Create a local board
Start organizing tasks offline, with no account and no online workspace.
02
Connect local repositories
Point the board at the projects and coding CLIs already on the machine.
03
Run and review locally
Keep execution, command policy and human approval inside the desktop app.
04
Share when you need to
Promote a workspace online, sync across devices and invite collaborators by email.

Start local. Go shared when the work does.

Begin with a private desktop board. Add online workspaces, cross-device sync, invites, and collaboration when the project becomes a team effort.

Free

Local desktop

Boards, repositories, worktrees and agent runs stay on your machine by default. Credentials remain in your system's secure storage.

✓Local boards
✓Local agent adapters
✓Human approval gates
✓Offline by default

Pro & Team

Online workspaces

Keep board activity in sync across computers and invite collaborators into the workspaces that need a shared view.

✓Cross-device sync
✓Workspace invites
✓Shared board activity
✓Team collaboration

Only the workspace data you choose is synced. Source repositories, worktrees and credentials remain local.

MODELS & KEYS

Use the models you already pay for. No token markup.

Every agent, in every column, runs one of two ways: through the CLI login you already have, or through your own API key. Requests leave your machine straight for the provider—cadre.rocks never sits in the middle of them.

CLI

Use the CLI login

No new billing

Point a column at a CLI that is already installed and authenticated. The run reuses that session.

Works with the subscription you already pay for
cadre.rocks detects which CLIs exist on this machine
Model and reasoning effort still chosen per column
No key to paste, nothing new to store

BYOK

Bring your own key

Your provider, your bill

Prefer API billing, a self-hosted endpoint or a model the CLI does not expose? Save a key for that agent.

Stored in the OS keyring—never in config files, logs or browser storage
Scoped to one agent in one column, separate from Chat BYOK
Any OpenAI-compatible endpoint through a local profile
Remove the credential and the column falls back to the CLI

Tokens are billed by your provider. cadre.rocks charges for the orchestration layer—boards, parallel runs, approvals—never per token.

Column agentsIn progress

Refresh models

EXECUTION ORDER

1Claude CodeAnthropic
Local execution
CLIUses the installed CLI loginBYOKUses your saved API key
Model
CLI default
Reasoning
High
2CodexOpenAI
Local execution
CLIUses the installed CLI loginBYOKUses your saved API key
Model
gpt-5-codex
Reasoning
Extra high
Execution credential configured in the system keyring.

AVAILABLE

GrokOpencodeOpenAI Compatible

Agents run in the order above. Without agents, the column stays manual.

Board settings → Column agents. The credential is scoped to that agent in that column, and is separate from Chat BYOK.

Choose your download

Free local boards · Your CLI logins and keys stay on your machine

COMMON QUESTIONS

Questions, answered.

Does local-first mean I cannot collaborate?

No. Online workspaces add board sync across devices, email invitations, owner/admin/dev roles and shared activity whenever a project needs them.

Is my source code uploaded for sync?

No. Repositories, worktrees, local paths and agent execution stay on your machine. Only the workspace data you promote online is synchronized.

Where are provider credentials stored?

In the operating system keyring: macOS Keychain, Windows Credential Manager or the Linux Secret Service. Never in SQLite, config files or browser storage.