The open-source app everyone uses to manage agents at work
navigation: {"section":"Automation and structured work","sectionOrder":60,"order":40}
Status cards
The status-card experiment turns a saved prompt/query into an inspectable summary of watched work, with refresh history, configuration, and archive/restore controls.
Feature ID: status-cards.
Implementation: status page, card detail.
Agent access: companion.
Sub-features
authoring:status-cards/authoring— create a card and configure its prompt, refresh behavior, and summarizer.generation:status-cards/generation— observe compilation/refresh tasks and their successful or failed output.inspection:status-cards/inspection— read the summary, watched work, history, and available query debugging.archive:status-cards/archive— archive and restore without confusing a stale summary with a current result.
How to get to it (user POV)
status-board
Open /status, choose New card, and follow a card at /status/:cardId.
card-settings
Open the card detail’s settings/query-debug controls and archive/restore actions.
Driving it
Preconditions: follow the baseline. Enable status cards, use a configured summarizer and disposable tasks, and record whether summary generation is simulated or live.
status-board
Automated: status-card service/routes covers gated lifecycle and generation contracts; tile UI covers rendering.
Manual: Create a bounded card, inspect its generation task, and wait for a saved summary. Change a watched task, refresh, and verify both the summary and update history reflect the source change. Exercise a failed generation and confirm it is not presented as fresh.
card-settings
Automated: settings form and update engine cover separate UI/engine layers.
Manual: Change a disposable card’s prompt or summarizer, run the offered rebuild/refresh, and inspect the resulting query and summary. Archive and restore it, reload its direct link, and check the actual new generation outcome.
Gotchas
- Summary quality needs comparison against source work, not just a successful task status.
- A saved old summary must not be counted as a successful new refresh.
- Experimental visibility, author permissions, and agent ownership constrain mutation.
Storybook verification
authoring
Capability ID: status-cards/authoring.
Scope: ui Storybook: Mount CreateStatusCardDialog and StatusCardSettingsForm prompt, summarizer, refresh options, required/invalid inputs and save errors. Production: POST /companies/{id}/status-cards and PATCH /status-cards/{id} must enforce gate/author authority, save configuration and start expected compile task when prompt changes. Sources: Source: CreateStatusCardDialog.tsx, StatusCardSettingsForm.tsx, status-cards.ts. Tests: StatusCardSettingsForm.test.tsx, status-cards.test.ts
generation
Capability ID: status-cards/generation.
Scope: ui Storybook: Mount card tile/drawer compiling, refreshing, failed, stale existing summary and successful new-summary states with linked task. Production: POST /status-cards/{id}/recompile and /refresh plus update/finalization engine must persist actual new output/history; compare saved summary with source tasks, not merely successful task status. Sources: Source: StatusCardTile.tsx, StatusCardDetailDrawer.tsx, status-cards.ts, status-card-update-engine.ts. Tests: StatusCardTile.test.tsx, status-cards.test.ts, status-card-update-engine.test.ts
inspection
Capability ID: status-cards/inspection.
Scope: ui Storybook: Mount StatusCardDetailDrawer summary, watched work, update/revision history, query debug, empty/loading/error and stale summary disclosure. Production: GET /status-cards/{id}, /updates, /summary-revisions and /dry-run must filter accessible card/source records; fixtures cannot establish summary truth or query authorization. Sources: Source: StatusCardDetailDrawer.tsx, status-cards.ts. Tests: StatusCardTile.test.tsx, status-cards.test.ts
archive
Capability ID: status-cards/archive.
Scope: ui Storybook: Mount StatusCards and ArchivedStatusCardRow active/archived list, restore pending/failure and old-summary state. Archive differs from deletion. Production: PATCH /status-cards/{id} archived true/false must persist and authorize change; restore may enqueue refresh, whose new outcome must be inspected rather than treating old summary as current. Sources: Source: index.tsx, ArchivedStatusCardRow.tsx, status-cards.ts. Tests: status-cards.test.ts, status-card-update-engine.test.ts