In Linear, when a ticket is assigned to @Codex, the activity update response is “agent did not start”, even though the agent did start, and ran the task. I’ve tried disconnecting and reconnecting Codex, but not still not seeing Linear register that the task has started, or Codex provide updates to the issue upon completion.
I’m seeing this as more of a status-sync issue than an actual start failure, since the Codex task does start and run.
Workaround for now: if the task was created in Codex, just continue it there and link the resulting task/PR back to Linear. You can also use Linear’s “Open in coding tool” flow instead of delegating with @Codex, which seems to avoid the broken agent-status path.
For the bug itself, I’d look at the mapping between the Linear agent session and the Codex thread/task ID, especially around the recent AgentControl changes. It looks possible that the task runs normally but the started/completed lifecycle events aren’t making it back to the original Linear session.
A useful regression test would simply check:
Linear session → Codex task starts → running event → completion event → same Linear session
Happy to provide task/session IDs and timestamps from a failing run if that helps.
@davidbuilds Welcome to the forum!
@webpause22 Thanks for the reply.
This was moved from a different Discourse category to the appropriate place on the forum for discussing and documenting a Codex bug. The forum, however, is not the official issue tracker. If the problem needs to be formally reported and tracked by the Codex maintainers, the official place is the OpenAI Codex GitHub issue tracker.
For future reference please follow the posting requirements for the Codex Bugs subcategory:
I asked ChatGPT to search for the closest related issue, and it identified:
https://github.com/openai/codex/issues/47860
If that issue describes the same problem you are experiencing, consider adding a 
reaction to the GitHub issue itself, rather than only reacting to this forum topic. GitHub reactions can help the maintainers gauge how many users are affected.
If it does not match your problem closely enough, search the existing Codex issues for a better match. If you cannot find one, consider opening a new issue and include as much relevant information as possible, such as your Codex version, operating system, environment, reproduction steps, expected behavior, actual behavior, and any relevant logs or error messages.
@EricGT thank you for this guidance. I’ve the issue you listed.