You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
treehouse worktree pool is shared across firstmate homes by project name, so sibling homes collide on slots #4977
The treehouse worktree pool is keyed only by project name (~/.treehouse/<project>-<hash>), not by the firstmate home that asked for it. In a fleet where the main home and one or more secondmate homes each hold their own clone of the same project, they share one pool. A slot handed to home B can already be registered to home A's clone (a different git dir), so the spawn refuses.
Reproduction
Main home with projects/qc-app cloned; a secondmate home with its own projects/qc-app clone (same project name).
Main home dispatches a task on qc-app: treehouse allocates worktree slot 1 in ~/.treehouse/qc-app-<hash>, bound to the main clone's git dir.
Secondmate home dispatches a task on qc-app: treehouse get picks the lowest-numbered slot in the same pool, finds slot 1 registered to a different git dir, and fm-spawn refuses:
spawn for qc-intake-r1 refuses - the treehouse worktree pool at ~/.treehouse/qc-app-fcc8c2 is shared across firstmate homes by project name; its worktree 1 is currently registered under a different git dir
Observed three times in one day on one fleet (two on a suite secondmate, one on a qc-app secondmate); the only workaround was pruning the colliding slots by hand from the other home.
Fix
#4932 gives each firstmate home its own pool root, with tests modelling the per-home root and a live end-to-end test proving two homes on one project no longer collide. Validated locally with ShellCheck, actionlint and the test suite.
Verdict:ready-for-pr · contract-class: restore · Firstmate flag: no
Tip check (dd9b2ef): Tip still sends plain treehouse get (no per-home --root). fm_treehouse_pool_slot only checks pool-state + shared git-common-dir with the spawning clone — so sibling homes with separate clones of the same origin still compete for one ~/.treehouse/<project>-<hash> pool and hit the isolation refusal. Open PR #4932 (fix(bin): give each firstmate home its own treehouse worktree pool root, head 3dcbcf7371ea21e0d9b6e5f35596ac4a6b327d9c) is the existing fix path — not merged. No competing PR from firstmate.
VISION (per-rule):
Delegation with a spine: secondmate/main homes on the same project are an existing fleet shape; a shared pool that refuses spawn breaks that path.
Restart / durability: hand-pruning colliding slots is not an acceptable standing workaround.
Scope: keep worktree isolation honest across homes without nesting pools inside project or home checkouts.
Aligns. contract-class: restore (multi-home same-project spawn is a concrete default path currently broken by shared pool identity).
Leave open; help existing #4932 through PR triage when ready. Issue stays ready-for-pr until that lands on main.
I hit this running main + secondmate homes on the same project name: treehouse keyed pools by origin only, so homes shared ~/.treehouse/<project>-<hash> and fm-spawn refused foreign git dirs.
Built:#4932 — each FM_HOME gets its own treehouse pool root; rebased onto current main (903fc30), mergeable. Local isolation tests green; Actions may need maintainer workflow approval on the fork PR.
Ready for review/merge when CI is allowed. Happy to address nits.
Verdict:existing-pr → #4932 · contract-class: restore · Firstmate flag: no
Tip check (3c14a54): Tip still sends plain interactive treehouse get (no per-home --root). No fm_treehouse_home_root helper. fm_treehouse_pool_slot still only checks shared git-common-dir with the spawning clone — sibling homes with separate clones of the same origin still compete for one ~/.treehouse/<project>-<hash> pool. Open PR #4932 (fix(bin): give each firstmate home its own treehouse worktree pool root, head 903fc3077ed298be036f0ff859b40aa1b49f56ad) remains the covering help; reporter follow-up confirms it is rebased and mergeable pending CI/workflow approval. Not fixed on tip; do not open a competing PR.
VISION (per-rule): multi-home same-project spawn is an existing fleet shape; a shared pool that refuses spawn breaks that path; hand-pruning slots is not a standing workaround. Aligns. contract-class: restore.
Keeping existing-pr. Help #4932 through PR triage; restamp only — no new ready-for-pr work.
Activity
kunchenguid commentedon Sep 20, 2026
Speaking as Kun's firstmate:
Verdict:
ready-for-pr· contract-class: restore · Firstmate flag: noTip check (dd9b2ef): Tip still sends plain
treehouse get(no per-home--root).fm_treehouse_pool_slotonly checks pool-state + shared git-common-dir with the spawning clone — so sibling homes with separate clones of the same origin still compete for one~/.treehouse/<project>-<hash>pool and hit the isolation refusal. Open PR #4932 (fix(bin): give each firstmate home its own treehouse worktree pool root, head3dcbcf7371ea21e0d9b6e5f35596ac4a6b327d9c) is the existing fix path — not merged. No competing PR from firstmate.VISION (per-rule):
Aligns. contract-class: restore (multi-home same-project spawn is a concrete default path currently broken by shared pool identity).
Leave open; help existing #4932 through PR triage when ready. Issue stays
ready-for-pruntil that lands on main.devin-ai-integration commentedon Sep 24, 2026
mehulbhagwani commentedon Sep 25, 2026
Reporter follow-up — work complete on my side
I hit this running main + secondmate homes on the same project name: treehouse keyed pools by origin only, so homes shared
~/.treehouse/<project>-<hash>andfm-spawnrefused foreign git dirs.Built: #4932 — each
FM_HOMEgets its own treehouse pool root; rebased onto current main (903fc30), mergeable. Local isolation tests green; Actions may need maintainer workflow approval on the fork PR.Ready for review/merge when CI is allowed. Happy to address nits.
kunchenguid commentedon Sep 25, 2026
Speaking as Kun's firstmate:
Verdict:
existing-pr→ #4932 · contract-class: restore · Firstmate flag: noTip check (3c14a54): Tip still sends plain interactive
treehouse get(no per-home--root). Nofm_treehouse_home_roothelper.fm_treehouse_pool_slotstill only checks shared git-common-dir with the spawning clone — sibling homes with separate clones of the same origin still compete for one~/.treehouse/<project>-<hash>pool. Open PR #4932 (fix(bin): give each firstmate home its own treehouse worktree pool root, head903fc3077ed298be036f0ff859b40aa1b49f56ad) remains the covering help; reporter follow-up confirms it is rebased and mergeable pending CI/workflow approval. Not fixed on tip; do not open a competing PR.VISION (per-rule): multi-home same-project spawn is an existing fleet shape; a shared pool that refuses spawn breaks that path; hand-pruning slots is not a standing workaround. Aligns. contract-class: restore.
Keeping
existing-pr. Help #4932 through PR triage; restamp only — no new ready-for-pr work.fix(bin): isolate per-home Treehouse pool roots