powercontext README

The project's README from github.com/oceanbase/powercontext. As one markdown file: README.md.

PowerContext

Context for work that humans and agents hand off and continue.

PyPI version License Apache 2.0 Discord

English · 中文 · 日本語

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.

You and agents hand work off and continue with stored context

Website · Installation walkthrough

PowerContext 1.1.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.1.0 and open the interactive configuration wizard in a dedicated directory:

uv tool install --force "powercontext[cli,server]==1.1.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.1.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
Codex
Claude Code
Claude Code
DeepSeek Harness
DeepSeek Harness
Hermes Agent
Hermes Agent
Pi Coding Agent
Pi Coding Agent
OpenClaw
OpenClaw
OpenCode
OpenCode
WorkBuddy
WorkBuddy
Bub
Bub
Pydantic AI
Pydantic AI
LangChain
LangChain
LangGraph
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

Compact comparison of PowerContext results on LoCoMo and SWE-bench Pro

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.

Contributors

Thank you to everyone who contributes to PowerContext. ❤️

PowerContext contributors

See all contributors · Start contributing

License

PowerContext is licensed under the Apache License 2.0.

powercontext (oceanbase/powercontext)

Searching Database…

What is this?PowerContext is a self-hosted context service from the OceanBase team. It keeps decisions, evidence, and task state together with the project, so you or another agent can pick the work up in a later session.
So is it a library I import into my code, or a service I run?It's a Server you run plus client integrations: applications connect through an async Python client, HTTP API, MCP, or the in-process Core SDK.
How do I set it up?Install the 1.1.0 release with Git and uv (uv provisions Python 3.11+), open the interactive configuration wizard in a dedicated directory, then start the Server in its own terminal and keep it running.
Do I need my own model API keys?Only Full memory capabilities needs them: automatic Memory and Topic Memory require separate Generation and Embedding API credentials, which an agent subscription does not cover. Basic memory works with no extra model APIs.
Does it work on Windows yet?macOS and Linux are supported; Windows support is experimental. If Python dependency downloads are slow or fail, the README has mirror retry instructions.
Can the Server run on a different machine from my agent?Yes. For a Server on another machine use HTTPS or the remote connection guide; remote plain-HTTP URLs require explicit consent, and automated setup can pass --allow-insecure-http.
Where does the context data live?In the Server you run yourself: the wizard asks whether storage and access are local or remote, and remote connections go over HTTPS with explicit consent.
What is the difference between Memory and Handoff?Memory holds durable information such as confirmed decisions and evidence, and reusable approaches can be saved as Experience or Skill. A Handoff packages the current objective and state so the next person or agent can continue without rereading the full history. Every item stays scoped to its work and keeps its sources and earlier revisions.
Is there a walkthrough for learning the workflow?Yes — 22 Jupyter tutorials (in Chinese) plus a complete team workflow that runs Memory, context preparation, Handoff, Experience, Skill, and a real agent step by step. The first seven tutorials need no model or API key.
How does it relate to PowerMem?PowerContext is the successor to PowerMem, so new setups should start here. The 1.1.0 release includes the guided setup wizard.
What is the seekdb dependency installed during setup?It's a dependency of PowerContext: if it's missing, the setup wizard asks once and installs it in the background for you.
What are similar projects?deer-flow, mem0, brigade, EverOS, OpenMetadata, hindsight, Memori, Raven
Creator
oceanbase
Size
51.7 MB
Stars
1.3K
Age
11mo
Commits · 90 Days