[Feature]: Worktree Conversations on Board

[thomas-intramotev]

Problem

When I use Claude Code's Worktrees feature--e.g. by starting the CLI with the --worktree flag--the resulting conversation doesn't show up on Claudine.

Proposed Solution

When scanning a monitored workspace, also check for a .claude/worktrees/ directory and treat each subdirectory as an additional workspace to scan. The worktree name can be surfaced on the conversation (e.g. as a badge or metadata field) so it's clear which worktree a conversation belongs to.

Something like a claudine.monitorWorktrees toggle (default: on) could act as a modifier on the claudine.monitoredWorkspace setting, essentially meaning "look for any worktrees under all monitored workspaces."

Alternatives Considered

I can move an existing conversation in the Claude Code VS Code extension to a new worktree by telling the agent e.g. "in a new worktree...", and it will persist in Claudine (presumably because the .jsonl file is still in the 'base' project folder), but other (non-worktree) conversations started from the CLI normally appear in Claudine. It would be nice to be able to claude --worktree <worktree-name> via the same workflow and have that appear in Claudine.

Additional Context

No response

[thomas-intramotev]

Tricky thing: I've been trying to implement this myself, and while it's fairly straightforward to get worktree conversations to appear on the Kanban board, the problem is in resuming them from their card on the board.

It's currently a known limitation of Claude Code that a conversation ID is insufficient to resume a conversation started with the --worktree flag: you need to use both the --resume and --worktree flags to resume such threads.

As far as I can tell: there is currently no way to pass the --worktree argument to a new Claude Code editor tab. A possible workaround is to introduce the "Open Menu" functionality to Editor mode and let users fallback to opening the conversation in an external (or even the integrated VS Code) terminal.