Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

session-flow: continue-in-background dirty-tree gate ignores worktree.bgIsolation

Open Beginner friendly
  • Is something wrong?
#7,288 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
git, shell
Domain
tooling

Research direction

Read plugins/session-flow/skills/continue-in-background/SKILL.md, especially step 1, “Dirty-tree gate,” and compare how the source-control plugin reads the setting in plugins/source-control/hooks/worktree-create-gate.sh. Update the gate and launch report to account for worktree.bgIsolation set to none; verify the refusal reason and warning match the issue’s expected behavior.

Written by the indexing model from the issue text.

Description

needs-triage priority: medium

Summary

/session-flow:continue-in-background's dirty-tree gate assumes a background session always moves into an isolated git worktree before editing, unless the current session is already in a linked worktree. The worktree.bgIsolation setting can turn that isolation off, and then the background session edits the working copy directly. The gate does not read the setting, so its reasoning and outcome are wrong in that configuration.

Affected area / component

plugins/session-flow/skills/continue-in-background/SKILL.md (step 1, "Dirty-tree gate")

Steps to reproduce

  1. In a git repository, set "worktree": {"bgIsolation": "none"} in .claude/settings.json.
  2. Leave an uncommitted change in the checkout.
  3. Run /session-flow:continue-in-background.

Expected behavior

The gate accounts for worktree.bgIsolation. With isolation off, the launched session sees the uncommitted changes, so the "changes won't carry over" reason for refusing does not apply. The real risk is different: the background session and the user would edit the same checkout at the same time, and the launch report should say so.

Actual behavior

  • SKILL.md:124-130: "Background sessions move into an isolated git worktree (a fresh checkout) before editing files (https://code.claude.com/docs/en/agent-view), so OTHER uncommitted changes in this checkout would NOT carry into the launched agent's edits. Any such changes → do NOT launch". The only exception is a session already inside a linked worktree.
  • Live docs, https://code.claude.com/docs/en/agent-view#how-file-edits-are-isolated (read 2026-10-12): "To turn off worktree isolation for a repository where git worktrees are impractical, set worktree.bgIsolation to "none". Background sessions then edit your working copy directly without moving into a worktree first." The same section lists other skip cases (a session moved to the background with /background, a write outside the working directory).
  • Nothing in plugins/session-flow/ mentions bgIsolation (grep -rn bgIsolation plugins/session-flow returns nothing). The source-control plugin already names the setting (plugins/source-control/hooks/worktree-create-gate.sh:64).

Suggested fix

Read the effective worktree.bgIsolation value before the dirty-tree check. When it is "none", skip the "changes won't carry over" refusal and instead warn that the launched session will edit this checkout in place, alongside the user. This is a gate-logic change, not a pointer fix.

Environment

session-flow on main as of 2026-10-12.

Found during the upstream-pointer sweep (PRs #7061-#7274).

Dominant language
Shell
Stars
22
Forks
2
Avg merge
6h 42m
Merged PRs (30d)
902

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from melodic-software/claude-code-plugins

All issues in melodic-software/claude-code-plugins

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.