openai / openai/codex

Feature request: authenticated cross-engine permanent-session delivery and receipts

Open
#44,662 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app app-server enhancement
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Request

Is there an existing supported integration for authenticated, bidirectional delivery between registered permanent Codex and Claude workbench sessions?

If not, please consider a documented desktop/agent integration that provides:

  1. Resolve a registered permanent session by engine and stable identity.
  2. Send a compact assignment to one exact recipient using an idempotency key.
  3. Reconcile an assignment by that key and return the provider attempt/message identity.
  4. Read one bound recipient event/turn receipt so the sender can distinguish delivery, acceptance, and execution.
  5. Document per-call and end-to-end timeout/cancellation behavior.
  6. Enforce sender/recipient/lane authorization so capability does not become arbitrary messaging.

Why this matters

Today, the exposed Codex thread tools can message Codex tasks, but we do not see an equivalent supported Claude session resolver, sender, or receipt-readback interface. The Claude CLI resume flow is not an acceptable substitute because it can copy a running session and does not provide authenticated recipient or execution evidence.

We need to know whether a supported integration already exists before building anything. This request contains no customer data, credentials, local paths, transcripts, or internal session identifiers.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The payload names no files or tests. Start by reviewing the exposed Codex thread tools and the Claude CLI resume flow described in the request. Compare them with the requested resolver, delivery, reconciliation, receipt, timeout, cancellation, and authorization behavior; done means establishing whether a supported integration exists or documenting the required integration scope.

Written by the indexing model from the issue text.

Assessment

Domain
api, authentication, cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.