Skip to content

Orchestrator per-tab + (shells) + chef toggle; Discord MVP plan#259

Merged
ANonABento merged 2 commits into
mainfrom
orchestrator-ux-and-discord-plan
Jun 7, 2026
Merged

Orchestrator per-tab + (shells) + chef toggle; Discord MVP plan#259
ANonABento merged 2 commits into
mainfrom
orchestrator-ux-and-discord-plan

Conversation

@ANonABento

Copy link
Copy Markdown
Owner

Two commits.

feat(orchestrator): per-tab + + chef toggle

  • The orchestrator + is context-aware: Chat → new chat, Terminal → new shell (sub-tab strip: Shell 1, Shell 2… with close ×; each its own chef_<ws>[_n] tmux session), Files → hidden.
  • Settings → Agent → Show orchestrator panel toggle (hide the in-app chef if you drive the board externally). Persisted, defaults on.

docs(discord): MVP plan + epic refresh

  • .tickets/discord/MVP-PLAN.md: thin first slice (connect → task→thread → agent output streaming, one direction). Reply-routing/#chef/bidirectional stay later slices.
  • E001 note confirming thread=task + thin-MVP-first, flagging architecture drift since it was written.

tsc · lint · clippy · cargo check · vitest (+2 terminal tests) green locally.

The orchestrator panel's `+` button is now context-aware on the active view:
- Chat → new chat (unchanged; still disabled when the chat is empty)
- Terminal → new shell, shown as a sub-tab strip (Shell 1, Shell 2, … with a
  close ×). Each shell is its own tmux session — `chef_<ws>` for shell 1
  (back-compat), `chef_<ws>_<n>` for the rest; `ensure_chef_terminal` takes an
  optional shellIndex. Only the active shell renders; switching re-attaches with
  restored scrollback, and you can't close the last one. The strip only appears
  with >1 shell.
- Files → `+` is hidden (read-only browser, no sensible "new" yet)

Also adds a "Show orchestrator panel" toggle (Settings → Agent → Orchestrator &
Concurrency). Off hides the chef panel in both docks — for users who drive the
board from an external agent (MCP/API) and don't need the in-app chef. Defaults
on; persisted via AgentConfig.orchestratorEnabled.

tsc · lint · clippy · vitest (+2 terminal tests) green.
Adds .tickets/discord/MVP-PLAN.md — a thin first vertical slice for the existing
Discord epic (E001): connect the bot, create a thread per task in its column's
channel, stream agent output into it (KaitenCode → Discord only). Reply-routing,
#chef, and bidirectional sync stay as later slices (T058–T060).

Adds a dated note to E001 confirming the thread=task (board mirror) model and the
thin-MVP-first decision, and flagging that the architecture has moved since the
epic was written (local API on by default, advisory interactive completion).
@ANonABento ANonABento merged commit 9d83770 into main Jun 7, 2026
3 checks passed
@ANonABento ANonABento deleted the orchestrator-ux-and-discord-plan branch June 7, 2026 18:58
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