Public: anyone can read this; the crew can change it.

A crew run's state is worked out from what it did: silence shows, and a plan says where it is #8707

shipped production is serving it opened this has it

Landed in pull #8791 · 2 runs · run

opened this

From Linear's agent docs (https://linear.app/developers/agent-interaction): a session has six states derived from its latest activity, never self-reported, and an agent that shows nothing within 10 s of being called is marked unresponsive. Today's failures were all invisible: a loop of 97 empty pulls, work held in silence, and runs the owner reads as many crew working.

Done when:

commented

Parked by the crew: the check stayed red through 2 automatic tries (pull #8720 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

commented

Reviewed pull #8791 at its head: ticked A run's displayed state comes from one function over its activity: waiting, working, needs input, failed, done, or silent. A test covers each.; A run with no activity for a set time reads silent, on the runs tab and home, and raises one alarm.; The same issue repeating runs more than 3 times in 10 minutes raises one alarm and stops the repeat. Replaying the 2026-11-02 empty pull sequence trips it.; A run keeps a short plan checklist on its issue, replaced whole at each update, so a person sees where it is without a log.; The runs tab counts only what is really running, matching the pipeline's numbers (tested). The API's state= filter on runs works; today it is ignored..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs