Discuss anywhere, document once.
Channels, DMs, and shared docs stay close to the work they discuss. Organize the rooms you use, save what matters, and send a message when the time is right.
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.
A place for the conversation around the work.
Keep important rooms close, return to the unread point, and give drafts or saved messages a place to live.
Ditch the context-switching.
Rich unfurls automatically expand commits, pull requests, and issues inline. Everything is indexed, searchable, and fundamentally linked to your Git history. Channels keep discussions organized by topic or team, while direct messages handle the quick syncs. No Slack bot to set up, no webhooks to maintain.
Every deploy, and what was in it
v0.9.4 is out. 6 issues closed, 2 of them security.
Release
v0.9.4 · web
Rollback plan for the key change is the previous key staying readable for one heartbeat. Written up in the runbook.
Every decision becomes knowledge.
A beautiful block editor for specs, deployment guides, and post-mortems. You can see who else has the doc open, and a save that raced someone else's is refused rather than silently overwriting it. Embed live code snippets, reference issue IDs that auto-update their status, and link directly to repository files. When the code changes, your docs know about it.
- Runner sandbox RFC
- Secrets runbook
- Cycle 12 brief
- Agent conduct
- Why one workspace
Runner sandbox RFC
kapA job runs inside a sandbox that holds the only copy of a decrypted secret, and the sandbox is destroyed with the job.
Why not decrypt on the server
Because the server is the thing that gets read. A value that never leaves the sandbox cannot be found in a heap dump, a log line, or a backup.
Rotation
Rotating re-encrypts the store under a new workspace key. Runners hold the old key only until their next heartbeat.
Comments
Say what happens to a job that is killed rather than finishing - that is the case people will ask about.
Filed REZ-48 for the decommission case, which this sentence does not cover.
Filed from this page
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.