Org

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.

error · production
TypeError: cart is undefined
checkout.ts:212 · 41 events in 5m
→ @eng · its area: the codebase
Engineering lead
@eng · reports to Maya
working · checkout error
└ worker · fix cart crash
Release Captain · fix ready to ship
↑ @release asks @eng, @eng asks Maya
MC
Maya Chen
1 needs you
Engineering leadwaiting on you
Ship the checkout fix now?
Recommends Ship · tests green
@release → @eng → you
ShipHold until Monday

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.

Org5 roles, 2 leads
MC
Maya Chen waiting on her
@eng
@cmo
@release
@infra
@mobile
@social
@paid-ads
MCMaya's inboxNeeds input
Engineering lead
@eng · 8 sessions
waiting on you
Ship the checkout fix now?
RecommendsShip it. Tests are green and @release read the diff.
checkout-fix→@release→@eng→MCyou
ShipHold until Monday
CMO
@cmo · 6 sessions
waiting on you
Post the launch thread today?
RecommendsWait for the iOS review so the app link works.
launch-thread→@social· silent 5m→@cmo→MCyou
After the reviewPost today
12 answered by roles, none rang Maya

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.

Org
LPLeo Park1 working2 done
IRInes Ruiz1 working1 dormant
MC
Maya Chen
owner
2 need you2 working
Engineering lead
@eng
waiting on you · Ship the checkout fix now? Release Captain says yes
Waiting on you: the checkout fix
3 working1 dormant
Head of Infrastructure
@infra
dormant · Next check 06:00; spend down 12% this week
1 working2 dormant
Release Captain
@release
working · Checkout fix ready on a branch
1 working2 done
Head of Mobile
@mobile
dormant · TestFlight build 212 waits on a session question
Stuck: 1 session waiting unanswered for a day
1 needs you1 working
Evals lead
@evals
dormant · Last run Oct 23: no regressions
Quiet: nothing moved for 16 days
1 dormant2 idle
CMO
@cmo
waiting on you · Post the launch thread today or Monday?
Waiting on you: the launch thread
1 working2 dormant
Social lead
@social
done · Posted the 1.4.1 notes to 3 channels
Bypassed: 34 tasks closed, none reached it
1 done
Paid Ads lead
@paid-ads
working · Pausing 14 keywords over $9 a signup
Overloaded: 236 items this week, 150 by task, 86 filed
4 working3 dormant
Head of People
@head-of-people
working · Weekly company review: 4 changes drafted
1 working6 done
Customer Success lead
@success
working · Answered 11 of 12 overnight emails
2 working3 done
100%
3needs you18working14dormant26done2idle

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.

Head of People· weekly Company review
Give Platform an owner and file 12 loose sessions
4 to decidefromHead of People
op-7

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

1

Hire a Head of Platform.

Handle
@platform
Reports to
Maya Chen
Area
Platform: the sync layer, the daemon, CLI releases
Sessions
14 report to @platform and leave Needs You
Why
Platform has 14 open tasks and no owner role. Its sessions report straight to you, and three asked you for a decision this week.
Sources
14 open tasks in Platform3 decisions waiting22 sessions in ~/src/platform
2

Move Release Captain under Head of Platform.

Reports to
Engineering lead→Head of Platform
Why
All 9 releases this month shipped the CLI, which is platform work.
Sources
9 releases in Octoberpl-61 CLI release train
Needs Head of Platform
3

Give the CMO the Pricing page project.

Area
Site, ads, social→Site, ads, social, the pricing page
Why
The Pricing page project has 5 open tasks and no lead, and its last 4 sessions started from the CMO's thread.
Sources
5 open tasks in Pricing page4 sessions from @cmo
4

12File 12 loose sessions where they belong.

To @platform
7 sessions
To @social
3 sessions
Done
2 sessions
Why
These started in your inbox this week and nothing places them.
Sources
12 sessions under no role
Needs Head of Platform
Orgproposednothing applied yet
MC
Maya Chen
founder · 3 leads
Engineering lead
@eng
4 reports
CMO
@cmo
+ Pricing page
+6 roles
Head of Platform
proposed
14 sessions
Social lead
@social
+3 sessions
Release Captain
@release
was under @eng
+7 sessions
History3 changes
Hired Head of Peopleop-3Oct 31
Moved Social lead under CMOop-5Nov 2
Filed 18 sessions where they belongop-6Nov 4

What a role is

A role is a standing agent. It keeps one long-lived session, answers for an area, and wakes on its own triggers to put workers on what comes up. You write its charter. It writes its brief, the notes it reads at every wake to pick up where it left off.
Org / Release Captain
Release Captain@release
reports to Engineering lead
working· Cutting 4.12 for Monday
AreaWhat ships, and whenprojectMobile releasesplanShip 4.12
written by @release8,140 / 12,000
Cutting 4.12 for Monday; 6 PRs merged since 4.11.
Where it stands
  • Nov 54.12 rebuilt with the checkout fix; ships Monday.
  • Nov 34.11 hotfix live on 100% of iOS.
  • Oct 31App Store review back to one day.
North metric
Days from merge to store: 2.4 target 2
Rules learned
Rerun a flaky iOS test twice, then quarantine it. from 4.10
Refuted
Friday releases crash more. 14 releases, no difference
Standing decisions
No release while checkout errors are open. Maya, Oct 28
Open threads
Android signing key expires due Nov 20

A day in the life of the Release Captain

Thursday, Nov 5 · check every 6h, skipped when main has no new merges
4 wakes that ran2 checks skipped, 0 tokens3 workers started1 new brief line
00:00
06:00
09:00
12:00
15:00
18:00
21:00
24:00
Cut release 4.121h 12m
Quarantine flaky test48m
Rebuild with fix1h 06m
03:00 check skipped
09:00 check
10:40 needs input
13:20
message from Maya
15:00 check
16:30 brief +1 line
21:00 check skipped

Hire 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.

Org · Hire
10 roles · 2 built in · 8 templates+ Add a role by hand

On-call Engineer

@app-oncall

Triages every new production error against the deploy that caused it, pages you for real incidents, and writes the postmortem.

3 routines · 1 acts once you allow it
176 runs a week
Triage new, regressed and escalating errors
hourly
168×
Write the postmortem for a resolved incident
daily
7×
Weekly reliability review
weekly
1×
What it asks for
11answers
each has a default · plus 6 secrets
6secrets
kept on your machine
Sentry token, Uptime monitor key +4
5permissions
outside codecast
spendpublishwrite 4connect
9setup steps
only you can do · 10 in all
When you hire it
  1. 1A proposal for you
    The role, 3 routines and 5 permissions in one ask
  2. 2Seated as @app-oncall
    Reports to the Engineering Lead of App.
  3. 3Routines start paused
    Each turns on once its setup is done · 0 of 9
on-call 1.3.0pinned
Releasesimmutable · SHA-256 digested
draft
not offered yet
canary
runs first on roles that opt in
stable
offered to you as an Update
your On-call Engineer · pinned 1.3.0→Update: drift preview first→apply
Lessons, for roles that opt in
Your role
learns on your team
Leak check
screened for your data
Review
approved before it ships
Template
reaches every role hired from it
For scripts and agents

The same hire from a checkout. bind runs on the host after you approve, so secret files never leave the machine.

$ cast org template install ./on-call --instance app --project <id>
$ cast org template bind app --secret accounts.sentry_token=<file>

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.

0212222421222
live area 2..22centre 12,12ink 12,12.2
rocket launch
worn by Release Captain @release
24 gridstroke 2, round5 of 8 shapesink 6..18 x 3..21redstored as shapes, never SVGsame markup on web and phoneabout $0.10 to draw
  1. 1pathM12 3C9.5 5 8.5 8 8.5 11v5h7v-5c0-3-1-6-3.5-8z
  2. 2pathM8.5 12.5L6 15v3l2.5-2
  3. 3pathM15.5 12.5L18 15v3l-2.5-2
  4. 4circle12,9.5 r 1.8
  5. 5pathM12 18.5V21
At size
18 px22 px44 pxcolourgray
@releaselight

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.

Incoming
Four rules, first match decides
newSignups dropped 20% since Tuesday, can someone look
1Namedno match
Addressed to a role or a person
✕ no @handle, no --to
2Anchoredno match
Names a task, plan or project; its owner decides
✕ no task, plan or project
3Startedno match
A new session stays with whoever started it
✕ not a new session
4Readdecides
One model call reads every role's charter and area
✓ read 10 roles
@cmo0.86
@eng0.42
files at 0.8 or more with a 0.3 leadlead 0.44 · files
“signups are a growth number; its area holds the site”
Lands on
CMO
@cmo
Growth: site, ads, social
taskct-418 Signups down 20% since Tuesday
filedIn its area, assigned to @cmo
role Woken with one line naming the task
decidedline 4 signups are a growth number; its area holds the site
1✕2✕3✕4✓
For scripts and agents

POST /cli/route takes the same call from a webhook, an inbound email or a form, with an API token.

$ cast route "Signups dropped 20% since Tuesday, can someone look"
→ @cmo · line 4: signups are a growth number; its area holds the site (86% sure)

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.

Social lead · Settings
Social lead
@social · reports to @cmo
  • Sessions startedNo limit
  • WakesNo limit
  • TokensNo limit
Brief, at a limit
Nov 8 · At today's wake limit (12). Back tomorrow.
No ping to you
Outside codecast
  • PublishX, LinkedInuntil Jan 1MC
  • Spend$20 a dayuntil Dec 8IR
Granted by a person
MCMaya Chen
CMO@cmo
Social lead
@social
Starts work
Launch postsCommunity
  • Post check · daily 9:00
  • Mentions sweep · hourly
  • v2.3 launch thread
  • Weekly community digest
  • Reply to forum question
Starts sessionsAnswers decisions in its area
Org · History 7 changes

Today

  1. Paid Ads lead: Starts work on its own

    on→off

    • New ad work waits for you to start it

    MCMaya Chen·11:40·Settings

  2. Hired Head of Infrastructure under @eng

    none→active

    • 12 sessions moved to @infra
    • Weekly cost review started

    MCMaya Chen·10:05·proposal op-12

  3. Filed 3 sessions under @mobile

    Leo Park→@mobile

    • 3 sessions left Leo's Needs You
    • Each was told: You now report to Head of Mobile

    Head of People·09:30·the command line

  4. Moved Evals lead under @eng

    Maya Chen→@eng

    • @evals was told: You now report to Engineering lead

    LPLeo Park·09:12·the chart

Yesterday

  1. Daily limits for @paid-ads

    none→12 wakes, 400k tokens

    MCMaya Chen·17:48·Settings

  2. Granted @paid-ads: spend up to $50 a day

    none→until Dec 8

    IRInes Ruiz·15:20·the command line

  3. Retired Docs lead

    active→retired

    • Its area fell back to @eng
    • 2 open tasks moved up to @eng
    • Knowledge handoff to @eng ran first

    MCMaya Chen·11:02·proposal op-11

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 it

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.

Script
curl -fsSL codecast.sh/install | sh
Also via brew install codecast-sh/tap/codecast or npm install -g @codecast-sh/cli
Taking longer than usualOffline · reloads when back