pi-context-decisions

Give Pi the skills relevant to your task, without advertising your entire collection up front.

This extension uses a decision model to pick skill descriptions for Pi to see. As your task changes, it can add more. Skills already advertised stay available for the rest of that session branch.

It can also filter external tools, MCP servers and extension tool groups. That is a separate feature, off by default.

When is it useful?

• You have lots of skills. For a task such as “Review these validation changes,” it can advertise relevant review skills instead of unrelated release or UI skills.
• Your work changes during a session. Move from reviewing code to preparing a release, and relevant release skills can be added without dropping the earlier ones.
• You have many tools or MCP servers. Enable tool filtering to make relevant external tools available as needed, while keeping essentials always allowed.

If you only have a few skills, you may not need it: by default, fewer than eight automatic skills are left unfiltered. Decision calls add latency and may incur provider charges.

Install and set up

Requires Node 22.18+ and Pi 1.1.0 APIs.

pi install npm:pi-context-decisions

Keep this package first or near the start of your configured extensions. In Pi:

1. Run /decisions.
2. Open Advanced, choose Provider / execution, then Model. Supported backends are Pi classifiers, TypeSafe, OpenAI and OpenRouter.
3. If credentials are missing, configure the matching TYPESAFE_API_KEY, OPENAI_API_KEY or OPENROUTER_API_KEY, or use Pi's /login <provider>. OpenAI needs an API key, not Codex/ChatGPT OAuth.
4. In Skills, leave Skill filtering on. Optionally choose skills under Always allowed · Global or Always allowed · Project; save allowlist edits with Ctrl+S.
5. Close the dialog and start a fresh session before sending your first task.

No decision model is selected by default. Until you select one, nothing is filtered and no decision calls are made. Selecting a model does not change either filtering switch. A fresh session matters because filtering never retracts skills or tools already made available on a branch.

Use Tab to switch settings tabs, Enter to select, Space to toggle, and Esc to go back or close.

Use it

Ask Pi to work normally, for example:

Review these validation changes for missing edge cases.

The picker scores unadvertised skills and adds relevant ones. By default it runs on each prompt and adds up to 12 new skills per round. It advertises names, descriptions and locations—not full skill bodies.

Use /decisions history to see committed additions on this branch, or /decisions status to check setup and the last decision:

/decisions history
/decisions status

To try tool filtering, open /decisions → Tools, enable Tool filtering, and choose a mode:

• tools: pick individual external tools.
• mcp: pick whole MCP-server or extension tool groups.

Add essentials to the Tools tab's always-allowed lists, then start a fresh session. /decisions tools list and /decisions mcp list show availability without making decision calls.

Know before enabling

• Metadata leaves Pi. The selected decision provider receives bounded user-task text and skill names/descriptions. Tool filtering also sends tool/group metadata. It does not send skill bodies, tool arguments/results or conversation transcripts.
• Additions are permanent on that branch. Removing an always-allowed entry does not retract an earlier addition. A failed decision adds nothing by default; existing additions stay.
• This is not a sandbox. Skill filtering changes advertisements, not permissions. Tool filtering gates Pi tool calls, but does not stop server connections, hide discovery results or restrict bash and other processes.

Documentation

• Settings, commands and always-allowed lists
• Providers and credentials
• How skill picking works
• Tool/MCP filtering and its limitations
• Library API
• Development and tests · Publishing
• Changelog

MIT license.