powercontext-project-context

PowerContext

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

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.

Website · Installation walkthrough

PowerContext 1.3.0 includes the guided setup. The commands below install this version 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.

The optional recall-sufficiency gate records scope-local daily search effort and budget omissions for later policy evaluation. See the configuration reference for its recording and failure behavior.

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

uv tool install --force "powercontext[cli,server]==1.3.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.3.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.