Bug type
Incorrect behavior or output
Summary
With an auto-mode agent running in one terminal, and using /gsd steer in another terminal, it's possible for the steering instructions to end up modifying the project-level files and not what's in the worktree, leading the auto agent to never see the steering instructions and continue on as if they never happened.
Steps to reproduce
With worktree isolation - create milestone, begin auto mode, in second terminal, provide steering instructions on the current slice.
Expected behavior
Auto-mode agent should get the steering instructions.
Actual behavior
New context is written outside worktree, agent never sees it.
GSD version
.58
Node.js version
v24.14.0
Operating system
Kubuntu 24
Install method
npm global install
Affected area
Git / worktree isolation
Model and provider
No response
Logs, screenshots, and evidence
From the agent in the steering session when I tried to steer again to ensure the instructions were being followed:
The worktree has the old context too. The context I wrote with the new
architecture was written to the main .gsd/ directory, not the worktree. But more
importantly, S01 has already been completed with the wrong architecture.
Impact
Severity: High, user instructions ignored
Additional information
No response
Bug type
Incorrect behavior or output
Summary
With an auto-mode agent running in one terminal, and using /gsd steer in another terminal, it's possible for the steering instructions to end up modifying the project-level files and not what's in the worktree, leading the auto agent to never see the steering instructions and continue on as if they never happened.
Steps to reproduce
With worktree isolation - create milestone, begin auto mode, in second terminal, provide steering instructions on the current slice.
Expected behavior
Auto-mode agent should get the steering instructions.
Actual behavior
New context is written outside worktree, agent never sees it.
GSD version
.58
Node.js version
v24.14.0
Operating system
Kubuntu 24
Install method
npm global install
Affected area
Git / worktree isolation
Model and provider
No response
Logs, screenshots, and evidence
From the agent in the steering session when I tried to steer again to ensure the instructions were being followed: The worktree has the old context too. The context I wrote with the new architecture was written to the main .gsd/ directory, not the worktree. But more importantly, S01 has already been completed with the wrong architecture.Impact
Severity: High, user instructions ignored
Additional information
No response