4 Commits

Include renames

Author	SHA1	Message	Date
jpmschweitzerandClaude Opus 4.7	5fad8dc430	deliver slash commands typed so the Claude TUI runs them ... The composer routed everything through tmux paste-buffer -p (bracketed paste), and Claude's TUI deliberately doesn't parse a leading slash on pasted input — so /command and /skill arrived as literal text instead of running. Now a recognised command (single-line, leading slash, token in ClaudeConfig's slash list) is delivered via send-keys -l (typed) so the TUI fires it; everything else keeps the bracketed-paste path, which also leaves a stray leading slash (e.g. a /tmp path) as literal text rather than mis-parsing it. The slash list is warmed lazily when a Claude pane opens so custom commands are recognised. T-153. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-23 12:35:53 +02:00
jpmschweitzerandClaude Opus 4.7	f65ef50379	fix Claude secondary pane copy + false "session exited" ... Two things surfaced in the secondary pane: the tab said "session 1" while the banner said "secondary 1" — now both say "session N". And the banner showed "session exited" right after starting, even though Claude was alive: a transient tmux client process can exit during spawn while the session itself is fine. pane.exit now verifies via `tmux has-session` and only reports exited when the session is actually gone. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-23 09:48:26 +02:00
jpmschweitzerandClaude Opus 4.7	6910c79e5b	submit composer input via tmux server, not the detached client PTY ... The composer sent input with pane.write, which writes to the PTY of the tmux client the app spawned. That client detaches (we no longer render or drain its PTY since T-137), leaving the session alive on the server with no client — so keystrokes written to the dead PTY vanished and Claude never saw the message. Submit now goes through the tmux server: load the text into a named paste buffer, paste it bracketed (multi-line and special chars arrive as one block, not a stream of submits), then send Enter. Verified against a live session — paste-buffer -p reaches Claude's input with no client attached. The no-tmux fallback still uses pane.write (claude runs directly in our PTY there). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-23 00:01:43 +02:00
jpmschweitzerandClaude	6601056972	finish T-87: cold-start reap, kill-all-sessions, helper tests ... Three remaining acceptance criteria for T-87: 1. Cold-start reap. The Claude extension's activate() now kills every leftover secondary tmux session for the current repo before any new spawn. activate runs before any UI mounts, so _nextSecondary's starting value of 1 is correct even when a previous run died abruptly (kill -9, OOM, force-quit). The deactivate() hook also calls reapSecondaries as a courtesy on explicit extension teardown — but Flutter's deactivate doesn't fire on app quit, so activate is the load-bearing path. 2. claude.kill-all-sessions actually kills server-side. The command previously called pane.close on every claude pane, which only kills the tmux client. It now also calls tmux.killAllForRepo to kill the sessions on the clide socket. 3. Tests. test/builtin/claude/tmux_session_test.dart covers killSession, listClideSessions, reapSecondaries, and killAllForRepo via the TmuxRunner override — no real shell-out in tests. Co-Authored-By: Claude <noreply@anthropic.com>	2026-05-06 16:48:06 +02:00