Skip to content

PowerContext v1.4.0

Latest
Latest

Choose a tag to compare

View all tags
@hidb4ai hidb4ai released this 19 Oct 05:56
· 56 commits to master since this release
powercontext-v1.4.0
cab054d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

PowerContext v1.4.0

Not only memory, but a full story.

English

PowerContext v1.4.0 helps project knowledge evolve while keeping work and changes traceable. This release introduces explicit Dream reviews, Working Notes for current progress, Dashboard revision history and comparison, and an experimental Kimi Code integration.

Dream: evolve knowledge through review

  • Use task outcomes, explicit corrections, or usage feedback as a reason to start Dream. Select the relevant knowledge and evidence, then inspect the proposed changes.
  • Propose revisions to Atomic Memory, Profiles, Topic Memory, Handoffs, Prompt configuration, and tags through the unified Candidate review flow.
  • Approve the exact Candidate version against the current target before publication. Generating a proposal does not approve it, execute work, or install a Skill.

Available operations depend on Server configuration. Skill revision remains disabled until its trusted evaluation requirements are met. Approving a Handoff publishes a revision without automatically continuing the task.

Working Notes: retain current progress

  • Capture findings, abandoned approaches, validation results, unresolved questions, and next steps as short-lived Working Notes.
  • Cite still-valid notes in a Handoff through exact Source references, so later work can inspect the evidence behind the recorded progress.
  • Set optional expiry to prevent new consumption while retaining the original record for audit.

Working Notes stay outside automatic Memory, Topic Memory, and other Artifact generation. Capturing a note does not automatically promote it into durable knowledge.

Knowledge changes with traceable history

  • Browse revision history, open exact versions, and compare content directly in the Dashboard.
  • Restore supported historical content as a new revision, recording the source version, reason, and actor. Previous revisions remain readable.
  • Inspect each Atomic Memory’s history and compare its revisions in a read-only view. Atomic Memory restoration follows its separate preview and confirmation workflow.

New revisions record creation timestamps; existing records retain unknown metadata where historical values are unavailable.

Connect Kimi Code to project memory

  • Install and diagnose the experimental integration through powercontext setup kimi-code and powercontext doctor kimi-code, using an explicitly configured Scope.
  • Save and search memories, read exact revisions through native MCP tools, and receive relevant context in a new session.
  • Optionally capture text prompts as Sources and inspect content-free Hook runtime observations.

Explicit Memory operations do not require a Generation model. Automatic Memory generation requires the Server’s Generation configuration and scheduler; successful Source capture alone does not establish that a Memory was created. Open a new Kimi Code session after setup or configuration changes.

Context, retrieval, and Agent integrations

  • Codex and Claude Code: Add opt-in, bounded startup context from explicitly selected Atomic Memories and an optional exact Handoff. Delivery receipts support deduplication; the feature is disabled by default.
  • Retrieval: Unify Chinese segmentation and English word analysis across supported backends, configure full-text/vector fusion weights for Atomic Memory and Topic Memory, preserve Source language during generation, and improve long-query handling.
  • DSH: Expand native MCP workflows with tool-catalog checks, Scope enforcement, approval handling, and caller-content secret screening. Refresh generated Agent guidance while preserving local edits.

Reliability and evaluation

  • Standardize operational logs, metrics, and trace identity, and expose extraction diagnostics through CLI capabilities.
  • Preserve exact captured Source identities on reads, pin SQLite content before custom authorization, and improve connection cleanup during cancellation.
  • Add stable Scope-local handles for exact Artifact revisions. Omit the placeholder x-api-key when Anthropic-compatible requests use an explicitly configured Authorization header.
  • Add cross-host work-continuity acceptance, offline Memory write-gate evaluation, and Dream generation baselines; extend Kimi Code and ZCode acceptance workflows. These checks do not establish a universal quality or performance gain.

Install and upgrade

After the package is published:

uv tool install --force "powercontext[cli,server]==1.4.0"

Include any extras your deployment already uses, such as code or seekdb. Upgrade the Server, clients, CLI, MCP, and Agent integrations together, then reopen Agent sessions.

Back up the complete database and configuration before maintenance. Stop all writers before database changes. Existing collection-based Memory databases require offline Atomic Memory conversion and verification.

Compatibility changes:

  • Candidate APIs move from /v1/artifact-candidates/* to /v1/candidates/* without compatibility aliases. Dream clients must support contract 2.
  • Retained legacy Memory routes return Atomic Memory records and references. Collection-based operations and legacy citation formats are no longer supported where documented.
  • The legacy collection MemoryWriteGate is unsupported by the Atomic Runtime; legacy collection capacity and compaction settings do not constrain Atomic Memory.

Existing Dream database upgrades remain limited. The current unified migration bundle reports server_ready=false and does not provide a complete production upgrade path. Passing Atomic Memory verification alone does not establish full Server readiness. Do not bypass migration_required or migration_framework_not_ready.

[Full changelog](powercontext-v1.3.0...powercontext-v1.4.0)

中文

PowerContext v1.4.0 让项目知识持续演进，也让工作进展与知识变化有据可查。本次带来显式发起的梦境复盘、承接当前进展的便签、Dashboard 历史版本浏览与对比，以及试验性 Kimi Code 集成。

梦境，触发知识演进

  • 把任务结果、明确纠正或使用反馈作为复盘契机，显式发起梦境。选择相关知识与证据，检查提出的修订建议。
  • 通过统一 Candidate 审核流程，为 Atomic Memory、Profile、Topic Memory、Handoff、Prompt 配置及标签提出修订。
  • 批准时检查精确候选版本与当前目标，再发布变更。生成提案不会自动批准、执行任务或安装 Skill。

可用操作取决于 Server 配置。Skill 修订在满足可信评测要求前保持关闭。批准 Handoff 会发布新版本，不会自动续接任务。

便签，留住当前进展

  • 用短期便签记录当前发现、放弃的方案、验证结果、未解决问题和待办。
  • 在 Handoff 中通过精确 Source 引用使用仍有效的便签，让后续工作能够查看进展背后的依据。
  • 可设置过期时间；过期后阻止新的消费，原始记录仍保留供审计读取。

便签不参与自动 Memory、Topic Memory 或其他 Artifact 生成。采集便签不会自动将其晋升为长期知识。

知识变更，有据可回溯

  • 在 Dashboard 浏览修订历史、打开精确版本，直接对比内容变化。
  • 将支持的历史内容恢复为新修订，记录来源版本、原因和操作者，已有历史仍可读取。
  • 查看每条 Atomic Memory 的历史并对比版本，界面保持只读；Atomic Memory 恢复使用独立的预览和确认流程。

新修订记录创建时间；旧记录缺少历史元数据时保留未知状态，不补造日期。

让 Kimi Code 接上项目记忆

  • 通过 powercontext setup kimi-code 和 powercontext doctor kimi-code 安装、诊断试验性集成，使用显式配置的 Scope。
  • 通过原生 MCP 工具保存和搜索记忆、读取精确版本，并在新会话中注入相关上下文。
  • 按需将文本提示采集为 Source，并查看不含正文内容的 Hook 运行观测。

显式记忆操作无需 Generation 模型。自动生成记忆需要 Server 的 Generation 配置和调度支持；Source 采集成功本身不代表记忆已经生成。安装或调整配置后，请重新打开 Kimi Code 会话。

上下文、检索与 Agent 集成

  • Codex 与 Claude Code： 新增可选的有界会话开场上下文，使用显式选定的 Atomic Memory 和可选的精确 Handoff。通过投递回执支持去重，默认关闭。
  • 检索： 在支持的后端统一中文分词与英文词语分析，为 Atomic Memory 和 Topic Memory 配置全文与向量融合权重，生成时保留 Source 语言，并改进长查询处理。
  • DSH： 扩展原生 MCP 工作流，检查工具目录、执行 Scope 约束、保留审批流程，并筛查调用方内容中的敏感值。更新自动生成的 Agent 指引，同时保留本地修改。

稳定性与评测

  • 统一运行日志、指标与追踪身份，在 CLI capabilities 中提供提取诊断。
  • 精确读取已采集的 Source，在自定义授权前固定 SQLite 内容快照，并改进取消时的连接清理。
  • 新增 Scope 内指向精确 Artifact 版本的稳定句柄。为 Anthropic 兼容请求显式配置 Authorization 请求头时，不再附加占位 x-api-key。
  • 新增跨 Host 工作连续性验收、Memory 写入门控离线评测及 Dream 生成基线，扩展 Kimi Code 和 ZCode 验收工作流。这些检查不代表所有任务都有统一的质量或性能提升。

安装与升级

包发布后执行：

uv tool install --force "powercontext[cli,server]==1.4.0"

保留当前部署使用的 code、seekdb 等扩展，一起升级 Server、客户端、CLI、MCP 与 Agent 集成，并重新打开 Agent 会话。

维护前完整备份数据库与配置。 数据库变更前停止全部写入进程。已有集合式 Memory 数据库需完成 Atomic Memory 离线转换与验证。

兼容性变化：

  • Candidate API 从 /v1/artifact-candidates/* 调整为 /v1/candidates/*，不提供兼容别名；Dream 客户端需支持契约 2。
  • 保留的旧 Memory 路由返回 Atomic Memory 记录与引用。文档中列明的集合式操作和旧引用格式不再支持。
  • Atomic Runtime 不支持旧集合式 MemoryWriteGate；旧集合容量与压缩设置不限制 Atomic Memory。

已有 Dream 数据库的升级仍有限制。 当前统一迁移包报告 server_ready=false，尚不提供完整的生产升级路径。Atomic Memory 验证通过不代表整体 Server 已就绪，不要绕过 migration_required 或 migration_framework_not_ready。

[完整变更](powercontext-v1.3.0...powercontext-v1.4.0)

What's Changed

  • docs(readme): add MiniMax Code to integration table by @knqiufan in #1954
  • fix(persistence): finish connection cleanup before a cancellation propagates by @guamiao in #1782
  • test(zcode): automate CLI acceptance and skill behavior evaluation by @jackie-cqz in #1850
  • feat(e2e): report Bub token usage through bub-acp-server 0.1.1 by @Fengzdadi in #1952
  • fix: dynamic tauri check for powercontext version by @Alanxtl in #1953
  • fix(migration): skip unenveloped Sources in the residual Memory check by @happy-v587 in #1935
  • feat: add cache for github actions by @Alanxtl in #1948
  • feat(integrations): generate and safely refresh host guidance by @russell001209-ai in #1877
  • build(deps): bump jdx/mise-action from 2.4.4 to 5.1.1 by @dependabot[bot] in #1958
  • build(deps): bump actions/setup-go from 6.5.0 to 7.0.0 by @dependabot[bot] in #1959
  • build(deps): bump actions/setup-node from 6.5.0 to 7.1.0 by @dependabot[bot] in #1960
  • build(deps): bump actions/upload-artifact from 7.0.1 to 7.0.2 by @dependabot[bot] in #1961
  • build(deps): bump Swatinem/rust-cache from 2.9.1 to 2.9.2 by @dependabot[bot] in #1962
  • feat(recall): make FTS and vector channel weights configurable per de… by @Lkx-JY in #1891
  • ci: run unit and end-to-end tests in parallel by @Fengzdadi in #1965
  • fix(evaluation): register the LoCoMo Scopes the runner captures into, and resolve them before inference by @jasondeng1997 in #1894
  • fix(zcode): refresh packaged skill evaluation pin by @hidb4ai in #1968
  • feat: add minimal Kimi Code integration by @jackie-cqz in #1964
  • RFC: Handoff session rollover by @AlexStocks in #1783
  • ci: add Kimi Code real-host acceptance by @jackie-cqz in #1974
  • feat(context): add bounded project bootstrap context by @wangchenxuya in #1720
  • docs(rfc): explainable PreparedContext receipts by @Tsukikage7 in #1435
  • docs: refresh Artifact FAQ and HTTP API overview by @frf12 in #1993
  • feat: add stable handles for artifact reversions by @Tech-Circle-48 in #1933
  • fix(zcode): stabilize pending boundary test timing by @hidb4ai in #1998
  • feat(kimi-code): add Hook runtime observations by @jackie-cqz in #1988
  • fix(desktop): refresh contract hashes and prevent validation drift by @hidb4ai in #1996
  • test(e2e): verify cross-host work continuity by @knqiufan in #2002
  • fix(zcode): use patched Node for Windows acceptance by @knqiufan in #2008
  • feat(evaluation): add offline evaluation workflow for Memory write gate by @lizining1231 in #2001
  • feat(cli): show extraction diagnostics in capabilities output by @mangeshraut712 in #2009
  • docs(examples): add OpenAI Python SDK PreparedContext example by @tangwenhai839-create in #2010
  • fix(memory): preserve source language and improve text recall by @jackie-cqz in #2011
  • feat(observability): standardize telemetry identity and structured logging by @happy-v587 in #2007
  • docs(rfc): propose reviewed multi-artifact Dreaming by @Zxf-xufeng in #1715
  • feat(dsh): Refactor PowerContext integration to utilize MCP tools and implement full ability by @Alanxtl in #1784
  • feat(search): integrate Atomic Memory into artifact retrieval by @frf12 in #1882
  • feat(dream): expand reviewed artifact and tag revisions by @Zxf-xufeng in #1716
  • docs(readme): lead with what PowerContext is and prove it with text by @AlexStocks in #2003
  • feat(search): unify word analysis across backends by @PsiACE in #1979
  • feat(work): add source-backed working notes by @Qiao-yq in #1949
  • fix(search): avoid OceanBase long-query expression overflow by @frf12 in #2024
  • feat(runtime): add privacy-safe decision projection by @beatenevo in #1987
  • docs(readme): add deepwiki badge, front-load quick start, and clarify evaluation scope by @Inference1 in #2027
  • test(dream): establish P0 generation baselines by @beatenevo in #2029
  • fix(runtime): pin the SQLite content snapshot before custom authorization by @tlyyxjz in #2026
  • test(dream): allow scheduling margin for usage accounting by @hidb4ai in #2032
  • fix(sources): accept captured Source identities on exact read by @NeverENG in #2030
  • docs(readme): move the content of the Quick Start section to a suitable later position by @Inference1 in #2045
  • docs:add manual startup guides by @CX33071 in #2046
  • docs(rfc): refine artifact evolution proposal by @beatenevo in #1750
  • feat(dashboard): browse, compare, and roll back artifact revisions by @b1ngsha in #1813
  • docs(onboarding): document capabilities, triggers, and Hook trust for… by @Lkx-JY in #2047
  • fix(runtime): omit placeholder x-api-key when Authorization header is configured by @huto-c in #2049
  • chore(release): prepare v1.4.0 by @hidb4ai in #2059

New Contributors

Full Changelog: powercontext-v1.3.0...powercontext-v1.4.0

Contributors

AlexStocks, Tech-Circle-48, and 27 other contributors
Assets 4
Loading