Package Exports
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@quantpartners/pca) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
PCA
Git for AI context.
PCA is an open source CLI that gives your project persistent AI context. It keeps decisions, project memory, branch state, and AI task context close to your code.
Installation
npm install -g @quantpartners/pcacd your-project
pca initpca init creates the local memory structure and installs Git hooks. If the workspace is already initialized, run:
pca install-hooksHow It Works
PCA uses Git as the trigger, Markdown as the source of truth, and SQLite in .pca/pca.db as the operational index.
After a relevant Git commit, the hook records a pending decision and exits:
git commit -m "feat: implement checkout flow"💡 PCA: Decision pending. Run 'pca commit' to save it.Review pending decisions when you are back at the shell:
pca commit┌─────────────────────────────────────────┐
│ PCA — Save this decision? │
│ commit: feat: implement checkout flow │
│ [Y] Yes, record [N] No, skip │
└─────────────────────────────────────────┘
> yAccepted decisions are recorded in project memory. Skipped decisions are resolved and removed from the pending queue.
Branch changes are tracked by the post-checkout hook so PCA can keep branch-local context state.
Daily Flow
# New project
pca init
pca bootstrap
pca task "describe your task"
# Every day
git commit -m "feat: something"
pca commit
pca task "next task"
# When ready for cloud memory
pca setup
pca syncCommands
Local commands
These work without an OpenAI API key.
| Command | Description |
|---|---|
pca init |
Initialize PCA memory in this project. |
pca bootstrap |
Generate initial context from an existing project. |
pca status |
Show project memory status. |
pca commit |
Record decisions or review pending ones. |
pca logs |
List active context commit history. |
pca logs --all |
List active and deprecated context commits. |
pca forget |
Deprecate a context commit. |
pca recovery |
Restore a deprecated context commit. |
pca task |
Generate compact context for your AI agent. |
pca doctor |
Diagnose your PCA setup. |
pca install-hooks |
Reinstall Git hooks in the current project. |
pca help |
Show the CLI guide. |
Cloud commands
These require an OpenAI API key. Run pca setup first.
| Command | Description |
|---|---|
pca setup |
Configure your OpenAI API key. |
pca sync |
Upload memory to OpenAI Vector Store. |
pca query |
Search memory via RAG. |
pca visual add |
Add image to visual memory. |
pca close |
Close a task and update changelog. |
PCA Cloud
Coming in 2.0.0:
| Command | Description |
|---|---|
pca login |
Sign in to PCA Cloud. |
pca logout |
Clear cloud session. |
pca whoami |
Show account status. |
Forget And Recovery
Use pca forget when a context commit is no longer valid. PCA marks it as deprecated instead of deleting it.
pca forget
pca logs --allUse pca recovery to restore a deprecated commit:
pca recoveryRules
- Local-only mode works with no API key required.
- Markdown files in
pca/remain the source of truth. - Agents must not read the full
pca/folder. - Use
pca taskbefore every AI agent session. - Use
pca committo review pending decisions and record context. - Cloud commands require
pca setupfirst.
License
MIT
Links
- npm: @quantpartners/pca
- GitHub: thequantpartners/pca