PowerContext
Context for work that humans and agents hand off and continue.
Work rarely ends with whoever starts it. You hand a task to an agent, the agent gets part of the way, and later you or someone else takes over. The reasoning and current state often stay behind in that conversation.
PowerContext keeps context with the work across conversations. When you return, you can see what happened and continue from the current state. A new agent can do the same.
Website · Installation walkthrough
PowerContext 1.0.0 includes the guided setup. The commands below install the stable release and connect the matching Agent integration.
Pick up where the work left off
You see the context the work needs now: confirmed decisions, constraints, progress, evidence, and next steps. You can continue from there or hand the work to another person or agent without rereading the full history.
You decide what will matter later and what needs to move with the task. PowerContext stores durable information as Memory and organizes the current objective and state into a Handoff. You can record reusable approaches as Experience or Skill. PowerContext keeps every item within the scope of the work and preserves its sources and earlier revisions.
Install, configure, and connect your Agent
You need Git, uv, and your Agent's CLI.
Python 3.11+ is required; uv can provision it. macOS and Linux are supported; Windows support is experimental.
Install 1.0.0 and open the interactive configuration wizard in a dedicated directory:
uv tool install --force "powercontext[cli,server]==1.0.0"
mkdir -p powercontext-config
cd powercontext-config
powercontext config init --language en --output .env
If Python dependency downloads are slow or fail, follow the mirror retry instructions.
The wizard asks about storage, local or remote access, memory capabilities, Dashboard, model APIs, and Agent connections. Choose Full memory capabilities to test automatic Memory and Topic Memory; this requires separate Generation and Embedding API credentials. An Agent subscription does not provide those Server credentials. Choose Basic memory to save and retrieve memories explicitly without additional model APIs.
The wizard writes one .env environment file and .env.next-steps.md.
If seekdb needs installing, it asks once and installs the dependency in the background. Follow the printed
connection details and start Server in this terminal:
powercontext server run --env-file .env
Keep Server running. In another terminal, return to powercontext-config, load only the client settings,
and check the connection:
set -a
. ./.env
set +a
powercontext ready
powercontext capabilities
Continue with .env.next-steps.md to create and bind the selected Scopes, install the matching plugins, and launch
a new Agent session. The complete walkthrough
covers Codex and Claude Code, Dashboard login, SSH forwarding, HTTPS prerequisites, and observable acceptance checks.
For example, the matching Codex installation is:
powercontext setup codex --ref powercontext-v1.0.0
powercontext doctor codex
doctor verifies integration setup. To verify automatic memory, check that a real prompt becomes a Source,
produces a Topic, evolves after a related prompt, and can be recalled in a new session using the same Scope.
For a Server on another machine, use HTTPS or follow the
remote connection guide. Setup recognizes remote HTTP URLs from
flags or environment variables and asks for explicit consent; automated setup uses --allow-insecure-http.
Codex is official; other hosts and Python Agent frameworks are community; Bub is evaluation only.
These tags describe PowerContext integration maintenance and use. See the
capability matrix for supported features and availability.
Codex |
Claude Code |
DeepSeek Harness |
Hermes Agent |
Pi Coding Agent |
OpenClaw |
OpenCode |
WorkBuddy |
Bub |
Pydantic AI |
LangChain |
LangGraph |
Applications can use PowerContext through the async Python client, HTTP API, MCP, or the in-process Core SDK. See the interface reference to choose an entry point.
Explore the 22 Chinese Jupyter tutorials and a complete team workflow to run Memory, context preparation, Handoff, Experience, Skill, and a real Agent step by step. The first seven tutorials need no model or API key.
What changes with PowerContext
See the methods, full results, and limitations behind these comparisons.
Build PowerContext
make install
make check
make test
See CONTRIBUTING.md for the complete development workflow.
Learn more
PowerContext is the successor to PowerMem.
License
PowerContext is licensed under the Apache License 2.0.
Release files for powercontext 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| powercontext-1.0.0.tar.gz | 5.4 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| powercontext-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.9 MB
Release files / powercontext-1.0.0.tar.gz
| Download URL | powercontext-1.0.0.tar.gz |
|---|---|
| Size | 5.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec5b53116bf3ff193ca9b8f12852769f30b8b24111addca8e020f9bf9e37ab18
|
|
BLAKE2b-256 checksum How to use checksums |
1c60413191805f5be49a312425c827496224b7348ae0b09435bfa0da1299a749
|
| Upload date | |
|
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.
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 Sep 11, 2026.
Transparency logRelease files / powercontext-1.0.0-py3-none-any.whl
| Download URL | powercontext-1.0.0-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d13638c6f7645cbc3007d4ee644fdc269e565eb97cffab4def5f09ba42bc75d8
|
|
BLAKE2b-256 checksum How to use checksums |
edfede5111831ef873ed189f65a6525ce30f7ae543711b44a24ed1dc0633154c
|
| Upload date | |
|
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.
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 Sep 11, 2026.
Transparency log