Pi / OpenCode native TUI slash commands don't execute in composer (+ unified /clear, /tree family)

[PratikRai0101]

Pi / OpenCode native TUI slash commands don't work in composer

Version: v0.1.40
OS: macOS
Harness: Pi (primary), OpenCode (same class of issue)

What happened

Typing Pi-native commands (/new, /sessions, /resume, /tree, /fork, /clone, /compact, /export, /session) or OpenCode-native commands (/sessions, /new, /compact, /export, /undo) in MonoCode's composer (Ask, build, / for commands...) does not execute them. They get sent as plain LLM prompt text.

Expected: they execute the harness-native action (or a MonoCode equivalent), like they do in pi TUI / opencode TUI.

Root cause (checked in source)

1. MonoCode spawns Pi as pi --mode rpc (src/lib/harness/piProtocol.ts:buildPiSpawnArgs). Per Pi docs/rpc.md: "Built-in TUI commands (/settings, /hotkeys, etc.) are not included [in get_commands]. They would not execute if sent via prompt."
2. src/lib/harness/piAdapter.ts → discover: () => discoverPiSkills() → piSkillsFromRpcData (src/lib/harness/piSkills.ts) filters to only source==="skill" + skill: prefix. Built-in TUI commands never enter the / picker.
3. Only omp sets rawSlashCommands:true (src/lib/harness/piFamily.ts:157). pi doesn't, so isNativeCommandPrompt("/new","pi") is false (src/lib/skills.ts:114) and the text goes to the model.
4. MonoCode session layer (monocode.db sessions + resumeByThread in piFamily.ts / opencode.ts) already owns tabs/sidebar — it just needs slash shims calling existing RPCs.

Proposed fix

Phase 1 — portable Pi + OpenCode shims (intercept in promptPreparation.ts + App.tsx:3538 before sendTurn, list in Composer.tsx picker):

Slash	Pi native	OpenCode native	MonoCode mapping
/new	/new	/new (/clear)	new tab
/clear	— (new, unified)	alias of /new	same tab, new_session RPC + rebind, reset context meter, divider in blocks_json
/sessions + /resume, /continue	/resume	/sessions, /resume, /continue	focus Sessions sidebar picker
/compact + /summarize	/compact	/compact, /summarize	existing compactPiContext / compactOpenCodeContext
/export	/export	/export	pi export_html RPC / opencode markdown export
/copy	/copy	—	copy last assistant block (harness-agnostic)
/models, /thinking	/model, /thinking	/models, /thinking	aliases to model/thinking dropdowns (set_model / set_thinking_level)

Unknown /xxx on pi/opencode should show "TUI-only, not supported in MonoCode" instead of sending to the model.

Phase 2 — Pi session tree (pi-only):

• /tree (read-only first): get_tree RPC → picker of prompts/branches
• /tree:switch: jump + continue in same tab
• /fork <n>: fork(entryId) (get_fork_messages) → new tab prefilled
• /clone: clone RPC → duplicate tab

Phase 3: /share//unshare, /undo//redo (opencode git-backed vs pi /tree — needs workspace_snapshot UI), /init.

Don't port: /login, /logout, /connect, /settings, /themes, /editor, /exit, /trust, /scoped-models, /llama.

Files to touch

• src/lib/harness/piAdapter.ts — shim command list
• src/lib/promptPreparation.ts, src/App.tsx:3538 — intercept before sendTurn
• src/chrome/Composer.tsx:496 — / picker entries

Happy to PR Phase 1 (/new + /clear + /sessions + /compact + unknown-slash warning) if maintainers agree with the mapping.

[PratikRai0101]

Screenshots

Composer /-picker only surfaces skills, never TUI commands — composer placeholder reads Ask, build, / for commands, @ for references..., with the model + Supervised pills below. Typing a native command such as /new, /resume, /compact or /tree here never reaches any command runtime: pi's get_commands (which feeds this picker via discoverPiSkills) only returns skill:-prefixed entries, and since the pi provider doesn't set rawSlashCommands, the text falls through to the model as a plain prompt:

Session evidence backs it up: no thinking_level_change-style command event, no session switch — the slash text just becomes another user message in the thread (Sessions sidebar keeps showing the same Current NeoBot project status tab).

Happy to PR the Phase 1 shim (/new, /clear, /sessions, /compact, /export, /copy, unknown-slash warning) — just say the word on the mapping table above.

[hardbeat920]

thank you @PratikRai0101 would it make sense to support all the commands? for example /sessions to me it feels a bit useless considering that the sessions already appear on the sidebar

[PratikRai0101]

Fair question — let me sharpen what /sessions / /resume means here, because it's not duplicating the sidebar.

Today the sidebar only shows open tabs (resumeByThread is an in-memory Map<threadId, providerSessionId>). Quit MonoCode and there's no way back into a Pi session in ~/.pi/agent/sessions/ or an OpenCode server session — Pi TUI's /resume and OpenCode TUI's /sessions both solve exactly that by listing the harness-native store, MonoCode currently doesn't.

So the proposal isn't a second sidebar. It's:

• /resume (pi native name), /sessions + /continue (opencode native names) -> one picker sourced from the harness store, not open tabs. Pi: scan session dir filtered by cwd. OpenCode: list server sessions filtered by directory. Picking one calls switch_session (pi RPC) / getSession + adopt (opencode) into current or new tab.
• Fully agree on skipping TUI-only commands: /login, /settings, /themes, /editor, /exit, /trust, /scoped-models, /llama stay out.
• The rest stays relevant because there's no GUI equivalent: /new, /clear (unified, opencode already aliases it), /compact (+/summarize alias), /export, /copy — plus an unknown-/xxx guard so /new etc. stop silently becoming expensive LLM prompts (composer promises / for commands today).

To keep the PR reviewable I can split it:

• Phase 1a (no listing needed): /new, /clear, /compact, /export, /copy + unknown-slash warning, all via existing ACP/RPC calls in MonoCode's context.
• Phase 1b: the /resume picker backed by the harness session store.

Want me to start with 1a, or do 1a+1b together since the resume gap is the painful one?

[hardbeat920]

@PratikRai0101 thanks for the detailed write-up.

I think fork, clone, new, compact, and model switching should be MonoCode features that work consistently across all harnesses. Each adapter can use its native implementation where available, and slash commands can simply be aliases for those app actions.

For the same reason, I would prefer a unified MonoCode conversation tree instead of exposing Pi’s internal tree only for Pi.
The slash command issue is valid, but I think fork, clone, and tree need a separate cross-harness design.

Thoughts...?

[PratikRai0101]

Agreed on all three @hardbeat920 — slash commands as aliases for MonoCode app actions (native impl per-adapter where available), unified conversation tree instead of Pi-only /tree, and splitting fork/clone/tree into a separate cross-harness design issue.

So for this issue the PR scope becomes:

• Aliases only: /new, /clear, /compact (+/summarize), /export, /copy, /model(s), /thinking, /resume (=/sessions, /continue) — all calling existing app actions/RPCs, no Pi-only tree UI
• Unknown-/xxx guard so they stop silently becoming LLM prompts
• Keeping fork/clone/tree out — happy to open that as a follow-up design issue for the unified tree

If that matches, I'll PR it on that scope.

[hardbeat920]

@PratikRai0101 thanks, splitting out tree, fork, and clone makes sense.

This overlaps with #97 and PR #98, and we are still deciding how commands should be unified across all harnesses.

I do not want you to spend time on a separate Pi and OpenCode implementation that we may later replace.

Please hold off on the Phase 1 PR for now. Once the shared direction is clear, Pi and OpenCode can be added through the same command layer.

Feel free to open a separate design issue for the unified tree, fork, and clone functionality.