Everything installs relative to cwd right now (project-level config). A few hosts also support a user-level/global location — ~/.cursor/mcp.json, ~/.claude/skills/, ~/.gemini/settings.json, and so on (see src/hosts/README.md) — but there's no way to target that from agent-add today.
A --global flag that writes to the user-level location where the host actually supports one. Hosts that don't have a documented global spot for a given asset type would just need a clear "not supported" response, same as the existing per-asset-type capability checks.
Everything installs relative to cwd right now (project-level config). A few hosts also support a user-level/global location — ~/.cursor/mcp.json, ~/.claude/skills/, ~/.gemini/settings.json, and so on (see src/hosts/README.md) — but there's no way to target that from agent-add today.
A --global flag that writes to the user-level location where the host actually supports one. Hosts that don't have a documented global spot for a given asset type would just need a clear "not supported" response, same as the existing per-asset-type capability checks.