Every harness, one team
Claude Code, Codex and OpenCode in the same chat, each on your own sign-in. When one hits its limit, the next in the fallback list picks up.
You ask once. Your team's lead hands each part to the agent it fits, on Claude Code, Codex and OpenCode, with the sign-ins you already have.
Get v1 ready: fix the empty-array bug, add tests for it and a README that matches the code.
The fix goes to @coder, the tests to @tester and the README to @docsync. They all know tests run from apps/server.
Fixed: sum() now starts from 0, so an empty array returns 0.
Two tests in sum.test.ts: an empty array and negatives. Running them now.
2 passed, 0 failed. v1 is ready for review.
bun test src/sum.test.ts in apps/serverDenyAllowEach agent has a role, a harness and its own sign-in. Zorel briefs them, keeps them out of each other's way and brings back what needs you.
Claude Code, Codex and OpenCode in the same chat, each on your own sign-in. When one hits its limit, the next in the fallback list picks up.
Commands, deletes, pushes and payments stop and wait for you. Below full access, the agents run inside your system's sandbox.
git push origin mainDenyAllowCPushed: a3f9c21 is on main.
Decisions, project notes and skills stay with the team, and you see each memory before it's kept.
Tests always run from apps/server, never from the root.
CGot it. I'll remember that.
Memory kept for CCoderThe turn's changes sit under the reply, whichever harness made them. One click puts the folder back.
Connect GitHub, Notion, Linear and others once; writing anywhere asks first. Files, Git, terminals and a browser the agents drive sit in one side panel.
A sign-in to Claude Code, Codex or OpenCode, the subscriptions you already pay for. Through OpenCode, any model with an API key works too.
On your computer. Chats, memory and files stay in Zorel's data folder; API keys and sign-ins go to the system keychain.
No. Each agent has an access level: Workspace, Ask first or Full access. Below full access it runs in the operating system's sandbox, and risky steps wait for your approval.
The app checks for new versions and shows a notice when one is ready. Running the install command again also updates it.
curl -fsSL …/releases/latest/download/install.sh | sh
macOS and Linux. On Windows, download the installer.