Selection file format
Field-by-field reference for the powermise selection TOML.
The file powermise saves for each AI setup, in
~/.config/powermise/selections/<name>.toml. You don’t need to edit it — the
setup editor does — but it’s plain TOML if you want to.
schema_version = 2name = "engineering-agents"catalog = "powermise-profiles"harnesses = ["claude", "codex", "gemini"]
[preferences]include_desktop_apps = falseFields
Section titled “Fields”| Field | Type | Required | Notes |
|---|---|---|---|
schema_version | integer | yes | Currently 2. Version 1 files still load. |
name | string | yes | Lowercase letters, numbers, and single hyphens. Must match the file name, and names the mise file: conf.d/powermise-<name>.toml. |
catalog | string | yes | The catalog this selection resolves against: powermise-profiles. |
harnesses | list of strings | yes | Curated harness IDs, for example claude, codex, gemini. |
mcp_servers | list of strings | no | MCP server IDs to add to the setup’s agents, for example context7. Leave it out to use the harnesses’ recommendations. |
integrations | list of strings | no | Plugin IDs from the catalog to install with the agents’ own CLIs, for example claude-github. Only plugins for agents in the setup are installed. Leave it out to use the harnesses’ recommendations. |
preferences.include_desktop_apps | bool | no | Default false. Adds each harness’s desktop companion apps where the platform has a provider. |
Version 1 files
Section titled “Version 1 files”Selections written by the retired powermise CLI are schema_version = 1 and
may also contain machine_roles, preferences.auto_prune, and
preferences.update_system_packages. They still load: powermise reads them as
version 2, ignores those fields, and writes version 2 the next time the setup is
saved. Tool cleanup is now mise prune --tools, and package updates are mise’s
(see From the terminal).
A file with a newer schema_version than this powermise knows is skipped
rather than misread.
See Selections for how a selection resolves.