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
workspace: a folder reached through a symlink becomes two projects and two engines #1761
2026-10-05, dev@f81638787 (dev-20261005-f816387875e5), macOS, where /tmp is a link to /private/tmp. Found in the v0.7.1 happy-path pass by three lanes independently.
One folder becomes two projects, two conversations' worth of history and two engines.
On home, /project /tmp/x, type a message, enter: home stores the project as /tmp/x.
Quit, then cd /tmp/x && codeaf. The shell resolves the folder as /private/tmp/x, so codeaf does not resume that conversation; it opens a new empty one.
Home's projects panel now lists the folder twice, and two engine hosts run, one per spelling.
The engine commands miss an engine through the link.
$ codeaf engine --status --workspace /tmp/x
no engine is holding /tmp/x on this machine
$ codeaf engine --stop --workspace /tmp/x
nothing is holding /tmp/x here
$ codeaf engine --status-all
/private/tmp/x is held by an engine: this build
--stop --workspace /private/tmp/x stops it. The same applies to any folder reached through a symlink, such as a linked ~/Code.
Replication
Deterministic (no model). On any system: mkdir d && ln -s d l. Run codeaf engine --daemon --workspace "$PWD/d", then codeaf engine --status --workspace "$PWD/l". For the project split, set /project <link> on home, then launch from the resolved path; a key of the right shape is enough.
Where
Every place a workspace or project path is taken from a person (/project, --workspace, --dir) and turned into a key: the project store keying, the engine host's workspace name, and the engine --status/--stop lookup in cmd/codeaf.
The fix
A workspace is named by its resolved path (filepath.EvalSymlinks after Abs) everywhere it becomes a key. Both spellings of one folder then reach one project, one conversation history and one engine.
Acceptance
e2e:/project <link> then a launch from <dir> resumes the same conversation.
e2e: with an engine started for <dir>, codeaf engine --status --workspace <link> reports it held, and --stop stops it.
Activity
fix(workspace): name a workspace by its resolved path
enginehost: name a host by the folder, not a spelling of it
engine: the default workspace is the same folder as the named one
tui3: the pin regression for a typed /project through a symlink
gitidentity: the path fallback is the resolved path
enginehost: the host an older build wrote for this folder is still it…
chat: conversations an older build filed under another spelling still…