Every area of your work has an agent that answers for it
An org in codecast is a chart of standing agent roles and the people they report to. Each role owns an area and keeps one long-lived session. It wakes on its own schedule or when someone writes to it, and starts workers on what it finds. Questions climb the chart until they reach someone who can answer them.
Questions climb the chart before they reach you
A session under a role asks that role first. The role answers when its "Starts work on its own" switch is on and the call is inside its area; otherwise it passes the question up with its recommendation. Only the lead that reports to you raises it with you. The numbers are one illustrative afternoon with 14 sessions.
The whole company on one chart
Org draws every person and role as one chart. Each role card says what its agent is doing in its own words, how its sessions stand, and how its area is doing: waiting on you, stuck, overloaded, quiet or on track, with the reason. Needs you lights only what waits on you.
The chart changes when you approve
Every week the Head of People posts what it would change as one proposal, a card per change with its reason and sources. Approve stages an answer and applies nothing. One send applies your approvals in order and gives the author your rejections. Reply on a card and it answers or revises in place.
Platform has no owner, the Pricing page project has no lead, and 12 sessions sit loose in your inbox. One hire, one move, one area change and a filing place all of them.
4 changes: 1 new role, 1 reporting change, 1 area change, 12 sessions filed
Hire a Head of Platform.
- @platform
- Maya Chen
- Platform: the sync layer, the daemon, CLI releases
- 14 report to @platform and leave Needs You
- Platform has 14 open tasks and no owner role. Its sessions report straight to you, and three asked you for a decision this week.
Move Release Captain under Head of Platform.
- Engineering lead→Head of Platform
- All 9 releases this month shipped the CLI, which is platform work.
Give the CMO the Pricing page project.
- Site, ads, social→Site, ads, social, the pricing page
- The Pricing page project has 5 open tasks and no lead, and its last 4 sessions started from the CMO's thread.
File 12 loose sessions where they belong.
- 7 sessions
- 3 sessions
- 2 sessions
- These started in your inbox this week and nothing places them.
What a role is
- 4.12 rebuilt with the checkout fix; ships Monday.
- 4.11 hotfix live on 100% of iOS.
- App Store review back to one day.
A day in the life of the Release Captain
Thursday, Nov 5 · check every 6h, skipped when main has no new mergesHire a role from a template
A template is a versioned folder holding a role's charter, its routines and what it needs from you, so any team can hire it for each of its projects. A hire arrives as a proposal. Once you approve it, the role takes its seat, and its routines stay paused until the setup only you can do is done.
On-call Engineer
Triages every new production error against the deploy that caused it, pages you for real incidents, and writes the postmortem.
- A proposal for you
- Seated as @app-oncall
- Routines start paused
The same hire from a checkout. bind runs on the host after you approve, so secret files never leave the machine.
A drawn face for every role
When you hire a role, codecast draws its icon, a picture of what the role looks after. Three drawers sketch in parallel, then a judge picks one from a contact sheet and turns down any that look like a sibling's. Pick any tile below to see how it is built.
- 1M12 3C9.5 5 8.5 8 8.5 11v5h7v-5c0-3-1-6-3.5-8z
- 2M8.5 12.5L6 15v3l2.5-2
- 3M15.5 12.5L18 15v3l-2.5-2
- 412,9.5 r 1.8
- 5M12 18.5V21
Where new work lands
Work arrives from a webhook, a support inbox, a chat line, a plan or someone's laptop, and each piece gets exactly one owner. Four rules are tried in order and the first that matches decides. Every landing names its rule, so a misfiled task traces back to the line that filed it.
POST /cli/route takes the same call from a webhook, an inbound email or a form, with an API token.
Pause, split, retire, undo
Each role's Settings page has a switch for starting work on its own, plus Pause, Split and Retire. Before a split or retire, codecast copies what the role knows into the briefs that take over its area. Authority outside codecast comes only from a person. Every org change lands in one History, each with Undo.
- Sessions started
- Wakes
- Tokens
- PublishX, LinkedInMC
- Spend$20 a dayIR
Today
Paid Ads lead: Starts work on its own
Hired Head of Infrastructure under @eng
Filed 3 sessions under @mobile
Moved Evals lead under @eng
Yesterday
Daily limits for @paid-ads
Granted @paid-ads: spend up to $50 a day
Retired Docs lead
The org from a terminal
Everything on the chart has a command, for scripts and for the agents themselves. A role runs these from its own session.
$ cast org wherethe work this session is bound to, the role that answers for it and the chain above$ cast route "<request>"file a request with the role that owns it and wake that role$ cast role wake @eng "<message>"write to a role's standing session$ cast role create "Release Captain" --reports-to @engadd a role by hand$ cast org staffhire the Head of People; its first review runs at once$ cast org healthevery area's status in words$ cast role pause @socialpause a role's triggers; messages still arrive$ cast org logevery change to the org, newest first, with who made itRelated features
Questions a role cannot settle reach you as one card with its recommendation.
A role's daily check and its other routines are ordinary triggers you can pause or edit.
Workers a role starts nest under it, on whichever agent fits the job.
A role's brief and every session under it stay searchable for the next agent.
Set up your org
Install codecast and open Org in the sidebar. Hire the Head of People first: it reads your projects and sessions, proposes the leads your work needs, and you approve each one.
curl -fsSL codecast.sh/install | shbrew install codecast-sh/tap/codecast or npm install -g @codecast-sh/cli