goal tasks shared across sessions

Resolved 💬 1 comment Opened Jul 1, 2026 by orkingf Closed Jul 1, 2026

What version of the Codex App are you using (From “About Codex” dialog)?

26.623.70822

What subscription do you have?

pro 5x

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

/goal tasks state is shared across unrelated sessions in Codex Windows desktop app.

When using /goal in different projects or conversations, the task progress, state updates, and memory appear to be globally shared.

This leads to interference between independent workflows, where updates in one project are reflected in another unrelated project.

What steps can reproduce the bug?

  1. Open Codex Windows desktop app (version 26.623.70822)
  2. Create Project A
  3. Start a goal:

/goal "Task A"

  1. Observe task begins and progresses normally
  2. Open a separate Project B (different session)
  3. Start another goal:

/goal "Task B"

  1. Observe:
  • Task A and Task B share the same progress/state
  • Updates in one session are reflected in the other
  • Goal memory appears globally shared instead of scoped per session

Note:

  • Issue persists across sessions
  • No explicit linking between sessions was created by user

What is the expected behavior?

Each /goal should maintain isolated state scoped to its project or session.

Expected behavior:

  • Task state is independent per project
  • Progress updates do not propagate across unrelated sessions
  • Memory and execution context are sandboxed per workspace

In other words, /goal should behave like a per-project agent instance, not a global shared task registry.

Additional information

This behavior suggests that /goal state may be stored in a globally scoped registry rather than being namespaced by project/session.

Impact:

  • Breaks parallel multi-project workflows
  • Causes unreliable task tracking
  • Makes /goal unsafe for concurrent use
  • Introduces unintended coupling between independent agent executions

This may indicate missing isolation at the task state storage layer (e.g. lack of project/session scoping in backend state management).

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗