Skip to content

PowerContext v1.0.0 RC2

Pre-release
Pre-release

Choose a tag to compare

View all tags
@Teingi Teingi released this 10 Sep 12:14
· 200 commits to master since this release
powercontext-v1.0.0rc2
2f644be
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.0.0 RC2

English

PowerContext 1.0.0 RC2 is the second release candidate for 1.0.0. This update simplifies initial configuration and Agent connections, and introduces a reviewed workflow for turning Memory into Experience and approved Experience into Skill candidates.

This is a pre-release for testing the Server, clients, and Agent integrations together. The following changes are relative to RC1.

Highlights

  • Guided initial configuration: powercontext config init offers an interactive wizard in English and Chinese for storage, model APIs, memory capabilities, Dashboard access, and Agent connections. It writes .env and .env.next-steps.md, with instructions for starting the Server, creating and binding Scopes, and connecting Agents.
  • Persistent Agent authorization: save PowerContext connection credentials for Codex, Claude Code, DSH, OpenCode, Pi, and WorkBuddy so later sessions can read them. Stored authorization is bound to the Server URL and is used only when that URL matches.
  • From Memory to Experience to Skill: the new Dream workflow refines selected Memory entries into Experience candidates and derives Skill candidates from approved Experience. Candidates retain evidence references and become Artifact Revisions after review and approval. Skill publication and installation remain explicit actions. Submit runs, inspect their status, and review candidates through the CLI, Client SDK, or HTTP API.
  • Explicit consent for remote HTTP: connections to non-loopback plain-HTTP endpoints require an explicit opt-in. Interactive setup asks for confirmation; unattended setup uses --allow-insecure-http. Saved consent applies only to the corresponding endpoint. HTTP connections to localhost and loopback addresses remain allowed by default.

Install and verify

uv tool install --force "powercontext[cli,server]==1.0.0rc2"
powercontext --version

The version output should be 1.0.0rc2. For a first installation, start the configuration wizard:

powercontext config init --language en --output .env

Follow the generated .env.next-steps.md to start the Server, configure Scopes, and connect your Agent. Install the Codex integration from the tag matching the Python package:

powercontext setup codex --ref powercontext-v1.0.0rc2

Use powercontext-v1.0.0rc2 for other Agent integrations as well. Select the pre-release version explicitly when installing or upgrading.

Upgrade notes

  • Back up databases and configuration before upgrading. On startup, the Server initializes Dream run storage and adds Memory reference fields to existing Artifact and Candidate version tables. Upgrade the Server, clients, and Agent integrations together, then restart the Server and Agent sessions.
  • Dream and automatic memory processing require the appropriate Generation service; semantic retrieval also requires an Embedding service. Signing into an Agent subscription does not automatically supply these model API credentials. Basic mode remains available for explicit Memory storage and retrieval.
  • Existing deployments using remote plain HTTP must check and explicitly configure connection consent, including private-network and VPN addresses. Prefer HTTPS or an SSH tunnel for remote connections. --allow-insecure-http does not disable HTTPS certificate verification.

中文

PowerContext 1.0.0 RC2 是面向 1.0.0 的第二个候选版本。本次更新让首次配置和 Agent 接入更直接，并提供从 Memory 提炼 Experience、再生成 Skill 的可审核工作流。

主要变化

  • 通过向导完成首次配置：powercontext config init 提供中英文交互式向导，覆盖存储、模型 API、记忆能力、Dashboard 和 Agent 连接。向导生成 .env 与 .env.next-steps.md，给出启动 Server、创建和绑定 Scope、接入 Agent 的后续步骤。
  • 保存并复用 Agent 授权：支持为 Codex、Claude Code、DSH、OpenCode、Pi 和 WorkBuddy 保存 PowerContext 连接授权，供后续会话读取。保存的授权与 Server 地址绑定，仅在地址匹配时使用。
  • 从 Memory 到 Experience，再到 Skill：新增 Dream 工作流，可从选定的 Memory 条目提炼 Experience，并从已批准的 Experience 生成 Skill 候选。候选保留证据引用，经审核批准后形成正式的 Artifact Revision；Skill 的发布与安装仍需显式操作。可以通过 CLI、Client SDK 和 HTTP API 提交任务、查看状态并完成审核。
  • 明确远程 HTTP 连接的同意设置：连接非本机回环地址的明文 HTTP 服务时，需要显式同意。交互式安装会询问确认，非交互安装使用 --allow-insecure-http；保存的同意仅适用于对应地址。本机 localhost 和回环地址的 HTTP 连接仍默认允许。

安装与验证

uv tool install --force "powercontext[cli,server]==1.0.0rc2"
powercontext --version

版本输出应为 1.0.0rc2。首次使用可启动中文配置向导：

powercontext config init --language zh --output .env

按照生成的 .env.next-steps.md 完成 Server 启动、Scope 设置和 Agent 连接。安装 Codex 集成时，使用与 Python 包匹配的标签：

powercontext setup codex --ref powercontext-v1.0.0rc2

其他 Agent 集成也应使用 powercontext-v1.0.0rc2。预发布版本需要显式指定版本号。

升级说明

  • 升级前备份数据库与配置。Server 启动时会初始化 Dream 运行记录，并为已有 Artifact 与候选版本表补充 Memory 引用字段。Server、客户端和 Agent 集成应一起升级，随后重启 Server 和 Agent 会话。
  • Dream 和自动记忆处理需要配置相应的 Generation 服务；语义检索还需要 Embedding 服务。Agent 的订阅登录不会自动提供这些模型 API 凭据。基础模式仍可用于显式保存和检索 Memory。
  • 使用远程明文 HTTP 的现有部署，需要检查并显式配置连接同意，包括内网和 VPN 地址。远程连接优先使用 HTTPS 或 SSH 隧道；--allow-insecure-http 不会关闭 HTTPS 证书校验。

What's Changed

  • feat(config): add guided setup for first-time Server and Agent onboarding by @frf12 in #1545
  • feat(client): add explicit insecure HTTP opt-in across integrations by @frf12 in #1535
  • feat(setup): persist PowerContext Agent authorization by @frf12 in #1548
  • feat(dream): add reviewed Memory-to-Experience-to-Skill workflows by @Teingi in #1510
  • chore(release): prepare v1.0.0rc2 by @Teingi in #1555

Full Changelog: powercontext-v1.0.0rc1...powercontext-v1.0.0rc2

Contributors

frf12 and Teingi
Assets 4
Loading