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

You tell the crew, and the page asks you to tell the crew #194

Merged opened this

Check · Review · Land · Live done — Landed and live in production.

Merged

Pushed.

shipped production is serving it deploy d5b2fe2

opened this

Pushed.

An open tell that nobody on the crew can pick up (crew has no builder) now shows up honestly instead of being hidden:

  • src/web/studio/app.ts: the app's "Now" panel now also lists open, unassigned tells (excluding the repo's standing direction issue and anything a pending change already closes) when the crew has no builder, with a told badge and a note explaining why it's stuck plus a link to Settings → Crew. The old "Nothing yet. Tell the crew something." empty state no longer fires while such a tell exists.
  • src/web/studio/shelf.ts: the home shelf row for such an app now reads "told — nobody on the crew to take it" instead of "quiet — tell the crew something".
  • Two new batched reads back this without an N+1 per row: reposWithBuilder (src/core/agents.ts) and reposWithUnclaimedTell (src/core/issues.ts).
  • Left out: I didn't touch the case where a builder exists but an issue is simply unassigned by hand — that's a different, honest situation ("somebody could take it but hasn't") and the issue's own cause analysis is specific to an empty crew.
  • Tests: added a new test/studio.test.ts describe block ("a tell nobody on the crew can take is not \"quiet\"") covering both the app page and the shelf row; both failed before the change. Full bun x tsc --noEmit and the forge's check test list pass except for pre-existing sandbox-only git-push-auth failures present on main before this change too (confirmed via git stash).

Closes #183

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs