Worktree sessions under a channel #50
Labels
No labels
bug
docs
enhancement
good first issue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pedromcaraujo/forge#50
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Today a channel is one repo = one tmux session, declared statically in Nix. There is no way to run a second Claude session on the same project without it editing the same checkout.
Proposal
Let a channel spawn worktree sessions: each is a
git worktreeon its own branch with its own Claude session, shown as an indented row under its channel in the sidebar, with its own status dot. No NixOS rebuild per session.<channel>~<worktree>.--url-arg. The iframe loads/<channel>/?arg=<worktree>, and the launcher script validates the arg, then attaches to it. No new systemd units, ports, or nginx routes per session./worktrees). Closing kills the session, then removes the worktree if it's clean. If it's dirty, Forge asks before forcing. The branch is always kept.worktreeDiroption. It defaults to.claude/worktrees, which is relative to the channel cwd and matches Claude Code's own--worktree. Any linked worktree of the repo is listed, so ones made withclaude --worktreeor by hand show up too.worktrees = falseto opt out.Groundwork for #40, which would start a worktree session from an issue.