Skip to content

feat(tui): add subagent inbox foundation#13651

Open
friel-openai wants to merge 5 commits intomainfrom
dev/friel/tui-collab-foundation
Open

feat(tui): add subagent inbox foundation#13651
friel-openai wants to merge 5 commits intomainfrom
dev/friel/tui-collab-foundation

Conversation

@friel-openai
Copy link
Contributor

@friel-openai friel-openai commented Mar 6, 2026

Summary

  • add the TUI foundation needed to render subagent inbox items and related agent runtime events
  • teach the chat widget and history cells to display the new agent inbox content cleanly
  • refresh generated app-server schema fixtures and silence foundation-only helper warnings

Notes

  • this is the base TUI layer for follow-on subagent/watchdog runtime behavior
  • it intentionally stops short of the live pinned runtime panel, which lands in the stacked TUI behavior PR

Introduce the base TUI plumbing needed to render collaboration events and subagent state.

Add the foundational app events, history cells, chatwidget handling, and text formatting used by collaboration surfaces, and keep the replay dedupe coverage that prevents duplicate collab inbox rows when compatibility encodings are replayed from snapshots.
Rename the branch-added collab inbox payload, constants, helpers, snapshot, and spawn-mode type to agent terminology while leaving upstream-established collaboration surfaces unchanged.

Regenerate the app-server schema outputs and update the TUI replay snapshot to match the renamed AgentSpawnMode and agent inbox compatibility coverage.
Update the vendored CollabAgentSpawnEndEvent TypeScript fixture to match the current schema generator output after the branch-local agent rename work.
Mark the subagent panel helpers that are only exercised by the later behavior branch as dead-code-tolerant in the standalone foundation branch so codex-tui tests stay warning-free.
@friel-openai friel-openai changed the title feat(tui): add subagent UI feat(tui): add subagent inbox foundation Mar 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant