Skip to main content

scion

Turn a coding-AI chat session (Claude Code or Codex CLI) into a deployable, continuously-learning subject-matter-expert agent that any MCP-aware host can talk to.

scion extracts everything from a Claude Code or Codex CLI session — every message, every tool call, every memory file, every skill, every config — distills it into a portable, git-committable Agent Bundle, and serves the bundle as a stdio MCP server. Your colleague's Claude Code or Codex CLI calls /mcp__scion-<name>__ask (or the query tool) and gets a grounded answer. The bundle learns from every interaction via a nightly dream loop that consolidates new episodes into memory, gated by an evaluation ratchet so the agent cannot silently degrade.

Status

Pre-alpha. Building toward v0.1.0 (Phases 1–4 of the PRD).

Phase What State
0 Foundation, governance, context docs in progress
1 Claude Code extractor + bundle + CLI + LLMClient skeleton planned
2 Stdio FastMCP server + distill + memory tool wiring planned
3 Episode writeback + nightly dream loop with eval ratchet planned
4 Codex CLI extractor (closes v0.1.0) planned

Three-command quickstart (target — not yet runnable)

uv tool install scion
scion init demo
scion demo                  # full pipeline against synthetic fixture, no API key

Once Phase 1 ships, replace the third line with:

scion extract claude-code --cwd ~/proj/recon --output ./bundles/recon-sme
scion install claude-code ./bundles/recon-sme
# Restart Claude Code → /mcp__scion-recon-sme__ask "how do partial refunds work?"

How it compares

scion mem0 Letta / MemGPT Zep CE
Local-first, no daemon ✓ hosted daemon needs Neo4j
Git-committable bundles ✓ ✗ ✗ ✗
Continuous learning loop eval ratchet (Karpathy) LLM-extracted facts tiered memory (managed) temporal graph
Memory shape files (markdown) facts (KV+vector) tiered store knowledge graph
Provider portability LiteLLM (any) OpenAI-default OpenAI-default provider-agnostic
Plugin extractor surface ✓ n/a n/a n/a
Source-tool side effects none (read-only) n/a n/a n/a

Supported on

Linux + macOS, Python 3.11/3.12/3.13. Windows is out of scope for v0.1.0.

License

Apache-2.0.

Contributing

See CONTRIBUTING.md. DCO sign-off required (git commit -s); a hook is provided.

Metadata

Release files for scion 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for scion 0.2.1
File Size Uploaded
scion-0.2.1.tar.gz 142.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for scion 0.2.1
File Interpreter ABI Platform
scion-0.2.1-py3-none-any.whl Python 3 none any Details

Total release size: 243.0 kB

Release files / scion-0.2.1.tar.gz

Download URL scion-0.2.1.tar.gz
Size 142.2 kB
Tags Source
SHA-256 checksum
How to use checksums
8b4d74576c5f8189f9153757bf5741fcc860810e159b2bcda992b96d718b9944
BLAKE2b-256 checksum
How to use checksums
285143a0df6ba59fee9d8201fd07ddc16eb4773f44336ec658ab75e4f02de524
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 5, 2026.

Transparency log

Release files / scion-0.2.1-py3-none-any.whl

Download URL scion-0.2.1-py3-none-any.whl
Size 100.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4354d47e19c576559b12afa4a3e254778337bac3cb1379860de0b07c0c4eb148
BLAKE2b-256 checksum
How to use checksums
2328f381efe3b41f5ec138b723f675f4a269cad1d1578f36fe1d1ed778b14201
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on May 5, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.1 This release

2 release files

0.2.0

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page