Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
blacktop avatar

Save Session

  • 1 installs
  • 17 repo stars
  • Updated July 16, 2026
  • blacktop/dotfiles

Save-session is a skill that saves AI agent session information to a file for later resumption by any AI agent.

About

Save-session saves AI agent session information so any agent can resume the work later. A developer uses it when finishing a work session and wanting to save progress, or before ending a long coding or debugging session. It writes session metadata (session ID, agent, summary) to docs/.ai/sessions.json via a bundled script and documents how to find the session ID for Claude, Codex, Gemini, Copilot, and Cursor.

  • Saves AI agent session metadata to docs/.ai/sessions.json for later resumption
  • Supports Claude, Codex, Gemini, Copilot, and Cursor
  • Includes a Python script and per-agent session-ID discovery instructions

Save Session by the numbers

  • 1 all-time installs (skills.sh)
  • Ranked #2,476 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
At a glance

save-session capabilities & compatibility

Capabilities
handoff · session save
Use cases
memory · project management
From the docs

What save-session says it does

Save AI agent session information for later resumption.
SKILL.md
Save session metadata to `docs/.ai/sessions.json` for future resumption by any AI agent.
SKILL.md
Supports Claude, Codex, Gemini, Copilot, Cursor, and other AI agents.
SKILL.md
npx skills add https://github.com/blacktop/dotfiles --skill save-session

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1
repo stars17
Last updatedJuly 16, 2026
Repositoryblacktop/dotfiles

What it does

Save AI agent session progress and metadata so any agent can resume the conversation later.

Who is it for?

Saving session progress before ending a long coding or debugging session for later resumption.

When should I use this skill?

Finishing a work session, or when the user says 'save session' or 'remember this session'.

What you get

Session metadata is written to docs/.ai/sessions.json so the work can be resumed later.

  • docs/.ai/sessions.json entry

By the numbers

  • Supports 5+ named AI agents

Files

SKILL.mdMarkdownGitHub ↗

Save Session

Save session metadata to docs/.ai/sessions.json for future resumption by any AI agent.

Usage

python3 ~/.agents/skills/save-session/scripts/save_session.py \
  --session-id "SESSION_ID" \
  --agent "claude" \
  --summary "Brief description of work done" \
  --repo-root "$(pwd)"

For Codex, you can use automatic detection:

python3 ~/.agents/skills/save-session/scripts/save_session.py \
  --session-id auto \
  --agent codex \
  --summary "Brief description of work done" \
  --repo-root "$(pwd)"

Finding Your Session ID by Agent

Claude Code

Session storage: ~/.claude/projects/<project-hash>/<SESSION_ID>.jsonl

How to find:

  • Extract UUID from file paths in context (e.g., tool output paths contain the session ID)
  • Use /status command to see session info
  • List sessions: claude --resume (interactive picker)

Environment: CLAUDE_CONFIG_DIR changes storage location (default: ~/.claude)

Resume: claude --resume SESSION_ID or claude -r SESSION_ID

OpenAI Codex CLI

Session storage: ~/.codex/sessions/

How to find:

  • Use /status command within Codex
  • Copy from session picker
  • List files in ~/.codex/sessions/
  • Or pass --session-id auto (uses latest ~/.codex/shell_snapshots/*.sh filename; verify if multiple sessions are active)

Note: Session ID is not currently exposed to the model itself (see GitHub issue #5912)

Resume: codex resume SESSION_ID

Google Gemini CLI

Session storage: ~/.gemini/tmp/<project_hash>/chats/

How to find:

  • Use gemini --list-sessions to see all sessions with UUIDs
  • Sessions are project-specific

Resume options:

  • gemini --resume (latest session)
  • gemini --resume <UUID> (specific session)
  • gemini --resume <index> (by index number)
  • /resume command within interactive mode

GitHub Copilot CLI

How to find:

  • Use /session or /usage command to display current session ID
  • Use gh agent-task list (requires gh v2.80.0+)
  • Use gh agent-task view for session details

Resume: /resume SESSION_ID or /resume last

Note: Auto-compaction maintains context across long sessions

Cursor IDE

Session storage: SQLite databases in workspace storage

  • macOS: ~/Library/Application Support/Cursor/User/workspaceStorage/
  • Linux: ~/.config/Cursor/User/workspaceStorage/
  • Windows: %APPDATA%\Cursor\User\workspaceStorage\

How to find: Sessions stored in .vscdb files as JSON blobs

Note: No built-in session ID. Use SpecStory extension for backup/export.

Aider

Session storage: Chat history in .aider.chat.history.md in repo root

Note: No formal session ID system. History is file-based and can be referenced by timestamp.

Session File Format

{
  "sessions": [
    {
      "id": "uuid-session-id",
      "agent": "claude",
      "summary": "Implemented multi-platform CI",
      "created_at": "2026-01-31T15:45:00Z",
      "tags": ["ci", "rust"]
    }
  ]
}

Resuming Sessions

AgentResume Command
Claude Codeclaude --resume SESSION_ID
Codexcodex resume SESSION_ID
Gemini CLIgemini --resume SESSION_ID
Copilot CLI/resume SESSION_ID
CursorRestore from workspaceStorage backup
AiderReference .aider.chat.history.md

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.