PowerContext

Not only memory

PowerContext is the upgraded version of PowerMem and a context runtime for human-agent collaboration. It turns shared work into project context that can be understood, handed off, and continued.

Quick start

You need macOS or Linux, Python 3.11 or newer, uv, and at least one supported agent host.

1. Install PowerContext and the plugins

uv tool install "powercontext[cli,server]==0.0.2"

# Choose one or more integrations.
powercontext setup codex --source oceanbase/powercontext --ref v0.0.2
powercontext setup claude-code --source oceanbase/powercontext --ref v0.0.2
powercontext setup dsh --source oceanbase/powercontext --ref v0.0.2
powercontext setup hermes --source oceanbase/powercontext --ref v0.0.2

The first command installs the CLI and local Server in an isolated environment. The subsequent setup commands install the corresponding plugins from the matching repository tag. Run setup again to refresh an existing installation. Hermes integration requires Hermes Agent v0.20.4 or newer; see the Hermes integration guide for configuration and project-local installation.

2. Start and verify the local Server

Keep the Server running in one terminal:

powercontext server run

In another terminal, verify the service and plugin:

powercontext doctor
powercontext doctor codex  # or: claude-code / dsh / hermes

By default, the Server listens on 127.0.0.1:8000, exposes Streamable HTTP MCP at /mcp, and persists data in a local SQLite database. Explicit Memory operations work without configuring an inference provider.

Core capabilities

Capability	Core value
Memory extraction and management	Explicitly record decisions, constraints, outcomes, state, and next steps worth reusing over time; with a generation model configured, Memory can also be extracted from Sources. Revisions and retirements preserve history
Bounded request-time recall	Before an agent handles a request, generate one schema-validated, cited `PreparedContext` based on project scope, relevance, and a byte budget; recall failures do not block the original task
Handoff	Organize the objective, verified progress, blockers, next step, and evidence into an inspectable work package so another session, task, model, or agent host can continue from a clear state
Sources and evidence lineage	Preserve the original sources of knowledge and link Memory and Artifacts with exact citations; capturing a prompt creates only a Source and does not directly turn it into Memory
Experience and Skill governance	A model or caller can only submit a Candidate; an immutable revision is created only after Review, and a Skill must still be exported explicitly—it cannot approve, install, or execute itself
Local and service deployment	Use SQLite directly for local development, choose OceanBase for team deployments, and integrate with existing systems through HTTP/OpenAPI, MCP, authentication, and OpenTelemetry

Benchmarks

LoCoMo

LOCOMO benchmark comparison showing PowerContext accuracy, search latency, and answer token usage against PowerMem and a full-context baseline

SWE-bench Pro public v2

SWE-bench Pro public v2 comparison showing an increase from 82.35% with PowerContext off to 86.73% with PowerContext on

The evaluation ran in a Codex environment, with both the PowerContext OFF and ON groups using the gpt-5.6-sol model.

Plugins

PowerContext provides official plugins and installation guides for Codex, Claude Code, DeepSeek Harness, and Hermes Agent. All four integrations use the same scoped data and history-preserving contracts through PowerContext Server; the plugins do not start or embed the Server.

Official integrations

_Codex

_{Claude Code}

_{DeepSeek Harness}

_{Hermes Agent}

Development

Install the locked development environment and hooks:

make install

Run the main validation commands before opening a pull request:

make check
make test
make docs-test

After changing openapi/powercontext.yaml, run make contract-test. See CONTRIBUTING.md for the complete workflow and docs/en/development/ for implementation guides.

Community

Questions and feedback are welcome in Discord. Use GitHub Issues for reproducible defects and focused feature requests.

License

PowerContext is licensed under the Apache License 2.0.

Release files for powercontext 0.0.2

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

Source distribution (sdist)

Source distribution for powercontext 0.0.2
File	Size	Uploaded
powercontext-0.0.2.tar.gz	2.6 MB	Aug 20, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for powercontext 0.0.2
File	Interpreter	ABI	Platform	Reset
powercontext-0.0.2-py3-none-any.whl 445.5 kB Aug 20, 2026	Python 3	none	any	Details

Total release size: 3.0 MB

Release files / powercontext-0.0.2.tar.gz

Download URL	powercontext-0.0.2.tar.gz
Size	2.6 MB
Tags	Source
SHA-256 checksum How to use checksums	`f68b1dbe058e6a95ac2b45af000c471d900475921939c28af5f52995527385dd`
BLAKE2b-256 checksum How to use checksums	`3ce5b33f4feb504ea2be64d48393982f84f4de4baba9209c4175475ea0fa3f73`
Upload date	Aug 20, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

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.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/oceanbase/powercontext
Publishing commit: github.com/oceanbase/powercontext/tree/17f0369aa720f92a95b8777bf272974c56234ea8

Workflow

Publishing configuration: github.com/oceanbase/powercontext/blob/17f0369aa720f92a95b8777bf272974c56234ea8/.github/workflows/release.yml
Publishing logs: github.com/oceanbase/powercontext/actions/runs/32343344236/attempts/1

Artifact

Subject: powercontext-0.0.2.tar.gz
SHA-256 checksum: f68b1dbe058e6a95ac2b45af000c471d900475921939c28af5f52995527385dd Verifying attestations

Release files / powercontext-0.0.2-py3-none-any.whl

Download URL	powercontext-0.0.2-py3-none-any.whl
Size	445.5 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`628d4fadd0d858930e503b1a034b2f5017da04dd7262aab8dbb9e8a56b72604f`
BLAKE2b-256 checksum How to use checksums	`42a15ae66434d54cc8ffabb1ddc2bbc1300ce4c88548ea6e84b9331c30c9718a`
Upload date	Aug 20, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/oceanbase/powercontext
Publishing commit: github.com/oceanbase/powercontext/tree/17f0369aa720f92a95b8777bf272974c56234ea8

Workflow

Publishing configuration: github.com/oceanbase/powercontext/blob/17f0369aa720f92a95b8777bf272974c56234ea8/.github/workflows/release.yml
Publishing logs: github.com/oceanbase/powercontext/actions/runs/32343344236/attempts/1

Artifact

Subject: powercontext-0.0.2-py3-none-any.whl
SHA-256 checksum: 628d4fadd0d858930e503b1a034b2f5017da04dd7262aab8dbb9e8a56b72604f Verifying attestations