v1.5.2 · Faster memory · Native observability · Easier integrations
PowerContext v1.5.2 makes Agent long-term memory more efficient, transparent and easier to use, with single-Server performance improvements, native Dashboard observability, stronger Desktop and plugin support, OAuth subscription transports, and more reliable cross-tool handoffs.
Highlights
- Improve single-Server efficiency through batched writes, reusable query structures, optimized vector conversion, and fewer repeated computations and database round trips. Maintainer-provided release measurements report approximately 190% higher write throughput, 171% higher query throughput, and 64%–67% lower CPU cost than v1.5.1. These measurements were not rerun during release preparation. The repository does not include the workload, hardware, concurrency, sample count, measurement date or reproduction command for these figures; they are not independently reproducible release acceptance evidence or a throughput guarantee for every deployment or end-to-end model extraction.
- Add native Dashboard observability views for processing progress, failure diagnostics, Token usage and runtime state. Inspect saved Sources, generated Artifacts, Dream inputs and outputs, and read-only processing status. Historical Sources without a recorded save time retain an unknown value.
- Improve Desktop local Server installation, recovery and management, package independent Ops resources, and add Linux systemd --user service integration. Protocol checks and local setup support do not replace signed-installer or clean-machine platform acceptance.
- Load directory plugins that generate, render, search and change their own Artifacts, with plugin APIs and sandboxed Dashboard pages. Plugins can declare their own Source types. Plugins also gain per-plugin databases on OceanBase and seekdb (`powercontext_plugin_<name>`), Dashboard forwarding to their own Artifact API, Scope listing limited to their own readable Scopes, and fixes for user-change evidence and write/governance consistency. Hot reload, plugin data upgrades, plugin MCP tools and standalone Source collection are not included.
- Add Gateway alpha OAuth subscription transports and improve request deadlines, cancellation and bounded shutdown. Provider capabilities differ: Gemini context injection is disabled, and Claude CLI is single-turn/text-only and unavailable under enforcing or unknown Core protection. Gateway continues to buffer complete responses for inspection.
- Persist and recover DSH handoff deliveries, expose connection status and update checks, and embed the Dashboard in the sidebar. Add the Claude Desktop Code handoff adapter; native launch stays disabled by default until the receiving environment can be verified. Offer optional PowerContext long-term memory for dsh-pet.
- Strengthen privacy handling in DSH automatic recall and capture, request confirmation for OpenCode writes under default permissions, and detect Memory protocol mismatches across Hosts. Improve Codex setup, preserve OpenClaw project bindings during capture, and checkpoint in-session auto-compaction.
- Bound Topic Memory related history, preserve the healthy processing prefix before a failing or oversized look-ahead, and prevent concurrent head conflicts from consuming window attempts. Keep Memory merges within the tag limit and allow portable Source exports to retain recorded absolute working directories.
- Upgrade Server, SDK, CLI and integrations together. The directory-plugin framework replaces the previous managed plugin APIs and configuration. Migration v1_5_0_005 refuses databases that retain old plugin registrations or data. There is currently no supported in-place upgrade path for these databases. Unloading plugins, deleting plugin directories, or exporting archives does not clear the retained framework records, even when no Artifacts were generated. Keep the database on the previous version until a supported migration is available. A separate fresh database can use the new version, but this does not migrate old plugin data; do not manually delete framework records to bypass the check. Portable Artifact revision records use schema version 3 and still restore version 2. Database upgrade support is limited to source-version, target-artifact, backend and configuration combinations that pass full Server acceptance.
- Update imports from `powercontext.server.authz` to `powercontext.builtin.authz`, from `powercontext.cli.env_file` to `powercontext.env_file`, and from `powercontext.cli.inference_notice` to `powercontext.server.inference_notice`. `powercontext.paths.default_scheduler_path` has been removed. The `scheduler_path` argument is deprecated and ignored; passing a non-None value emits `DeprecationWarning`. Remove that argument from runtime construction.
uv tool install --force "powercontext[cli,server]==1.5.2"View the full GitHub release