Skip to content

workspace: a folder reached through a symlink becomes two projects and two engines #1761

Open

Description

@ZeroPoint95

What happened

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.

  1. On home, /project /tmp/x, type a message, enter: home stores the project as /tmp/x.
  2. 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.
  3. 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

  1. added
    bugSomething the code does that it should not
    area:sessionThe engine — turns, tasks, the toolbelt, checkpoints
    sev:seriousWrong or missing behaviour a person meets in ordinary use
    on Oct 5, 2026
  2. added 5 commits that reference this issue on Oct 9, 2026
    7bce0e2
    4f8cd37
    803cdd5
    d26cae9
    c0b1d9a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:sessionThe engine — turns, tasks, the toolbelt, checkpointsbugSomething the code does that it should notsev:seriousWrong or missing behaviour a person meets in ordinary use

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions