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: add --resume <session_id> and print resume hint on TUI close ...

Closing Navi Code now tells the user the session id and the exact command to
continue it, so a session is one re-run away instead of lost to state lookup.

- cli.py: add --resume <session_id> (mutex with --new-session). Raw and TUI
  paths resolve the given id via api.get_session; a bad id is a hard error,
  not a silent new session. After app.run() returns and the terminal is
  restored, print "Session <id>" / "Resume with: navi-code --resume <id>"
  when a session is attached.
- tui_app._resolve_session: make the explicit-id branch strict — a failed
  get_session surfaces an error event and returns None instead of falling
  through to creating a new session (a --resume typo used to silently start
  a fresh session). Saved-state resume stays lenient.
- tests: resume-flag resolve/bad-id/mutex + hint format; tui strict-on-bad
  explicit id and explicit-id resume.

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

tui: show the currently-served model in the status panel ...

The status panel's Model line was fed the global ollama_default_model, not the
session/profile model, and the server never told the client which model
actually served a call. Now:

- Backends stamp the resolved model onto LLMChunk (first chunk) / LLMResponse.
  The fallback backend reports the model that survived its server+model
  priority list (may differ from the profile's first choice).
- New ModelInfo event ({"type":"model_info","model":...}) emitted once per
  turn from agent._consume_stream, re-emitted only when the model changes
  across iterations. Additive WS event — old clients ignore it.
- TUI: attach_session/switch fetch the profile's configured model (first of
  profile.model) via api.get_profile_model so the panel shows a value before
  the first request; model_info then refines it to the actually-served model.
  Not forwarded to the chat panel. raw CLI prints "[model] ...".

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 TUI: show final answer below tools, not scrolled out of view ...

The assistant answer bubble was created at stream_start (the first event of a
turn), placing it at the TOP of the turn — above the thinking blocks and tool
cards that follow. chat_panel._refresh() calls scroll_end, so the view pinned to
the bottom (tools/thinking) and the answer at the top scrolled out of view.
Users saw tool results, planning, and thinking, but not the final answer.

Fix in chat_model.handle_ws_event (client-only, no protocol/server change):
- stream_start no longer eagerly adds an empty assistant bubble; it resets the
  current-assistant pointer so the first stream_delta opens the bubble lazily
  at the position where text actually arrives.
- tool_started/tool_call reset the current-assistant pointer so the next
  stream_delta opens a fresh bubble BELOW the tool cards — the final answer
  lands at the bottom, visible after scroll_end.
- stream_end purges empty assistant/thinking bubbles and resets pointers.

Tests: stream_start creates no empty bubble; final assistant_message renders
after the last tool_call with no empty bubbles; empty bubbles purged on
stream_end. 574 passed, 1 skipped.

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

test(tui): mock backend api so TUI tests are server-independent ...

test_escape_stops_active_stream failed without a live server on :8000:
_startup calls api.create_session/get_session and _refresh_sessions calls
api.list_sessions, but only stop_session was mocked, so _ctx.session_id
stayed None. The whole file silently hit a real server (slow, flaky).

Add an autouse fixture mocking create_session/get_session/list_sessions.
Per-test stop_session mocks stay (own call lists). 571 passed, 0 failed.

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: 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>