guide
Prime Agent settings: global and project configuration
Settings are stored as JSON and deep-merged from global ~/.prime/agent/settings.json to project .prime/agent/settings.json, with selected CLI flags and environment variables overriding specific fields. Project settings can restrict but not enable a globally disabled option. Restart the agent or daemon after changing core settings.
First-party announcement, documentation, release, or installer.
Global vs project settings
Global settings establish the default posture. Project settings refine that posture for one repository but cannot silently enable a globally disabled feature.
Precedence order
~/.prime/agent/settings.json
.project/.prime/agent/settings.jsonSafe defaults
Keep risky capabilities disabled until you have a repeatable reason to enable them. That includes autonomous continuations, unreviewed extensions, and any setting that broadens trust boundaries.
Context files and prompts
Context files provide repository rules and conventions. They should be small, readable, and stable; if they drift too far, consolidate them instead of scattering policy across the tree.
Themes and keybindings
Theme and keybinding settings control interface ergonomics. They are user-facing and reversible, so they make a good first place to confirm that configuration precedence works.
When to restart
Restart the agent or daemon when core settings change. If behavior still looks stale after a restart, check whether a project override or cached session state is winning.