Claude panel: Windows support and per-project chat history saved in the .kadr

[dvgmdvgm]

Two commits, reviewable separately.

1. Claude panel: run on Windows, paste into the terminal

The embedded session was POSIX-only (/bin/sh -c command -v, a /bin/bash watchdog, kill(-pgid)), so on Windows the panel failed at once with File not found.

• the command is found with where, taking the first hit with a runnable extension — npm puts an extensionless sh shim next to claude.cmd, and CreateProcess cannot run it
• claude runs directly in the pty (no bash, no process groups); a hard Electron death closes the pseudoconsole, which ends what is attached to it
• closing kills the whole tree (shim → claude → MCP servers) with taskkill /t /f
• Ctrl+V pastes instead of sending ^V, and right-click copies a selection or pastes (Electron has no context menu), as in Windows Terminal

2. Per-project chat history, saved inside the .kadr

Until now every panel open started a blank claude, so the assistant had no memory of the edits it had made. Now a project owns its chats:

• Project.claudeChats holds the session ids. The panel resumes the newest one (--resume), or starts a new one with a known id (--session-id).
• The header gets a chat picker (title + date) and a New chat button. The usage hint moves into the header's tooltip.
• Save and autosave embed the transcripts into the project file as claudeTranscripts: {id: jsonl}. project:read takes them out again and keeps them in main, so they never reach the renderer, whose project is deep-copied on every edit.
• Claude Code resumes only from <config>/projects/<slug of cwd>/<id>.jsonl, so right before a resume the longest known copy is written there. A chat begun in an unsaved project, in another folder or on another machine therefore still resumes.
• A chat joins the project on the user's first keystroke or paste in it, as a new project object. The unsaved dot and autosave then see that the file's copy is behind, and opening and closing the panel leaves no empty chats.
• Undo/redo carry the current chat list over, because a chat is not an edit. The panel is keyed by project id, so opening another project brings up its own chats. On Windows a close waits for taskkill, so a quick A→B→A switch never has two claudes writing one transcript.

Heads-up — privacy: a .kadr now carries its chat transcripts, so sharing the project file shares the conversations too.

Not tracked (documented in CLAUDE.md): a session switched inside the TUI (/clear, /resume) gets an id the panel never sees, so New chat is the supported way to start a new conversation. With an args override in claude-env.json no chat flags are added, because the override may run something that is not claude.

Checks

• node scripts/check-chats.mjs (new; no app, no network, uses a temp CLAUDE_CONFIG_DIR) → 16/16 pass
• the other four check-*.mjs pass; tsc is clean on both configs
• Live walk over CDP on Windows 10 / Electron 42, using a crafted transcript so no tokens were spent → 14/14 pass:
  • save embeds the transcript; open keeps it out of the renderer
  • the panel lists and resumes the chat after Claude's own copy was deleted
  • the first key marks the project unsaved
  • New chat starts a new session, and it is recorded only after input
  • A→B→A leaves one claude; undo keeps the list
  • opening another project restarts the panel on that project's chats
  • nothing survives a close; autosave embeds too
• Before the Windows fix the panel failed with File not found; after it, the TUI opens and the kadr MCP bridge answers kadr_state. Ctrl+V and right-click deliver the clipboard as a bracketed paste, where before they sent ^V and nothing.

Not run: the e2e*.mjs suites. They are Linux-oriented (/tmp, $HOME/.config/kadr, gen-test-media.sh) and were not run here.

🤖 Generated with Claude Code