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

Asks and crew answers fold into the core: what waits for a person is a state on an issue or pull, shown where that issue or pull already is #13787

shipped production is serving it opened this has it

Landed in pull #13838 · 2 runs · run

opened this

The owner, 2026-11-16: "the whole asks thing and the 'crew answers' things are just flaky abstractions of the core we're trying to get at … they take up a lot of UI space throughout the forge as well and I wonder if they contribute to slowness." His asks page took about 20 s to open in two browsers at once.

Measured on 0.7.613.

  • 59 source files are named for asks (7,578 lines) and 57 test files; 38 web files import an asks module, so an asks block is drawn on a large share of pages.
  • /asks takes 300 ms on the server with nothing else running (render 220 ms; the page budget is 100 ms), and it subscribes to eight live event kinds.
  • On the signed-in home, two asks phases (held 10.8 ms, stopped 8.3 ms) are 19 of the page's 41 ms: nearly half of home's server time computes rows he asked to have off the home.
  • The 20 s itself was the page thread stalled while hosted forges were being started and stopped (the stall log names /forges/:name/stop and engine jobs), which every page shares; asks did not cause that, but a 300 ms page feels it most.

The core. A repository, its issues and pulls, the crew, an app, a forge. "Something waits for a person" is a STATE of an issue or a pull (who is next and why: the next the forge already computes), not a second kind of object with its own page, blocks, counters and vocabulary. A crew member's answer is a comment on that issue or pull.

Ask. Design first (one short note in the pull or a docs page), then remove more than is added:

  1. One place where a person sees what waits for them: the kanban's cards and the issue/pull lists, filtered by "waits for me" (a lane or a filter, the owner's call in review), using next.who. No separate asks inbox page; /asks redirects to that filter.
  2. Asks blocks leave every other page (repo, app, settings, pull, feed, header counters) unless the thing waiting IS that page's object, in which case it is the one status line that object already has.
  3. Forge-level alarms (red main, backup failed, release not serving) are not asks: they are one line in the header that links to the system page (#13712).
  4. "Crew answers" as a separate surface goes: an answer is a comment, with the same thread, notifications and MCP read.
  5. Standing still repositories and "Turn this app off" (landed in 0.7.613 on /asks) move to the apps list as each app's state and action.
  6. The MCP and terminal keep one verb each for "what waits for me" and "decide this", reading the same next.
  7. Delete what this replaces in the same pulls (the owner's rule: only one). Report lines removed against lines added.

Budgets. Home loses the held and stopped phases; the "waits for me" view answers under 100 ms warm with 500 items.

Done when. There is no page, block or counter named asks; a person finds what waits for them on the kanban; the home's server time is under 25 ms.

the crew's run was interrupted: restart, resumes on the next pass — cancelled
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs