Custom Config Paths

Choose each agent's config file — Settings → General → Agent configuration lists every connected AI client; pick one, hit Change path, and aim the vault at that tool's real MCP config file — Perfect for named profiles like Hermes, portable installs, or any agent that keeps its MCP file somewhere unusual — Also reachable from the pencil button on each client in Connection and in Registry

Type paths the way you think of them — ~, %APPDATA%, and ${ENV_VAR} all expand to the real location

Test before you save — A built-in check confirms the file is readable and writable — or that it can be created where you point — before anything is stored

One file, everywhere it matters — Connect, repair, Registry apply, and adopt all honor the same chosen path, so installs and managed MCP servers always land where the agent actually reads them

See custom paths at a glance — A Custom path badge marks overridden clients in Settings, Connection, and Registry; Use default restores the standard location in one click without deleting the custom file

Devin joins the managed registry — Devin's config location is now verified, so Registry treats it as a full managed client instead of detect-only — adopt its existing MCP entries or apply your definitions through the same reviewed preview

OpenCode imports keep the whole tool call — Imported OpenCode sessions now record what each tool actually did — the command that ran, the file it touched, the pattern it searched, the URL it fetched — along with the output log and applied edits, instead of a bare "[tool: name]" line

Long tool logs stay tidy — Big command outputs collapse to a short preview in the conversation view with a Show all toggle, so a giant log doesn't flood the transcript