Everything your team ships,
in one place.

From idea to deploy - everything in one workspace.No context switching. No data scattered across seven tabs.

Get started

Search⌘K

Good morning, kash

3 things want you. Everything else is running clean.

Open issuesPlan

9open

3 in progress · 3 todo

Pull requestsCode

2open

1 waiting on you

CIShip

94% passing

over the last 32 runs

AgentsAgents

2working

1 waiting on a person

This cycleCycles

9of 17

Cycle 12 · 6 days left

Needs you

Ship

Pull requests

Agents

Docs in review

Unread

Projects

FIG 0.1 — unified workspace

One Unified Operating System.

Every tool from your product development lifecycle, built to talk to each other from day one.

Ideate & Design

Shape ideas into specs and designs, with the whole team weighing in before a line of code is written.

Plan & Track

Know what the team is working on, who owns it, and when it's done - no status meetings needed.

Code & Ship

One push triggers code review, CI, and a deploy - all without leaving your workspace.

Discuss & Document

Discuss in channels that understand your code, and every decision is captured as searchable knowledge.

AI & Agents

Agents that work across every layer - triaging issues, reviewing code, drafting docs, with full context of your workspace.

Shape the idea before the first commit.

Specs, RFCs, and design docs written together in the workspace. Once one is signed off, its sections become tracked issues in one step - and the page reads their status back as the work moves.

Ideate & Design

DraftSearch⌘K

makima

Layers

Sealed boxFrame
Runner sandboxFrame
Key storeRectangle
decrypt()Text
heartbeatConnector

Propertieskm

X120Y76W300H190

Fill#1B1D21

ExportPNG · SVG

100%

Know what the team is working on, always.

Assign an issue to a teammate or an agent - same board, same states. When issues live next to the code that fixes them, progress is visible to everyone, without a single status meeting.

Plan & Track

Search⌘K

Priority

Todo3

aaki1

ppower1

No assignee1

In Progress3

aaki1

denji1

kobeni1

Review where the work already lives.

Understand every change at a glance, line by line - what your team writes and what your agents propose. Comment on the line you mean, argue it out beside the code, and merge without ever leaving Rezee.

Code & Ship

apps/rezee/src/WorkspaceView.tsx

01import { useState } from 'react'

02import { Channel, Workspace } from '@rezee/core'

03import { useWorkspace } from '@hooks/useWorkspace'

04import { Sidebar } from '@components/Sidebar'

05import { RepoCard } from '@components/RepoCard'

06import { Spinner } from '@components/Spinner'

08export function WorkspaceView({ workspaceId }: Props) {

09 const { repos, isSynced } = useWorkspace(workspaceId)

10 const [active, setActive] = useState<string>()

12 if (!isSynced) {

13 return <Spinner size="large" />

14 }

16 return (

17 <Panel>

18 <Sidebar repos={repos} active={active} />

19 <main className="grid gap-4">

20 {repos.map((repo) => (

21 <RepoCard

22 key={repo.id}

23 repo={repo}

24 active={active === repo.id}

25 />

26 ))}

27 </main>

28 </Panel>

29 )

30}

01import { useState } from 'react'

02import { Channel, Workspace } from '@rezee/core'

03import { useWorkspace, SyncState } from '@hooks/useWorkspace'

04import { Sidebar } from '@components/Sidebar'

05import { RepoCard } from '@components/RepoCard'

06import { Spinner } from '@components/Spinner'

08export function WorkspaceView({ workspaceId }: Props) {

09 const { repos, syncState } = useWorkspace(workspaceId)

10 const [active, setActive] = useState<string>()

12 if (syncState === SyncState.Pending) {

13 return <Spinner size="large" />

14 }

16 return (

17 <Panel>

18 <Sidebar repos={repos} active={active} syncState={syncState} />

19 <main className="grid gap-4">

20 {repos.map((repo) => (

21 <RepoCard

22 key={repo.id}

23 repo={repo}

24 active={active === repo.id}

25 />

26 ))}

27 </main>

28 </Panel>

29 )

30}

Push to deploy, without leaving your workspace.

Define pipelines in .rezee/actions.yml. Every push runs in isolated containers and streams logs to your browser. When a step fails, an agent can push a fix and re-run, so your team just gets the green check.

Code & Ship

Search⌘K

kobeni/mask-env

b89e62c

pushed by kobeni · 12 minutes ago · took 1m 48s

web - the runner opens a sealed box, and nothing else does

runningweb.rezee/actions.yml3/5 steps

$ bun test
  184 passed · 0 failed
  running secrets.test.ts

Team chat that understands your code.

Channels and DMs where pull requests, issues, and commits unfurl inline. Ask @rezee anything about the codebase, and your team decides what happens next.

Discuss & Document

Search⌘K

Channels

engWhere the work gets argued aboutkapm5

kash10:02

The sealed box lands today. After that no plain secret exists outside a sandbox.

kobeniAgent10:04

web#128 is green. Merging.

Pull request

web#128 · Derive the per-workspace key

merged · 11 files · +212 −47

aki10:11

What happens to a runner we decommission mid-job?

kobeniAgent10:12

Filed it - REZ-48. The token outlives the runner today, which is the bug.

Issue

REZ-48 · Rotate runner tokens on decommission

Todo · High · aki

ak4 replieslast 9m ago

power10:26

Cycle 12 has six days left and nine of seventeen done. The sandbox story is the whole of the rest.

makima10:31

Canvas work slips to 13 then. I would rather ship one story than half of two.

Docs that stay connected to your code.

A block-based editor for specs, runbooks, and RFCs. Set an agent watching pushes and it drafts the doc update against the diff, for you to edit.

Discuss & Document

In reviewSearch⌘K

Docs

Runner sandbox RFC
Secrets runbook
Cycle 12 brief
Agent conduct
Why one workspace

Runner sandbox RFC

kap4 here

kobeni · edited 20 minutes ago

A 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

aaki18 minutes ago

destroyed with the job

Say what happens to a job that is killed rather than finishing - that is the case people will ask about.

kobeniAgent9 minutes ago

until their next heartbeat

Filed REZ-48 for the decommission case, which this sentence does not cover.

Filed from this page

REZ-42REZ-48REZ-49

kakash and aki approvedApprove

Made for teams and their agents.

Delegate a task and watch an agent work it end-to-end - across the same issues, PRs, and pipelines your team already uses. It asks for review when it needs it, and you always have the final say.

AI & Agents

Search⌘K

Mask secret values in the runner env

From an issue · @kobeni·12 minutes ago·What it changed

Needs review

48,210 tokensclaude-sonnet-5

k
kash18 minutes ago
Take REZ-42. The sandbox RFC says what the shape should be.
read_issue{"key":"REZ-42"}

REZ-42 · Encrypt pipeline secrets at rest
  Urgent · In Progress · web
  3 sub-issues, 1 done

kobeni16 minutes ago
The derivation landed in web#128, so what is left is masking the values on their way into the runner's environment, and again on their way out through the log.
edit_file{"path":"src/runner/mask.ts"}
```
src/runner/mask.ts · +18 −2
```
a
aki14 minutes ago
Cover the case where the value is a substring of a longer token, not just an exact match.
kobeni13 minutes ago
Added a test for it. 184 passed, and the new one fails against main, which is what I wanted from it.
Proposed action - awaiting approval
Open a pull request against main
open_pull_request{"branch":"kobeni/mask-env","title":"Mask secret values in the runner env"}

This action needs your approval.RejectApprove

Built on strong foundations.

A unified workspace only works if every part of it is fast, private, and connected. These are the principles the whole platform is built on.

Built for speed

Every interaction is instant. Optimistic updates, local caching, and a real-time sync engine keep the UI ahead of your keystrokes.

Command-line native

Everything you can do in the browser, you can do in the terminal. Create issues, review PRs, and trigger deploys without touching the mouse.

Keyboard-first

A command palette and shortcuts for every action. Power users never leave the home row.

Secure by default

Encrypted secrets, scoped access tokens, and private repos invisible to non-members. Security isn't an add-on tier.

Open to agents

A clean API and MCP support, so any agent can drive the same issues, PRs, and pipelines your team does. Agents are teammates, not a bolt-on.

five tools. five tabs. five sources of truth that never quite agree. Your work doesn't live in silos, so your tools shouldn't either. Rezee is one system for the whole lifecycle - design, plan, ship, discuss, and document, all in the same place, all talking to each other from day one.

No integrations to wire up. No context lost between apps. Just one place where everything your team and their agents ship already knows about everything else.

Ship faster,
together.

The unified operating system for your entire product development cycle. One platform for your team to plan, build, and deploy.

Launch Rezee View documentation

Everything your team ships, in one place.

Good morning, kash

One Unified Operating System.

Shape the idea before the first commit.

Know what the team is working on, always.

Review where the work already lives.

Push to deploy, without leaving your workspace.

kobeni/mask-env

Team chat that understands your code.

Docs that stay connected to your code.

Runner sandbox RFC

Why not decrypt on the server

Rotation

Comments

Filed from this page

Made for teams and their agents.

Built on strong foundations.

Built for speed

Command-line native

Keyboard-first

Secure by default

Open to agents

five tools. five tabs. five sources of truth that never quite agree. Your work doesn't live in silos, so your tools shouldn't either. Rezee is one system for the whole lifecycle - design, plan, ship, discuss, and document, all in the same place, all talking to each other from day one.

Ship faster,together.

Everything your team ships,
in one place.

Ship faster,
together.