Repository navigation
[bug] --continue can append to another project session when paths collide #156
Description
Activity
This comment was generated by AI during triage.
The collision mechanism is visible in source — verified below.
Verification (against current
main)packages/coding-agent/src/core/session-manager.ts:476-481encodes cwd into the session directory name by replacing every/,\and:with-:/tmp/case/project-aand/tmp/case/project/aboth map to the same directory, so the two projects share one session dir and--continue's newest-file pick can cross projects regardless of the headercwd.
Fix direction: a collision-free encoding (e.g. hash suffix) plus honoring header
cwdon continue. Maintainers will follow up.- added a commit that references this issue
on Oct 9, 2026
What happened?
step --continuecan open and append to another project's session. The paths/tmp/case/project-aand/tmp/case/project/aboth map to the same default session directory.list()shows both projects' sessions and--continuepicks whichever file is newest, ignoring its headercwd. This mixes conversation history and can modify the wrong project's session file. Reproduced 5/5 times oncb5fc14with extensions disabled.Steps to reproduce
STEP_CODING_AGENT_DIR, withSTEP_CODING_AGENT_SESSION_DIRunset.project/asession newer.project-a, list sessions and continue the latest one. Both sessions appear; continue opens theproject/afile. A new message fromproject-ais appended to that file.Expected behavior
Current-project listing and continue should match the session header's actual
cwd; a colliding directory name must not select a foreign session. I can implement the fix.Version
0.84.4