Navi Code TUI: show request duration (live timer + chat metadata) ...

Live elapsed timer next to the activity indicator (ticks once per second
during a turn, format 2m 16s), driven by the same stream_start/stream_end
hooks as the activity indicator — so it spans the whole turn (all LLM calls,
tool calls, planning, sub-agent steps). On stream_end it syncs to the
backend's authoritative elapsed_seconds before freezing; on stream_stopped/
error/disconnect it freezes at the locally-measured value.

On stream_end the model also appends a turn_meta ChatItem rendered as a dim
"⏱ 2m 16s" line below the answer — the total time the agent spent on the
user's request. The value comes from stream_end.elapsed_seconds, already
measured by the backend over the whole turn, so the TUI needs no timer for
accuracy. stream_stopped/error do not get a metadata line (only completed
requests).

Shared format_duration(): None -> "—", <60s -> "16s", <3600 -> "2m 16s",
>=3600 -> "1h 2m".

Co-Authored-By: Claude <noreply@anthropic.com>

Navi Code TUI: context-window fill gauge in the status bar ...

Add a ContextFill widget to the bottom StatusBar showing how full the LLM
context window is (absolute tokens + percent), colored by fill level:
dim < 70%, warning 70-89%, error >= 90%. Updates from stream_end and
compression_started/context_compressed events; seeded from get_session on
resume so the gauge isn't blank pre-turn. None from the backend keeps the
last known value.

Fix: name the widget attribute _ctx_fill, not _context — _context shadows
MessagePump._context (the internal context manager Textual wraps around
message processing) and hangs the app's message pump at mount time.

Polish: drop the "ctx " prefix (shows 12.0k/32.0k · 38%) and add a 1-char
margin between the activity indicator and the gauge.

Co-Authored-By: Claude <noreply@anthropic.com>

tui: load session message history into the chat panel on resume ...

Resuming or switching a session showed a blank chat — the past conversation
was never replayed. GET /sessions/{id} already returns the messages; the TUI
just ignored them.

- ChatModel.load_history maps persisted Message dicts back to the same
  ChatItems the live stream produces (user/assistant text, thinking, tool
  started/result, plan), skipping is_display=False (context-only user,
  summaries, compression events) so only what the user would have seen
  live is rebuilt.
- ChatPanel.load_history wraps it (clears the render cache + refresh).
- attach_session loads the messages from get_session, so resume/switch
  replays the history before the cwd/Connected banners.

Co-Authored-By: Claude <noreply@anthropic.com>

tui: activity indicator in a bottom status bar + 1-line input ...

Add an animated "agent is working" indicator so a silent gap (long-running
tool, the pause before the first token, sub-agent reasoning) reads as
"alive" rather than "hung": a braille spinner + phase label that runs on
its own timer, independent of the WebSocket event flow.

- New ActivityIndicator widget (rotating spinner + phase label, colored
  status_online), started/stopped from tui_app WS phase transitions
  (thinking / responding / planning / running <tool>) and stopped on
  stream_end/stopped/error and on connection drop.
- New StatusBar bottom line replaces Textual's Footer: indicator on the
  left, dim key-combo summary on the right. One line instead of the menu;
  the key bindings themselves stay on the App so the keys still work.
- Input box: TextArea min-height 3 -> 1, so the prompt is one line by
  default (auto-resize + max-height 12 unchanged).

Co-Authored-By: Claude <noreply@anthropic.com>

tui: drop unused Tokens/Iter rows from the status panel ...

set_tokens/set_iterations were never called and the two rows permanently
showed "-", so they were dead noise in the right column. Remove the rows
and their setters.

Co-Authored-By: Claude <noreply@anthropic.com>

tui: bound chat history render cost (cache + visible-item cap) ...

The chat panel rebuilt every renderable on each WS event, including
per-token stream_delta — so markdown was re-parsed for the entire history
on every token and the TUI lagged as conversations grew.

- Cache renderables keyed by id(item)+signature so only the changed item
  (the streaming assistant bubble) is rebuilt per token; the rest are
  reused. Prune orphaned entries so cache stays bounded by live items.
- Add max_visible_items TUI setting (default 200): render only the last
  N items with a "… N earlier messages not shown" hint when truncated.
  Items stay in the in-memory model (non-destructive) but are not laid
  out, so per-refresh cost is constant regardless of history length.
- Rename the cache attr to _chat_render_cache to avoid collision with
  Textual Widget._render_cache, which it resets on mount.

Co-Authored-By: Claude <noreply@anthropic.com>

Navi Code TUI: sub-agent spawn card + nested styling for subagent thinking/planning ...

Sub-agent activity was either rendered as a generic tool card (spawn_agent) or
dropped to raw debug output (turn_thinking was unhandled in the TUI chat model
and the raw CLI). The webclient nests subagent events inside the spawn_agent
card; the TUI is flat, so nesting is conveyed with a distinct spawn card plus
left-indented, dimmed subagent cards.

New renderers/subagent.py:
- SpawnAgentStartedRenderer: "↘ subagent · <profile_id>" card showing the task
  (+ briefing dimmed), secondary border. Registered before ToolStartedRenderer.
- SpawnAgentResultRenderer: "↙ subagent · <profile_id> ✓/✗" card with the
  result, success/error border. Registered before ToolResultRenderer.

Nested subagent styling (left indent via Padding + dim):
- ThinkingRenderer: is_subagent → "subagent thinking" title, dim border, indented.
- PlanningStatusRenderer / PlanReadyRenderer: is_subagent → indented (label/title
  already mark it as subagent).
- ToolStartedRenderer / ToolResultRenderer: is_subagent → indented so inner
  tool calls read as nested inside the spawn card.

chat_model handles turn_thinking → thinking_block item with is_subagent meta;
chat_panel._refresh forwards is_subagent to the thinking renderer. Raw CLI
render.py prints turn_thinking as a [thinking] block (with "(subagent)" prefix).

Tests: spawn card shows profile/task and status; subagent thinking/planning/tool
cards are indented and labeled; non-subagent tool card is not indented;
turn_thinking creates a subagent thinking_block. 593 passed, 1 skipped.

Co-Authored-By: Claude <noreply@anthropic.com>

Navi Code: render planning as a progress line + plan card, not raw events ...

planning_status and plan_ready events were unhandled in the TUI chat model and
the raw CLI renderer, so they fell through to raw debug output (TUI:
"plan_ready: {...}" status lines; raw CLI: "[event: plan_ready] {msg}").

TUI:
- New renderers/planning.py: PlanningStatusRenderer renders a "⚙ Planning ·
  <label>" line (info color; dim + "(subagent)" prefix for subagent planning);
  PlanReadyRenderer renders the plan as a Panel wrapping themed Markdown, titled
  "Plan" with an accent border ("subagent plan" + dim border for subagents).
- Registered both in default_registry().
- chat_model handles the events: non-subagent planning_status rolls in place
  (Analysis → Execution plan → Plan review share one line instead of stacking);
  plan_ready consumes the pending planning line and appends the plan card;
  subagent planning is appended as its own dim line/card so it does not bleed
  into the parent turn's indicator (matching the webclient).
- chat_panel._refresh maps the new kinds to the registry.

Raw CLI (render.py): planning_status prints "[planning] <label>"; plan_ready
prints a "[plan] … [/plan]" block with the plan text.

Tests: renderer accepts/render (label, subagent prefix, plan title/content);
chat_model rolling-in-place, plan_ready consumes indicator, subagent separation.
584 passed, 1 skipped.

Co-Authored-By: Claude <noreply@anthropic.com>

Navi Code TUI: drop forced line break, keep soft-wrap + Enter to send ...

The forced line break (Ctrl+Enter) never worked: the target terminal does not
distinguish any modifier+Enter from plain Enter — all of Ctrl/Alt/Shift+Enter
arrive as key='enter' character='\r' (verified via a one-off key probe). With
Enter bound to submit, any modifier+Enter newline binding would collide with
submit and is impossible to distinguish in software.

Remove the Ctrl+Enter branch from _PromptInput._on_key. The input stays
multi-line via soft-wrap (TextArea soft_wrap=True) and height: auto growth;
Enter still submits. Placeholder and module docstring updated to drop the
Ctrl+Enter mention and note why a newline key is not wired (revisit later).

Tests: removed test_ctrl_enter_inserts_newline_without_submitting; kept the
multiline-submit and input-grows tests. 576 passed, 1 skipped.

Co-Authored-By: Claude <noreply@anthropic.com>

Navi Code TUI: make the message input multi-line ...

InputBox used textual.widgets.Input, a single-line widget. Swap to TextArea so
the prompt is genuinely multi-line: soft-wrap is on, the field grows with content
(height auto, min 3, max 12, then internal scroll), and Enter no longer collides
with newline insertion.

_PromptInput(TextArea) intercepts keys in _on_key before TextArea's own handler
(which maps enter -> "\n"):
- Enter      -> submit: post UserSubmitted(text), then clear the field.
- Ctrl+Enter -> insert a hard line break.

Dropped dead set_prompt_char (referenced a non-existent self._prompt) and the
on_input_* handlers (submit now lives in the subclass). CSS selectors updated
from Input to TextArea. Placeholder notes the keybindings.

Tests: _input.value -> _input.text across the TUI suites; added Ctrl+Enter
inserts a newline without submitting, Enter submits the full multi-line buffer
(newlines preserved) and clears the field, and the input height grows with
content. 577 passed, 1 skipped.

Co-Authored-By: Claude <noreply@anthropic.com>

Navi Code: stop via Esc + project cwd propagation ...

- TUI: Esc stops active stream cooperatively via POST /sessions/{id}/stop
- TUI: render stream_stopped as status message
- CLI/WebSocket: send shell cwd in client->server message field
- Orchestrator stores cwd in session.session_metadata
- ContextBuilder injects [Working directory] into LLM context
- Agent sets current_working_directory ContextVar per turn
- tools/base: ToolContext gains cwd field
- filesystem/terminal/code_exec resolve relative paths against session cwd
- Add bin/navi-code wrapper for PATH symlink; document in README.md
- Update docs/websocket.md and tests

Full pytest: 544 passed, 1 skipped.

Co-Authored-By: Claude <noreply@anthropic.com>

Navi Code TUI: fix input box layout, command palette duplicate IDs, status renderer, and WS input loop ...

- clients/terminal/tui/widgets/input_box.py: switch Horizontal to Vertical with width: 100% for Input so it renders and accepts input in real terminals; add refresh on Input.Changed.
- clients/terminal/tui/screens/command_palette.py: remove fixed ListItem IDs to avoid DuplicateIds on fast filter.
- clients/terminal/tui/chat_model.py + renderers/status.py + widgets/chat_panel.py: render backend status events as dim system messages instead of raw dicts.
- clients/terminal/tui/ws_bridge.py: start NaviWebSocketClient.input_loop so enqueued user messages are actually sent to the backend.
- clients/terminal/tui/tui_app.py: focus InputBox synchronously in on_mount so typing works immediately.
- tests/clients/test_tui_app.py: regression test for visible input text.

Co-Authored-By: Claude <noreply@anthropic.com>

Navi Code TUI: review fixes for Phase 5 ...

- Fix raw CLI session API fields (session_id/name/preview)

- Add --mouse/--no-mouse flags and persistent TUI settings coercion

- Make attach_session/apply_theme public, add ChatPanel.clear()

- Deduplicate session selection handlers and editor error handling

- Update docs and tests

Navi Code TUI: Phase 5.2 — SessionsPanel, /export, integration tests ...

- Add right-side SessionsPanel widget (DataTable) listing server sessions.
- Wire SessionsPanel into TUI layout and session selection flow.
- Add SessionSelected / SessionListUpdated events and refresh logic.
- Implement /export slash command: markdown rendering + $EDITOR.
- Update /new, /sessions, /switch, /profile to use session_id/name/preview.
- Add integration tests for SessionsPanel and /export; update layout test.
- Update docs/navi_code_cli.md with new panel and command.

Co-Authored-By: Claude <noreply@anthropic.com>

Navi Code TUI: Phase 5.1 — config, mouse, themes, status ...

- Add TuiSettings persisted in ~/.navi_code/tui.json (theme, mouse, scroll_speed, diff_style, keybinds).
- TUI applies saved theme/mouse on startup; CLI gets --theme override.
- Add /themes picker with live preview and /mouse toggle command.
- Extend StatusPanel with backend URL, current theme, tokens/iter placeholders.
- Fix TuiContext.app() to use Textual active_app ContextVar.
- Add unit tests for settings, themes, and status panel.

513 passed, 1 skipped. Ruff clean.

Signed-off-by: Eugene Sukhodolskiy <eugene.sukhodolskiy@gmail.com>

Navi Code TUI: apply gnexus theme to widgets and renderers ...

- Register Navi themes as Textual themes so $tui-* CSS variables resolve.

- Update ChatPanel, StatusPanel, InputBox to use palette colors.

- Update all content renderers to draw from the active theme.

- Add set_active_theme/get_active_theme helpers for runtime color access.

Co-Authored-By: Claude <noreply@anthropic.com>

Navi Code: Phase 3 — Textual TUI skeleton (OpenCode-style) ...

- Add clients/terminal/tui package with micro-architecture:
  - events, context, chat_model, ws_bridge, permissions engine.
  - widgets: ChatPanel, StatusPanel, InputBox.
  - renderers: user/assistant messages, thinking, tool calls, errors,
    markdown, plain — registry-based and extensible.
  - slash commands: /help, /new, /sessions, /switch, /profile, /thinking,
    /compact, /quit — registry-based and extensible.
- Wire navi-code to launch TUI by default; keep click-CLI via --raw.
- Add textual>=0.70 dependency.
- Add TUI smoke tests via Textual Pilot.
- Add docs/plan_navi_code_tui.md with full Phase 4/5 roadmap.

Tests: 463 passed, 1 skipped (excluded unrelated websocket test).

Co-Authored-By: Claude <noreply@anthropic.com>