Features

• No model call, no tokens. The import runs in a Claude Code hook and prints its report directly. Tokens are only spent once you resume a session and start typing, just like any other conversation.

• No duplicates, ever. A session whose content hasn’t changed since its last import is skipped. A session that changed gets a new copy with the next suffix: Title, Title (1), Title (2)…. Existing files are never overwritten.

• Only this repository. Scoping works like /resume: the current git worktree by default, or --worktrees for all worktrees of the repo.

• Reads Copilot CLI’s own session files directly, read-only. No database, no CLI call, no network access.

Prerequisites

Python 3.10+

Installation

claude plugin marketplace add barseghyanartur/claude-sessions-importer
claude plugin install copilot-sessions@barseghyanartur

/plugin marketplace add barseghyanartur/claude-sessions-importer
/plugin install copilot-sessions@barseghyanartur

uv tool install claude-copilot-sessions      # or: pipx install claude-copilot-sessions
uvx claude-copilot-sessions list              # one-off run without installing

Usage in Claude Code

/copilot-sessions:import                      # sessions of the current worktree
/copilot-sessions:import --worktrees          # every worktree of the repository
/copilot-sessions:import --dry-run            # show what would happen
/copilot-sessions:import --with-tool-output   # include (truncated) tool output
/resume                                       # pick a "[copilot] …" session

Example report:

Copilot CLI → Claude Code import · git worktree /Users/me/repos/brrn
into ~/.claude/projects/-Users-me-repos-brrn

  imported     [copilot] Clarify Project Objectives

1 imported
Open them with /resume — titles start with "[copilot]".

Command line

The same package works in the terminal:

claude-copilot-sessions import --dry-run           # same as /copilot-sessions:import
claude-copilot-sessions import --worktrees
claude-copilot-sessions list                       # sessions in scope, newest first
claude-copilot-sessions list --all --format json
claude-copilot-sessions doctor                      # environment + sessions report

How it works

Copilot CLI keeps one directory per session under $COPILOT_HOME/session-state/<uuid>/: a workspace.yaml with the session’s directory, title and timestamps, and an events.jsonl with the conversation itself. There’s also a session-store.db SQLite index, but everything this importer needs is already in the two per-session files, so the database is never opened. See docs/design.md for the full format notes.

Development

make install     # uv sync (creates .venv with dev tools)
make test        # pytest (tests live in src/claude_copilot_sessions/tests)
make check       # ruff + mypy --strict + pytest + manifest validation
make run ARGS="list --all"
make dev         # claude --plugin-dir . (live plugin; /reload-plugins after edits)
make install-local / make uninstall-local

Troubleshooting

If /copilot-sessions:import makes Claude answer instead of printing a report, the hook didn’t run. Check the Python requirement above and run claude-copilot-sessions doctor, or sh ~/.claude/plugins/…/scripts/copilot-sessions doctor. It shows the Python in use, the Copilot home in use, the session count and the scope roots for the current directory.

License

MIT

Support

For security issues contact me at the e-mail given in the Author section.

For overall issues, go to GitHub.

Author

Artur Barseghyan <artur.barseghyan@gmail.com>