TUI: add /rename to rename the current session (prefilled inline editor, /name alias, bindable shortcut)

[code-yeongyu]

Summary

The interactive TUI has no /rename command. Renaming the current session today requires knowing the /name <name> command; there is no argument-less form that lets you edit the existing name, and no main-editor keybinding action for it. OpenCode ships /rename (a prefilled rename prompt, plus a session_rename keybind) and users coming from it expect the same verb. This issue tracks giving the TUI a first-class /rename for the current session, keeping /name as an alias.

Reproduction

1. senpi (or omo) in any project, send one prompt so a session exists.
2. Type /rename — autocomplete offers nothing; submitting it reports an unknown command and the text is sent nowhere useful.
3. Type /name with no argument — it only prints the current name or Usage: /name <name>; there is no way to edit the existing name in place.
4. /hotkeys lists no action for renaming the current session from the main editor (app.session.rename only works inside the /resume picker).

Expected (ideal state / acceptance criteria)

• /rename [name] is a builtin slash command: listed in BUILTIN_SLASH_COMMANDS with an argument hint, offered by autocomplete, shown by /hotkeys and help.
• /rename <name> sets the session display name with the same normalization /name applies today (newlines collapsed, trimmed), prints Session name set: <name> in the chat, and the footer shows the new name immediately.
• /rename with no argument opens an inline rename editor prefilled with the current session name (OpenCode DialogSessionRename parity): Enter commits, Escape cancels, a whitespace-only submit warns Session name cannot be empty and appends no session_info entry, and an unchanged name is a no-op (no new session_info entry).
• /name keeps working as a backward-compatible alias that shares the same handler; its description says it is an alias of /rename. README, docs/usage.md, docs/sessions.md and the session tip name /rename as the canonical command.
• A keybinding action app.session.renameCurrent (unbound by default, like app.session.new/tree/fork/resume; description "Rename the current session") is registered on the default editor and opens the same inline editor, so users can bind a key for it.
• The RPC (set_session_name) and app-server (thread/name/set) surfaces are unchanged; remote/host runtimes work because the handler goes through session.setSessionName.
• Tests under packages/coding-agent/test/suite/ cover the command, the alias, the inline editor commit/cancel/empty paths and the keybinding registration; changes.md trackers and the [Unreleased] changelog are updated so the changelog gate passes.

Actual

• /rename is unknown to the TUI.
• /name exists (packages/coding-agent/src/core/slash-commands.ts:30, handler interactive-mode.ts handleNameCommand) but has no prefilled edit form.
• app.session.rename (ctrl+r) is scoped to the /resume session selector (components/session-selector.ts); in the main editor ctrl+r is app.history.search, so the OpenCode default cannot be reused globally.

Evidence

• packages/coding-agent/src/core/slash-commands.ts:19-44 — builtin list, name present, no rename.
• packages/coding-agent/src/modes/interactive/interactive-mode.ts:4769 — /name intercept; handleNameCommand prints usage when the argument is empty.
• packages/coding-agent/src/core/keybindings.ts:125 — app.history.search = ctrl+r; :163-166 — main-editor session actions default to []; :195 — app.session.rename = ctrl+r (selector only).
• OpenCode reference: packages/tui/src/routes/session/index.tsx (session.rename command with slash: { name: "rename" }), packages/tui/src/component/dialog-session-rename.tsx, packages/tui/src/config/keybind.ts (session_rename: ctrl+r).

Root cause

Feature gap: the session-name API exists (SessionManager.appendSessionInfo, AgentSession.setSessionName, session_info_changed event) but the TUI only exposes it through /name <name>.

Scope

In: builtin /rename, inline prefilled editor, /name alias, app.session.renameCurrent keybinding action, help/hotkeys/tips/docs, tests, trackers, changelog.
Out: renaming other sessions from the main editor (already possible inside /resume), RPC/app-server protocol changes, desktop app work (tracked in the omo-desktop-app repo).

Related

• Desktop counterpart: omo-desktop-app issue (linked in the first comment).

[code-yeongyu]

Desktop counterpart (composer /rename, F2, app-to-CLI name push): code-yeongyu/omo-desktop-app#686.

Plan: one PR here (branch feat/session-rename-command) off main; progress and evidence will be posted on this issue.

[code-yeongyu]

PR opened: #1742 — branch feat/session-rename-command, rebased onto main after the v2026.9.16 release (HEAD 09927c3524).

What landed: /rename [name] as a builtin command, the argument-less form opening an inline editor prefilled with the current session name (Enter commits, Esc cancels, blank rejected, unchanged is a no-op), /name kept as an alias, and an unbound app.session.renameCurrent action for anyone who wants a key. Docs, the session tip, both fork trackers and the [Unreleased] changelog are updated.

Evidence (tests executed on a build machine, never in the shared checkout):

• RED before the implementation: 21/21 failing on the missing builtin, the missing keybinding entry, the unwired action and the not-yet-existing handlers.
• GREEN after: 21 passed (21), plus a regression sweep over the surfaces that iterate the builtin/keybinding tables or drive the same submit handler — 11 files / 85 tests passed.
• bun run check → exit 0.

One behavior change worth flagging: a bare /name now opens the rename editor instead of printing Session name: …, because the alias shares the new handler. The name is still visible in the footer and /session.

[code-yeongyu]

Real-surface QA on the TUI passed, CI is green.

The sandboxed CLI (isolated agent dir, offline, mock model) was driven through the repo's own QA harness and every frame was rendered through scripts/qa/xterm-render.mjs, so the assertions run against the parsed cell grid rather than raw escape strings. 25 grid assertions, 0 failures, covering:

• /rename QA Renamed Session → chat line Session name set: QA Renamed Session and the footer showing • QA Renamed Session •.
• bare /rename → the composer is replaced by a Rename session editor whose value row reads > QA Renamed Session (prefilled, cursor at the end) with enter submit esc/ctrl+c cancel hints.
• Enter on an edited value → Session name set: QA Renamed Session Two, footer follows.
• Escape → editor gone, footer unchanged, no new confirmation line.
• Cleared field + Enter → Warning: Session name cannot be empty, footer unchanged.
• /name Alias Works → the alias renames through the same handler.
• typing /ren → completion row → rename [name] — Rename the current session.
• /help → /rename — Rename the current session and /name — Alias of /rename (set session display name).

On-disk proof of the write semantics — the session file contains exactly three session_info entries, one per accepted rename, and none for the escape, empty or unchanged paths:

{"type":"session_info","name":"QA Renamed Session"}
{"type":"session_info","name":"QA Renamed Session Two"}
{"type":"session_info","name":"Alias Works"}

CI on #1742: 22 checks pass, 0 failing (including the required Check and test, Changelog gate and Review claim gate), mergeStateStatus: CLEAN. Local bun run check exits 0.

QA receipts live under local-ignore/qa-evidence/20260916-session-rename/ (raw .ans frames, parsed grids, rendered HTML, assertion JSON) and are not committed, per the repo's evidence rule.

[code-yeongyu]

Merged as a64c736976 (PR #1742); main now carries the command.

Verified on origin/main after the merge: slash-commands.ts line 30 is { name: "rename", description: "Rename the current session", argumentHint: "[name]" } with /name kept as its alias on the next line.

What shipped: /rename <name> renames immediately with the same normalization /name always applied; bare /rename (and bare /name) opens an inline editor prefilled with the current name — Enter commits, Escape cancels, a blank value warns Session name cannot be empty, and renaming to the same name writes nothing; app.session.renameCurrent ships unbound and is listed in docs/keybindings.md, because ctrl+r in the main editor is already prompt-history search.

Evidence of record:

• Real TUI QA through this repo's own harness (sandboxed CLI, offline, mock model), every frame rendered by scripts/qa/xterm-render.mjs and asserted against the parsed cell grid: 25 assertions, 0 failures — the confirmation line and footer after /rename …, the Rename session editor showing > QA Renamed Session, the Escape and unchanged paths leaving the footer untouched, the Session name cannot be empty warning, the /name alias, the → rename [name] — Rename the current session completion row, and both /help rows.
• On-disk semantics: the session file ended with exactly three session_info entries — one per accepted rename — and none for the escape, empty or unchanged commits.
• Tests: session-rename-command.test.ts + session-rename-editor.test.ts captured RED before the implementation (21/21 failing on the missing builtin, the missing keybinding entry and the not-yet-existing handlers) and 21 passed after; regression sweep over the surfaces that iterate the builtin/keybinding tables or drive the same submit handler: 11 files / 85 tests. Post-rebase re-run on the final tree: 4 files / 29 tests.
• CI on the merged HEAD: all required checks green (Check and test, Changelog gate, Review claim gate); bun run check exits 0 locally and audit-changes-md reports 288/288 production paths covered.

Two things worth remembering from this run: a bare /name no longer prints the current name, it opens the rename editor (the alias shares the new handler, and the name stays visible in the footer and /session); and main was red on arrival for an unrelated reason — interactive-mode-status.test.ts called a newly added private method that its hand-built stub lacked — fixed separately in #1748 rather than merged past.

Desktop counterpart shipped too: code-yeongyu/omo-desktop-app#687 and #688, closing that repo's tracking issue.