Decisions

One queue for the decisions your agents need from you

When an agent hits a fork it cannot settle alone, it writes the question, the options and its reasoning into a card. The card waits in Questions, in the app's sidebar and on your phone. You clear the queue when you choose to, a key per answer, and each answer goes back to the session that asked.

Questions321 waiting on you
Retire agent_runs_v13/3
asked 2h ago · 0 messages since
Approve dropping agent_runs_v1?

Nothing has written to it in 40 days and no query reads it. A drop is recoverable only from a backup restore.

codecast.sh/a/drop-analysis
agent_runs_v1: who still touches it
last write40 days ago
readers in code0
rows1.2M
restore pathbackup only
1Approvefrees the last migration on this table
2Holdkeep it one more release
tor type an answer in your own words
oopen the sessionsskip for nowxdismissescleave the queue
Settings page copyadvisory2/3
asked 1h ago · 31 messages since
Keep short toggle labels, or write each one as a sentence?

Both pass review. Sentences read clearer and make each row about a line longer. I am carrying on with labels.

1Short labelsproceeding with thisthe current layout, no new strings
2Sentencesclearer; 14 strings to rewrite
tor type an answer in your own words
oopen the sessionsskip for nowxdismissescleave the queue
Retry webhook deliveries1/3
asked 52m ago · 6 messages since
Exponential backoff or a fixed 30s retry?

The worker retries every 30s. A 10 minute outage at the provider sends 20 retries per event and trips their rate limit.

Jitter spreads the load but can hold the first good delivery back by up to 4 minutes.

1Exponential with jitter5 retries over about 30m, the first at 10s
2Fixed 30s, capped at 10simplest change; still bursts in long outages
tor type an answer in your own words
oopen the sessionsskip for nowxdismissescleave the queue
your sessions
  • Retry webhook deliverieswaiting on your decisionworking · Decision: Exponential with jitter
  • Settings page copyworking on its defaultworking · Decision: Sentences, overriding it
  • Retire agent_runs_v1waiting on your decisionon top

Three ways an agent can handle a choice it cannot make alone

It can stop and ask, which pulls you out of your own work to read a transcript. Or it can pick alone, and you find out after code depends on the choice. Codecast puts the question in a queue instead, and the agent asks only what is yours to answer: everything else it decides and reports.

The tracks below show an illustrative afternoon, made up rather than measured. They compare who loses time in each approach, and when.
1pm2pm3pm4pm5pm
Stop and askThe agent interrupts you each time it reaches a choice.
you
agent
Decide aloneNobody waits, but you find the guess in the diff and the agent redoes the work.
you
agent
Queue itThe agent asks once with the evidence, and you answer when you next clear the queue.
you
agent
your workagent workingan interruptionreworkclearing the queueparked or on other work

What the agent puts on a decision card

One question, 2 to 9 options, and the reasoning: what it found, what each option costs, and why it cannot pick. Each option carries its consequence under its label, so you compare outcomes where you click.

Codecast refuses a question posted with no reasoning or evidence, and warns the agent when the reasoning is thin or an option does not say what happens if chosen.
A decision's page in codecast: the question in large type, the agent's reasoning, two numbered options each with its consequence, and the answer with who gave it
Every decision has its own page, reached from the card. Discuss opens a thread about it, and once it is answered the page keeps the choice and who made it.
  • The questionone, in large type, so you know what you are deciding before you read anything else
  • The reasoningwhat the agent found, and why it cannot pick alone
  • The options2 to 9, numbered for the keys, each with what happens if you choose it
  • The evidencea report, a page per option or a long document, when a paragraph is not enough
  • The answera click or a number key, or Or answer in your own words

Blocking and advisory asks

Blocking is the default: the agent asks and stops, and the session shows Waiting on your decision until you answer. An advisory ask names a default and the agent carries on with it, while your answer can still override it.

Agents are told to ask in advisory mode only when the default is cheap to undo. Answers often land an hour later and disagree, and everything built on the default in that hour is work to unwind. If reversing costs more than waiting, block.
blocking

The session is waiting on your decision. The queue opens it as the full sheet, and it sorts to the top while the session can still take an answer.

in the session
Waiting on your decision
when you answer
Decision: Hold
answers · Approve dropping agent_runs_v1?
advisory

The agent keeps working on its default. In the session view the ask folds to one pill above the composer, so the thread stays the main event. It sorts after every blocking ask in the queue.

above the composer, folded
Asked for your steer· answer
1Back offproceeding with this
2Switch keys

The agent can turn an advisory ask into a blocking one, which clears its default. A blocking ask never answers itself; only an advisory member of a stack with an Auto default does.

Attaching evidence to a decision

A decision that deserves proof gets a page. The agent can attach a report that renders under the question, give each option its own page so two designs sit side by side, or attach a long document.

A card with a document, option pages or an answer beyond a single choice links to the decision's own page, where there is room to read.

Each option page opens full size from the card. A report or page can be one the agent built for this question, or a page already published in codecast.

Beyond one choice, an ask can take several options, an order, a short form, or one line of text. Each option can also carry its cost, risk and links to evidence.

Which layout?
the options, as pages
1Denseopen ↗
2Roomyopen ↗
1Dense
2Roomy

Clearing the queue, and the order it follows

Questions in the sidebar counts what is waiting on you and opens the queue as a list; one at a time walks it as full cards. The order follows a fixed rule. Blocked asks whose session can still take an answer come first. Blocked asks on a stopped session come next. Advisory asks come last. Inside each group the oldest is first, because a parked agent costs more the longer it waits.

Every ask shows its age two ways: wall clock, and how many messages the session has written since. A blocking ask with traffic after it means someone already answered in the thread.
Questions, in order
Approve dropping agent_runs_v1?
Retire agent_runs_v1·2h ago
Exponential backoff or a fixed 30s retry?
Retry webhook deliveries·52m ago
Rebuild tonight or after the freeze?
Search index rebuild·3h agosession not running
Keep short toggle labels, or write sentences?
Settings page copy·1h agoadvisory
keys, one at a time
1–9answer with that option
ttype your own answer
sskip for now
xdismiss; the agent is not told
oopen the session
escleave the queue

An answer marks the row answered at once and sends a normal user message into the asking session, Decision: <label>, rendered as an answer linked back to the ask. An answer given from the command line writes the same message. The first answer wins; a second one changes nothing.

A permission prompt and an agent's terminal question wait in the same queue. On a permission card the digits are off and only y and n answer, so a digit meant for the previous card can never approve something.

2 of 5
Exponential backoff or a fixed 30s retry?
Retry webhook deliveries ›
A 10 minute outage at the provider sends 20 retries per event today and trips their rate limit.
1Exponential with jitter5 retries over about 30m
2Fixed 30s, capped at 10simplest; still bursts
Or answer in your own words
DismissSkip ›

The phone app walks the same queue one decision at a time, and moves to the next one when you answer, skip or dismiss.

Stacks of related decisions

A stack groups related asks, like everything a launch needs from you, into a checklist with an id such as ds-7. An agent can build one as it asks, or you click group into a stack in the list, tick the cards and name it.

Blocking members never get an automatic answer. The auto default only answers advisory members, from a server job every 5 minutes, counted from when each joined the stack.
Launch checklistds-7due 2h ago
advisory members answer with their default after 24h
2 of 5 cleared
pn
  1. ✓Ship the pricing banner on Monday?Ship
  2. ✓Which plan is the default on signup?Team
  3. Send the launch email to the waitlist?
    1Send Tuesday 9amthe copy passed review on Friday
    2Hold a weeklands after the docs refresh
  4. 4Annual toggle on or off by default?advisory
  5. 5Keep the free tier's 3 seat cap?advisory
answer all defaults (2)resolves every advisory member with the default its agent declared
  • Due. Set on the stack's page: when you mean to clear it. Overdue stacks sort first.
  • Auto default. After that many hours, advisory members are answered with their default. The checklist also answers them all at once.
  • Keys. 1 to 9 answer the current member, n and p move between them.
  • Delegate to a role. Hands the stack to a role, which answers every open category for its members. Protected questions still come to a person.
  • Done. A stack closes when every member is resolved: answered, dismissed or withdrawn.

Editing or withdrawing an open ask

A posted decision belongs to the agent. When the facts change it rewrites the card in place, keeping its age and its spot in your queue. When the question stops mattering it withdraws it, and the conversation shows the ask as withdrawn.

Staleness is measured. Each ask records how far the session had got when it was posted; after 2 hours or 30 messages the agent is told to update or withdraw it. Asking the same question again updates the open card instead of adding a second.
rewritten in place, same spot in the queue
Which schema wins?
Note ids drift on rename·3h ago

The reasoning now says the web index already moved to path ids, so only the daemon is left to change.

withdrawn
Rebuild the search index tonight or after the freeze?withdrawn

It leaves your queue, and the transcript keeps the ask with its withdrawn mark.

What an agent should and should not queue

Switching on Decision queue in Agent features teaches agents where the line is: a card is for an answer that is genuinely yours, and every other choice the agent makes itself and says what it chose.

After posting, the agent writes nothing more about the decision. If its reply would only repeat the card, it ends the turn instead.
queue it
  • What you intendwhen nothing written settles it
  • A fact only you holdnothing in the code, the docs or past sessions says
  • Money beyond its budgetspend the run was not given
  • An irreversible change that reaches manya mistake people outside the work would feel
never queue it
  • ×Anything more reading answersthe code, the docs or past sessions already say
  • ×An answer already givenan earlier card, a ruling or the project's instructions settle it
  • ×Removing data the system rebuildsor that exists to be thrown away
  • ×A status updateprogress goes on the task
  • ×A probe, a test, a layout sampleevery ask reaches your real queue and phone

Commands for scripts and agents

Agents ask through the cast decide command, and anything on this page can be scripted with it. cast decide --help and cast stack --help print the rest.

cast decide "<q>" -o "A :: why" -o "B"Ask one question with 2 to 9 options; text after :: is the consequence
--context <md> | --context -The reasoning, in markdown; - reads a heredoc
--report <file>Publish an HTML or markdown page and embed it under the question
--option-page n=<file|slug|url>A page for option n
--doc <file>A long markdown body; the card links to the decision page
--advisory --default <n>Keep working on option n; the answer may override it
--kind single|multi|rank|form, --line <label>Ask for one, several, an order, a form, or one line of text
--card <card.json>Ask about a change card; without -o the options are Ship, Revise, Drop
--stack ds-N · --task ct-N · --to @handleAppend to a stack, bind to a task, address a person
cast decide ls [--mine]This session's asks with ids, answers and staleness
cast decide edit [id] [flags]Rewrite the open ask in place; --blocking clears the default
cast decide cancel [id]Withdraw it; the conversation shows it as withdrawn
cast decide show <sd> · answer <sd> <n>One decision in full; answer from a shell
cast stack create "<title>" [--policy auto-default:24h]Start a stack
cast stack add | remove | reorder | show | lsShape and read stacks
cast stack policy ds-N --due <when> | --auto-default <dur>When you mean to clear it; when advisory members default
cast stack delegate ds-N @handleA role answers every open category for the stack's members

Limits and questions

The parts people ask about first.

What happens when I dismiss?
The row resolves as dismissed and leaves your queue. The agent is not told. If it should hear no, answer instead, or type a reply with t.
Can two people answer the same ask?
The first answer wins. A second answer to a row that is no longer pending changes nothing, and the person who answered second is told the first answer stands.
Who receives it?
By default, whoever the asking session reports to: its owners and the first person its reporting line reaches. An agent can name people in the session's workspace instead.
Can an agent answer for me?
On teams using the org chart, a role can recommend an option, and a role holding a grant for that kind of question may answer it. Production, billing, data, access, external and product questions always stay with a person, and a person's answer always wins the race.
How many options?
2 to 9, mapped to the keys 1 to 9. For more structure an ask can take several choices, an order, or a short form.
Does blocking freeze the agent?
No. The agent is told to end its turn after asking. The session parks because the agent stops; nothing locks it.
Can I change an answer?
No. Once a row is answered, an edit or cancel fails and prints the answer. To change course, send the session a message.
What if the agent crashes and retries?
Posting the same question from the same session updates the open row, so a retry does not create a duplicate.

Get started with decisions

Install codecast, open Agent features from your account menu and switch on Decision queue. Your agents learn when to queue a choice and how to write the card, and the queue waits in Questions on the web, the desktop app and your phone.

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