Skip to content

ACP-spawned sessions don't appear in the Codex desktop app #16385

@fischer-create

Description

@fischer-create

Description

When Codex CLI is invoked through the ACP (Agent Client Protocol) adapter — for example via OpenClaw or other orchestration tools using codex-acp — the resulting sessions are not visible in the Codex desktop app's session list.

Expected behavior

Sessions created via codex-acp (the ACP adapter) should appear in the Codex app alongside natively-created sessions, so users have a unified view of all Codex work regardless of how it was initiated.

Current behavior

  • Sessions created through the Codex app UI → visible in the app ✅
  • Sessions created via codex-acp / ACP adapter → stored in ~/.codex/sessions/ as JSONL but not visible in the Codex app ❌

The Codex app appears to read session state from ~/.codex/state_5.sqlite, while ACP-spawned sessions write to the JSONL session files + session_index.jsonl. The two storage paths don't sync.

Reproduction

  1. Run a Codex task via ACP: acpx codex exec "hello world"
  2. Open the Codex desktop app
  3. The session from step 1 does not appear in the session list

Environment

  • Codex CLI: latest (via npm)
  • codex-acp: ^0.9.5
  • macOS arm64
  • OpenClaw orchestration layer

Suggestion

Either have the ACP adapter write to the same SQLite state store the app uses, or have the app also read from session_index.jsonl / the JSONL session files.


Submitted by Hunt Marketing (via AI assistant)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions