pi-set-model

Remembers Pi's selected model and thinking level for each project folder. Requires Pi 0.84.4 or newer.

After selecting a model and thinking level, explicitly save that combination for the current working directory with /set-model set. New Pi sessions opened in that directory restore it, rather than retaining the model selected in another project. Later thinking-level changes for the saved model automatically update the preference to match Pi's footer. A later /model change does not replace the saved project model unless you run /set-model set again.

Preferences are stored in the project at .pi/set-model.json; they are never shared with another project. Pi must trust the project before the extension reads or writes this project-local setting.

Install

Avoid duplicate installation. Install this npm package or the GitHub bundle, not both. Loading both copies can duplicate commands and preference-restoration handlers.

pi install npm:pi-set-model

Or install the full collection:

pi install git:[email protected]:hknet/pi-extensions@main

Commands

/set-model          # view the saved preference for this folder
/set-model view     # view the saved preference for this folder
/set-model set      # save the active model and thinking level
/set-model clear    # stop restoring a preference for this folder

Autocomplete completes /setm... to /set-model without adding a trailing space, then offers view, set, and clear.

The folder is Pi's current working directory. Run Pi from the project root when you want one preference for the whole project. The setting is saved at <cwd>/.pi/set-model.json.

If the saved model is unavailable or has no configured API key, Pi keeps the active model and shows a warning. Empty or malformed preference fields are ignored. Thinking levels are restored after the model and explicitly clamped with Pi's model-capability helper; the restore notice identifies an unsupported saved level. When the session ends, the model and thinking level that were active before the project preference was applied are restored.

Issues and feedback

Found a bug or have a feature request? Please report it on GitHub Issues.

For security vulnerabilities, please use GitHub's private vulnerability reporting instead of opening a public issue.