Shared memory and handofffor your coding agents.

PowerContext is a local context service that stores your project's decisions, constraints, verified checks, and task progress. Switch between Claude Code, Codex, or teammates and pick up directly from the latest state. How it works

One project memory across every session.

When a session ends mid-task, PowerContext keeps the decisions you made, the code state, and the next step ready for whichever agent takes over.

  • The next session starts from a structured handoff of the current state.

  • Project decisions and constraints stay saved as versioned revisions.

  • Working fixes go through human review before entering shared memory.

  • Approved workflows become reusable Skills exported to your agents.

  • Recall stays within a strict byte budget, injecting only relevant context each turn.

Switch coding agents.Keep the full context.

Start a feature in one coding agent and finish it in another. PowerContext keeps your project's memory, task progress, and approved skills in one shared server.

View all supported agents

Connect several agents at once

The setup command installs, configures, and diagnoses each host you name against the same Server.

powercontext setup

Measured on public benchmarks.

Both results come from the published evaluation harness. The benchmarks page details the test methods and exact scope.

Methods, results, and limitations
LoCoMo accuracy across 1,540 scored questions
90.78%
Full-context replay scores 52.9% on the same questions.
fewer input tokens on SWE-bench Pro
25.4%
About 225 million per 100 tasks with PowerContext on, 302 million with it off.

What people say

  • pluoki@pluoki

    PowerContext can automatically extract memory and revise topic summaries. Its formal Experience workflow adds a review gate before reusable lessons become available for recall.

  • David 的生意实验室@Musfengtang

    A deployment problem I was debugging in Claude Code yesterday, I could pick up again in Codex today. The idea behind this PowerContext plugin is just to my taste: switch tools without starting over from introductions.

  • Big Bull@BIGBULLapp

    PowerContext moves the durable parts out of the conversation and into a context service, so decisions, constraints, evidence and progress survive the session that produced them.

  • Scott Siu 萧少聪@ScottSiu1983

    The context receipt in PowerContext v1.5.0 is a genuinely practical feature. When an Agent got something wrong, you used to have to guess: was it never found, found but not passed on, or passed on and ignored? With receipts, at least the first two can be checked.

From install to your first shared memory

Run a local PowerContext server, enable the memory features you want, and connect your coding agents. Works locally on your machine or across devices.

Follow the complete guide
  1. 1Install PowerContext

    Install the latest stable release with local Server support. The installer sets up Python and uv if needed; follow its printed PATH instructions.

    curl -fsSL https://powercontext.oceanbase.io/install.sh | bash
  2. 2Follow the configuration wizard

    Choose your storage, access scenario, memory capabilities, Dashboard, and Agents. It writes configuration files and tailored next steps.

    powercontext config init
  3. 3Start the Server

    Run from the directory containing your generated .env and keep this terminal open. Use the Dashboard URL and token provided by the wizard, if enabled.

    powercontext server run --env-file .env
  4. 4Connect your Agent and verify memory

    Follow .env.next-steps.md to connect your Agent and select a Scope. Save a decision, then retrieve it with its citation in a new session using the same Scope.