Codex for Linear creates delegate/session and GitHub linkback but no Codex cloud task result

What version of Codex is running?

Not sure. This is observed through the Codex for Linear / Codex cloud integration path rather than a local CLI-only run.

Which model were you using?

Not applicable / not visible from the integration surface.

What platform is your computer?

Not platform-specific from the user side. The issue appears in the cloud integration path between Linear, GitHub, and Codex cloud.

What steps can reproduce the bug?

1. Configure Codex for Linear for a GitHub-backed repository that has previously been usable from Codex cloud.
2. In Linear, mention @Codex or use Delegate > Codex on an issue that points to that GitHub-backed repository.
3. Observe that Linear can reach the Codex delegate path and creates integration artifacts such as an agent/session thread.
4. Observe that a synced GitHub issue/linkback can also be created for the Linear issue.
5. Wait for the normal pickup window.
6. Check the Linear issue and the synced GitHub issue/thread.

What is the expected behavior?

Once Linear delegation reaches Codex and the GitHub issue/linkback exists, Codex should either:

• start a Codex cloud task for the intended GitHub repository and post a task/progress/result link back to Linear or GitHub, or
• post a clear blocker explaining the missing repository/environment/account binding and the exact user/admin action needed before retrying.

What do you see instead?

The Linear delegation path appears to partially work, but no Codex cloud task result appears.

Observed pattern:

• Linear can delegate or mention Codex.
• A Codex agent/session artifact can be created.
• A synced GitHub issue/linkback can be created.
• No Codex cloud task link appears.
• No progress/result reply appears.
• No completed task artifact appears.
• No branch or PR appears.
• No explicit blocker is posted after the pickup window.

This looks similar to the environment/repository association failure family described in prior public reports such as openai/codex#3932, where cloud task creation can fail when no associated environment is available, and related Codex Cloud repository context issues such as openai/codex#12498.

The confusing part is that the integration is not failing at the first step. Linear can reach Codex and GitHub sync can occur, but the actual GitHub-backed Codex cloud task handoff/result never becomes visible.

Additional information

Public support/community signals that seem related:

• openai/codex#3932: cloud task creation failure when no associated environment is available.
• openai/codex#12498: Codex Cloud losing GitHub remote/repository context.
• A public Linear community thread about Codex Agent frequent errors includes guidance that this type of error is usually tied to missing Codex environment setup for the user.

This issue intentionally does not include private repo names, Linear workspace names, account identifiers, screenshots, logs, local file paths, legal/source material, or internal workflow details.

Requested improvement:

Please make the Codex for Linear path return a visible, actionable blocker when delegation/session/GitHub-linkback succeeds but no Codex cloud task can be started. Ideally the reply should identify whether the problem is:

• no associated Codex cloud environment,
• wrong GitHub repository mapping,
• environment owned by a different account/workspace,
• missing GitHub repository access,
• Linear account/workspace binding mismatch, or
• a backend Codex-for-Linear resolver issue.