Feature Request: Expose Codex session ID for resuming previous sessions

[sarices]

Problem

Related to #493 (which covers Claude sessions), the same issue exists for Codex sessions started via Paseo.

Codex CLI supports codex --resume <session-id> to continue a previous session, but Paseo does not expose the Codex session ID through its CLI or UI. This makes it impossible to resume a Codex session from outside Paseo (e.g., directly in the terminal or from another device).

Currently:

• paseo ls --json does not return a sessionId field
• paseo inspect <id> --json also lacks session ID information
• The session ID may exist in Paseo's local storage, but there's no documented way to access it for Codex sessions

Use case

1. Cross-device workflow: Start a coding session on mobile via Paseo, then want to resume it in a native Codex terminal on desktop
2. Paseo downtime: If Paseo daemon is stopped or the app crashes, users lose the ability to continue where they left off using native Codex CLI
3. Flexible tooling: Users may want to switch between Paseo's UI and native Codex CLI depending on the task, without losing context

Proposed solution

Expose the Codex session ID in:

• paseo ls --json output (add a sessionId field)
• paseo inspect <id> --json output
• Agent detail view in the desktop/mobile app

Bonus: A paseo resume <id> command that wraps codex --resume <sessionId> would be even better.

Context

This would make Paseo a true orchestration layer that doesn't lock users in — consistent with the project's philosophy of managing existing agent CLIs rather than replacing them.

[boudra]

hey, will look into exposing it in the CLI

but i want to point out that we have a "Copy resume command" option in the agent tab context menu, works for both CC and Codex