Your team and your agents,
in one workspace.
Agents read the spec, the issue, the code and the chat. They work in the open, and a person approves anything that cannot be undone.
Start free, no card · Works with Claude Code, Codex, Cursor and any MCP client
Shape the idea
before the first commit.
Specs, boards, decks and interface mocks live in the same workspace as the code that builds them. An approved spec turns into issues, and an agent can draw a board beside you and check its own work.
Plans that know
what the code is doing.
Issues, projects and cycles span every repository in the workspace. Branch from an issue and the pull request links itself, merge it and the issue closes, so the board stays true without anyone updating it.
From branch to production,
in one place.
Git hosting, stacked pull requests, CI and deploys, with branch protection that gates every merge on green checks. See what is live in each environment, then roll back or promote without a rebuild.
Mask secret values in the runner env
#131 · kobeni wants to merge kobeni/mask-env into main · +84 −12 across 6 files
Register the sealed values before the first step runs, not after - otherwise checkout's log is unmasked.
The conversation
stays next to the work.
Channels, threads and a wiki sit beside the issues and pull requests they talk about. Links unfurl with their live status, and one search covers what was said and what was written.
Where the work gets argued about
The sealed box lands today. After that no plain secret exists outside a sandbox.
web#128 is green. Merging.
Pull request
web#128 · Derive the per-workspace key
What happens to a runner we decommission mid-job?
Filed it - REZ-48. The token outlives the runner today, which is the bug.
Issue
REZ-48 · Rotate runner tokens on decommission
Cycle 12 has six days left and nine of seventeen done. The sandbox story is the whole of the rest.
Canvas work slips to 13 then. I would rather ship one story than half of two.
Agents propose.
People decide.
Bring Claude Code, Codex, Cursor or your own agent. Over 270 MCP tools reach every surface your team uses, and anything that cannot be undone waits for a person to approve it.
The RFC is agreed. File the work it implies, one issue per section.
From a failed CI run: run 1a9d on runner
Take REZ-42. The sandbox RFC says what the shape should be.
The details that make it fast.
And keep it safe.
Built for teams that live in the keyboard and the terminal. Conflicts, flaky tests, vulnerable dependencies and breaking API changes show up before they reach production.
Keyboard-first
A command palette for every action, and a key for the ones you repeat.
Command-line native
Repos, issues, pull requests, runs and agent tasks from the rezee binary.
Stacked pull requests
Review a change layer by layer, and restack the rest when one lands.
Conflicts before review
The moment either branch moves, you know whether a pull request still merges.
API contract checks
OpenAPI, GraphQL and protobuf diffs, with breaking changes marked first.
Flaky tests, caught
A test that passes and fails on one commit is flagged, then quarantined with an owner.
Dependency fixes
See which live build carries an advisory, and open the pull request that fixes it.
Incidents from chat
The message becomes the first entry, and the postmortem drafts itself.
Pipelines in one file
Jobs that wait on each other, a step cache, and reruns of only what failed.
The decision behind a pull request lives in a chat thread nobody can find. The spec sits in another tool, three edits behind what was built. Integrations sync copies of the work. They do not share its context.
So we built one system where the work and the reasons for it stay together. That turned out to be what agents need too.
- $22
- a person a month, every layer included
- 500
- agent credits per person each month
- 270+
- MCP tools for your agents
- 1
- workspace instead of five tools
Bring your next project.
Start free, with no card. Connect the agent you already use, hand it an issue, and approve its first merge today.