feat(pi): add native Pi Coding Agent support - #1259
Conversation
|
Testing for this change is complete.
The PR is ready for review. Please start reviewing when convenient. |
…nt-support # Conflicts: # README.md # docs/en/docs/how-to/install-and-run.md # docs/en/docs/index.md # docs/zh/docs/how-to/install-and-run.md # docs/zh/docs/index.md
…nt-support # Conflicts: # README.md # scripts/generate_js_operations.py
…nt-support # Conflicts: # README.md # docs/en/docs/index.md # docs/zh/docs/index.md # zensical.toml
|
Conflicts with current Validation completed:
Please begin review when convenient. |
|
License check failed |
|
The review feedback and the failed license check are addressed in a5f619c. The Pi secret check now uses the centralized boundary-aware scrubber, with regression coverage for password assignments, token-shaped credentials, PEM keys, and ordinary risk-based text. All files reported by the License Check now have Apache-2.0 headers. Testing is complete:
The branch is pushed and ready for review. |
|
All GitHub checks are now green, including License Check. The review feedback is addressed, the latest master is merged, and the branch is ready for review. Please review when convenient. |
|
GitHub currently reports merge conflicts with the latest master branch. Please resolve them and update the PR. Thanks! |
…nt-support # Conflicts: # src/powercontext/cli/system.py
|
I merged the current master (7915a4d) and resolved the CLI conflict while retaining both the Pi and Hermes setup/doctor commands. GitHub now reports the PR as mergeable. Validation completed:
The branch is pushed and ready for review. |
|
@pi-dal if we have supported pi, please submit another PR and update the readme to let users know this feature. |
|
@AlexStocks Added the requested README follow-up in #1309. It announces Pi Coding Agent support in the English, Chinese, and Japanese READMEs; provides a working Validation completed:
Please review #1309 when convenient. |
* feat(pi): add native Pi package * fix(pi): harden package compatibility * fix(pi): remove unverified version gate * feat(pi): align tools with Claude Code * fix(pi): complete Claude Code parity * refactor(pi): narrow native tool surface * fix(integrations): secure explicit writes and Git sources * docs: align integration installation refs * fix(integrations): harden remote setup * fix(pi): harden secret capture checks * fix(pi): retain captures after flush failures
Which issue or RFC does this PR close?
Closes #1258
Rationale for this change
Pi Coding Agent currently has no PowerContext integration. This adds the smallest native workflow that restores durable project context and transfers work between Pi sessions. It is deliberately not a field-for-field or operation-for-operation clone of the Claude Code integration.
What changes are included in this PR?
pc_*Memory and Handoff tools, with interactive confirmation and secret rejection for durable writes./pc flushoperations.Are there any user-facing changes?
Users can install with
powercontext setup piand access nativepc_*Memory/Handoff tools and/pcdiagnostics in Pi. No breaking API or persisted-format changes.How was this change tested?
mise exec -- make pi-testmise exec -- make test(547 passed, 1 skipped)mise exec -- make contract-testmise exec -- make docs-testmise exec -- make checkAI usage statement
Implemented with Codex (GPT-5) under user direction.