git:20260614.c685c4b to git:20261105.b0942c0

13 added, 6 removed. Audit A to A.

---

name: cf-session

description: >

- Continue or branch Codex conversations with the native session controls. Use when the user

- asks to resume, continue, fork, or restore a Codex session. Codex owns its transcript format,

- so Coding Friend does not copy or rewrite session JSONL files.

+ Continue or branch Codex conversations with the native session controls, and list, read or

+ export (redacted) Codex sessions with the Coding Friend CLI. Use when the user asks to resume,

+ continue, fork, restore, list or export a Codex session.

---

# $cf-session

Codex provides native session management:

- Use `/resume` in the TUI or run `codex resume` to continue a saved conversation.

- Use `/fork` in the TUI or run `codex fork` to branch a conversation.

- Use `/archive` to archive the current conversation without deleting its transcript.

- Do not run Coding Friend's Claude session scripts or parse Codex session files. If the user

- needs cross-machine continuity, explain that native Codex session availability is the supported

- path and keep durable project knowledge in `docs/memory/`.

+ The Coding Friend CLI reads Codex sessions (it never writes them):

+ - `cf session list --json --provider codex` lists them, newest first (`--provider` exists

+ only on `list`).

+ - `cf session show --json -- codex:<thread-id>` prints one session's turns, redacted.

+ - `cf session export --json -- codex:<thread-id>` exports it as redacted Markdown (tool output

+ left out by default; redaction is best effort, so read it before sharing).

+ There is no save or load for Codex sessions: to continue one, use `codex resume` or

+ `codex fork`. Keep durable project knowledge in `docs/memory/`.