As a Claude Code plugin

claude plugin marketplace add barseghyanartur/claude-plugin-opencode-sessions
claude plugin install opencode-sessions@barseghyanartur

Or inside a Claude Code session:

/plugin marketplace add barseghyanartur/claude-plugin-opencode-sessions
/plugin install opencode-sessions@barseghyanartur

Update later with claude plugin update opencode-sessions@barseghyanartur, or turn on auto-update for the marketplace under Marketplaces in /plugin.

The plugin runs the code bundled in the plugin itself, so it does not need the PyPI package. It needs a Python >= 3.10 on PATH (python3, python3.1x) or uv. Note that /usr/bin/python3 on macOS is 3.9. brew install python or uv python install 3.12 fixes that, or set OCS_PYTHON=/path/to/python.

As a command-line tool

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

What an imported conversation contains

• One transcript per opencode session, in Claude Code’s own session folder for this project (~/.claude/projects/<project>/<uuid>.jsonl).

• User messages and assistant replies as text. Each tool call becomes one line (→ bash: `pytest -x`), and its output is left out unless you pass --with-tool-output. Reasoning, synthetic and sub-agent content are left out.

• A first line saying which opencode session it came from. Claude reads this when you resume, so it knows the context.

How duplicates are prevented

The Claude session id is uuid5(opencode session id + hash of the converted content). Importing unchanged content maps to a file that already exists, so it is skipped. The first line of each imported file records the opencode session id, content hash and suffix, so changed content gets the next free suffix (the highest existing one + 1). New files are written under a temporary name and hard-linked into place, which can’t overwrite an existing file. Continuing an imported conversation in Claude doesn’t count as a change: only the opencode side is compared.

Claude Code’s transcript format is internal and may change between Claude Code versions. The importer writes only a minimal, stable subset of it.

Scoping

Configuration

Every command also accepts --db PATH and --backend auto|sqlite|cli.

How each channel works

• Claude Code plugin: there is no registry upload. This repository is the marketplace (.claude-plugin/marketplace.json), so pushing to main publishes. Users only receive an update when the version in plugin.json changes, so every release must bump it.

• PyPI: claude-opencode-sessions is uploaded with twine, using the credentials in ~/.pypirc, so you don’t type them each time.

• Anthropic community marketplace (optional): a reviewed listing in anthropics/claude-plugins-community, pinned to a commit. Submit through the form that make submit prints the details for.

One-time setup

Put API tokens for PyPI and TestPyPI in ~/.pypirc (chmod 600):

[distutils]
index-servers =
    pypi
    testpypi

[pypi]
username = __token__
password = pypi-...

[testpypi]
repository = https://test.pypi.org/legacy/
username = __token__
password = pypi-...

Release checklist

make bump BUMP=minor     # or BUMP=patch|major, or VERSION=0.2.0
$EDITOR CHANGELOG.rst    # add the release notes
git commit -am "Release $(uv version --short)"
make test-release        # check, build, twine check, upload to TestPyPI
make release             # the same, upload to PyPI
make tag                 # tag vX.Y.Z and push (plugin users get the update)

For the community marketplace, run make submit after the release and file the form.