extract-chat-session

To extract context and pending work from a Codex chat session, provide one or more session-id values to generate a structured continuation packet. This packet consolidates workspace paths, completed work, and open loops into a ready-to-run format for seamless thread resumption.

You can merge multiple Cursor chat sessions into a single continuation plan by providing multiple session-id values. The skill normalizes the session IDs and consolidates their memory, decisions, and open loops into one execution lane with explicit assumptions and recommended next actions.

A chat session continuation packet is a structured output that aggregates memory and pending work from chat transcripts. It includes fields such as provider, session_id, workspace_paths, artifact_paths, completed_work, open_loops, and recommended_next_actions for immediate execution.

Recovering workspace paths and artifact references from chat transcripts is handled automatically during session extraction. The skill aggregates these references along with key outputs and decisions to ensure your next executable actions have the correct file context.

No external dependencies or specific environment setup are required to extract chat sessions. You simply need to provide the session-id values from your Codex or Cursor workspace to generate the continuation packet.

The best way to prepare a chat transcript handoff is to extract memory and open loops using session IDs. This generates a continuation packet with explicit assumptions and recommended next actions, ensuring the new thread has all necessary workspace and artifact context.