Prime Agent
prism and prism-responses providers into Prime Agent's models.json, the file its model registry loads custom providers from. On Windows it also finds a Prime Agent installed inside WSL through the \\wsl$ share.Last updated Reviewed against Prism v0.3.26
Where the config lives
Prism resolves Prime Agent's directory in the same order Prime Agent itself does:
| Priority | Location |
|---|---|
| 1 | $PRIME_AGENT_CODING_AGENT_DIR if set |
| 2 | $PI_CODING_AGENT_DIR if set — the legacy variable name |
| 3 | ~/.prime/agent |
If you have moved Prime Agent's data directory with either variable, Prism follows the same override instead of writing to ~/.prime/agent blindly.
%USERPROFILE%\\.prime\\agentdirectory does not exist, Prism looks for a default WSL distro's ~/.prime/agent through the \\wsl$ share. Prism never starts WSL itself — the fallback is only consulted while the distro is already running. The loopback proxy URL works from WSL through localhost forwarding.One-click setup
Open the Agents tab
Agents. Prime Agent is detected via its config directory or the prime-agent binary.Click Setup
models.json and keeps a one-time backup. Your own providers are untouched.Pick a model in Prime Agent
What Prism writes
{
"providers": {
"prism": {
"baseUrl": "http://127.0.0.1:11434/v1",
"apiKey": "prism",
"api": "openai-completions",
"models": [
{
"id": "glm-5.1:cloud",
"name": "GLM 5.1 (Ollama Cloud)",
"input": ["text", "image"],
"contextWindow": 128000,
"maxTokens": 16384,
"reasoning": true,
"thinkingLevelMap": {
"off": null,
"minimal": null,
"low": "low",
"medium": "medium",
"high": "high",
"max": null
}
}
]
},
"prism-responses": {
"baseUrl": "http://127.0.0.1:11434/v1",
"apiKey": "prism",
"api": "openai-responses",
"models": []
}
}
}The two blocks exist because Prime Agent binds one protocol per provider. A block with no models is removed on re-sync, and the legacy prism-codex provider is cleaned up.
settings.json is never modified
Prism registers models and nothing else. It does not write defaultProvider or defaultModel, so the model Prime Agent starts with stays your choice.settings.json is only read, never written.
Add MCP servers
Prime Agent only executes MCP servers declared in its user-scope settings file; project-level entries are ignored. Prism writes its gateway entry there under mcpServers. See MCP Gateway.