SkillFoxx

save-session skill

Bookmarks for coding agent sessions: save one under a project name, find it later and get the resume command with its folder.

  • 60 ★ on the repository
  • Last commit
  • MIT
Skill

Minimal access

Why this level

  • The skill reads local agent sessions and writes Markdown files under `~/.agents/memories/sessions/`.
All reasons and checks

jemshit/save-sessionAuthor:jemshit

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add skills/save-session

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Minimal accessThe tool runs nothing and makes no network calls.

  • The skill reads local agent sessions and writes Markdown files under `~/.agents/memories/sessions/`.

This is third-party code. Review the repository files before installing.

What it does

save-session records the current coding agent session as a bookmark. The skill detects the session id, model and working directory and stores them under a project title you give. If the same session already has another title it asks whether to keep or replace it. When titles collide it adds the suffix `- 2`, `- 3`. Search is read-only: by title, or as a list for the current agent. The answer carries the native resume command and the directory to run it from. Bookmarks live in one Markdown file per agent under `~/.agents/memories/sessions/`.

Who it is for. People who work in Claude Code, Codex and OpenCode in parallel and a week later cannot remember which session held the useful context.

Good fit when

  • You switched tasks and want to come back to this session later by project name.
  • A few days on you need the exact resume command without hunting for an id.
  • Sessions of one repository are spread across several agents and a bookmark list shows them together.
  • Another project history sits in the folder and the session must open from the right working directory.

Not a fit when

  • You need full conversation history: a bookmark keeps only id, model and folder.
  • The agent is not on the supported list, so there is no session detection for it.
  • Sessions must be shared across machines: the files are local to the home folder.

Example request

Save this session as "heap benchmark", then list saved sessions and give me the command to resume it.

Limitations

A bookmark holds the id, model and folder, not the conversation content. Each agent has its own file because ids do not carry across agents. For Antigravity CLI newer installs still need an explicit id, and Claude Code checks an environment hint against the project transcript when one exists. The bookmark folder can be changed with `AGENTS_MEMORIES_DIR`. When detection is uncertain the skill asks instead of guessing, so saving is not always fully automatic.

How to disable. Remove the skill through your agent skill manager or uninstall the `save-session` plugin. Delete the bookmark files in `~/.agents/memories/sessions/` separately if you no longer need them.

FAQ

Which agents are supported?

Pi, Claude Code, Codex, Antigravity CLI and OpenCode. For each the skill returns its own resume command, such as `claude --resume <id>` or `codex resume <id>`.

Does it need a server or account?

No. Bookmarks are plain Markdown files on your machine and the skill adds no server, account or hosted database.

What if two projects get the same title?

The skill appends `- 2`, `- 3` and so on. Similar titles are shown for confirmation and never merged automatically.

Where are bookmarks stored?

In one Markdown file per agent under `~/.agents/memories/sessions/`. The `AGENTS_MEMORIES_DIR` variable sets another folder.

How do I get back into a saved session?

Ask "resume the heap benchmark session" with your own title: the skill returns a command such as `claude --resume <id>` and the folder to run it from.

Discussion

No questions or reviews yet.

Skills

A skill for searching past sessions: a full-text index of Claude Code, Codex, pi and Grok chats in one SQLite database

SkillMinimal access146

Terminal search across Claude Code, Codex, OpenCode and other agent sessions, with a jump back into the right chat

CLIExtended access193

A skill that keeps project memory in plain Markdown files: session logs, a wiki, rules, a to-do list and a note on where to resume

SkillExtended access376

An fzf-based CLI that lists sessions of Claude Code, Codex and six more agents across projects and resumes the chosen one.

CLIExtended access51

A CLI that hands session context between coding agents: continue a Claude Code session in Codex, Cursor, OpenCode and others.

CLIExtended access83

The CLI turns a coding-agent session into a shareable page with conversation, tool activity, files and a diff.

CLIExtended access593

Comparison with similar tools

Cards that share the main search query, and how they differ.

ToolOfficialRepository starsMain difference
save-session (this card)no60
Coding Agent Session Search (cass)no1,205searches the full text of session history; save-session keeps only bookmarks and returns the resume command
Claude Session Dashboardno77a dashboard over the `.claude` folder showing context use; save-session returns to the right session by name

README in short

The skill gives one workflow for five agents: save, find, resume. Bookmarks are human-readable and editable as ordinary text.

README badge

Original SKILL.md

---
name: save-session
description: Save the active coding session (session ID, model, working directory) to a per-harness markdown record under ~/.agents/memories/sessions/, and later find a saved session by project title and tell the user exactly how to resume it. USE THIS SKILL whenever the user wants to save, bookmark, or remember a session or session id ("save this session", "remember this session", "store my session id", "note down where we were"), or asks to get back into earlier work ("resume the X session", "find the session for X", "continue where we left off on X", "which session were we doing X in", "what's my session id for X", "how do I get back into X"). Applies to Pi, Claude Code, Codex, Antigravity CLI (agy), and OpenCode. Trigger even when the user names neither a session ID nor a harness — figuring those out is this skill's job.
license: MIT
metadata:
  author: "Jemshit Iskanderov"
  version: "0.2.0"
---

# save-session

Two modes:

1. **save** — record the current session under a project title so future-you can find it.
2. **find & resume** — look up saved sessions by project title and hand the user the exact resume command.

## Where records live

Destination resolution, in order:

1. A destination the request explicitly names (useful for testing or project-local notes).
2. The `AGENTS_MEMORIES_DIR` environment variable, if set.
3. Default: `~/.agents/memories/sessions/` (create it if missing).

Sessions are owned by the harness that created them — a Pi session id means nothing to
Codex, and each harness stores and resumes sessions its own way. That is why records get
**one file per harness**, so a lookup never mixes id spaces:

```
~/.agents/memories/sessions/
├── pi.md
├── claude-code.md
├── codex.md
├── antigravity.md
└── opencode.md
```

## Record format

Keep entries to exactly these four fields — this is a lookup index, not a journal. Notes,
summaries, and reflections belong in the project itself.

```markdown
# Sessions — Pi

Report a problem