# Resume Any Chat

> Use when the user wants to inspect, search, normalize, resume, hand off, or optionally import local Codex, Claude, or Antigravity CLI conversation history. This skill provides a local viewer, provider-specific parsers, native resume commands, a Codex handoff flow, and an explicit experimental Codex-history import path.

- Skill: `adarshnagrikar14/resume-any-chat` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add adarshnagrikar14/resume-any-chat`
- Raw SKILL.md: https://api.skillmd.com/api/skills/adarshnagrikar14/resume-any-chat/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: adarshnagrikar14 (https://skillmd.com/u/adarshnagrikar14)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/adarshnagrikar14/resume-any-chat

---


# Resume Any Chat

Use this skill for local multi-provider chat history work across the current user's home directory:

- `Codex` from `.codex/sessions`
- `Claude` from `.claude/projects` plus `.claude/history.jsonl`
- `Antigravity` from `.gemini/antigravity-cli/brain/*/.system_generated/logs`

## Workflow

1. Default to listing useful recent sessions directly in-chat.
Show recent `Codex`, `Claude`, and `Antigravity` sessions first unless the user already named a provider/session.
The default professional list format is:
- recent `10`
- per item show:
  - `id`
  - `title`
  - `last message`
- then show exactly these next actions:
  - `Continue in Codex`
  - `Continue Native`
  - `Summarise`
  - `Import into Codex History (Experimental)`
- if session `cwd` and current workspace differ, say that briefly and suggest the safer option
- stop there unless the user explicitly picks one of those actions

2. Refresh/export the current index:

```bash
node plugins/resume-any-chat/runtime/cli.js export
```

3. Useful commands:

```bash
node plugins/resume-any-chat/runtime/cli.js latest
node plugins/resume-any-chat/runtime/cli.js latest claude --limit 15
node plugins/resume-any-chat/runtime/cli.js session claude <session-id>
node plugins/resume-any-chat/runtime/cli.js handoff antigravity <session-id>
node plugins/resume-any-chat/runtime/cli.js import-history claude <session-id>
```

Command mapping:
- `show all history`
- `show history`
- `list history`
- `show recent`
- `show me all history`

For any of the above, you must run:

```bash
node plugins/resume-any-chat/runtime/cli.js latest
```

If the user names a provider, you must run:

```bash
node plugins/resume-any-chat/runtime/cli.js latest <provider>
```

4. Launch the local 3-tab viewer when the user wants to browse sessions visually:

```bash
node plugins/resume-any-chat/runtime/cli.js serve
```

5. Prefer the safe built-in flows:
- Native resume:
  - `codex resume <session-id>`
  - `claude --resume <session-id>`
  - `agy --conversation <session-id>`
- Cross-provider continuation:
  - generate a Codex handoff packet
  - launch a fresh Codex session from that handoff
- Experimental import:
  - only when the user explicitly chooses `Import into Codex History (Experimental)`
  - import a foreign session into Codex history without replacing the safer default flows

## Rules

- Do not treat foreign-session import as the default continuation path.
  - prefer native resume or Codex handoff first
  - use experimental Codex-history import only after explicit user choice
- Do not read Antigravity token-monitor/auth cache unless the user explicitly asks for that risky path.
- Prefer `transcript_full.jsonl` over `transcript.jsonl` for Antigravity when both exist.
- If a provider session has no reliable `cwd`, do not auto-launch; return the command and the missing-cwd warning.
- `show session <provider> <id>` should include recent turns by default.
  - default: show the overview plus last `5-8` meaningful messages
  - `verbose`: include more context, including thinking/tool lines when useful
- If the user says `continue here`, do not tell them to leave the thread first.
  - Run `handoff <provider> <session-id>` without `--launch`
  - use the generated summary and handoff file as context
  - continue the work in the current Codex thread
  - do not stop at `If you want, I can...` unless the next task is genuinely ambiguous
- Never auto-resume, auto-handoff, auto-summarise, or auto-open anything immediately after listing.
  - listing is one step
  - action happens only after the user explicitly chooses it
- `Import into Codex History (Experimental)` is opt-in only.
  - add it as a selectable action
  - do not use it unless the user explicitly chooses it
- Do not answer `show all history` by describing, linking, or summarizing `state.json`.
  - `state.json` is an internal cache/export artifact
  - mention it only if the user explicitly asks for raw JSON, export files, cache debugging, or file paths
- For `show all history` and similar list requests, return the direct `latest` output itself.
  - do not replace it with totals-only summaries
  - do not ask for `provider + session id` before showing the actual list
- If the prior session already contains a clear unfinished task, continue that task directly.
  - Example: if the last unfinished ask was `show full repo structure`, start doing that
  - only ask a follow-up if multiple next steps are equally plausible or if risk requires confirmation
- The rule above applies only after the user has already chosen `Continue in Codex` or equivalent.
- Do not invent a different menu or a generic conversational close.
  - follow the list-first flow above
  - avoid endings like `If you want, I can...` when the user already asked to continue
- Avoid rigid reply menus like `tell me one of these only`.
  - accept natural requests such as `latest claude`, `show me more codex`, `continue this here`, `open the viewer`, `resume that claude one`