Give your existing coding agent memory, skills, approvals, and connector tools over MCP.
Let your agent set it up
Copy this one request into Claude Code, Codex, Cursor, VS Code, ChatGPT, or another supported coding agent. You do not need to choose a harness or follow terminal steps yourself.
Tell whatever coding agent you already have open:
Go to https://guild.dacdev.studio/install/agent and set up Guild for me. Detect this harness and operating system, use the recommended plugin when supported or the hosted MCP fallback, complete the applicable sign-in and verification, sync starter artifacts only when this harness supports local artifacts, and tell me what now works.
Most setups need only the copied request and one browser approval.
1
Your agent chooses the right path
It detects the harness and uses either its supported Guild plugin or hosted MCP Tools-only setup — never both.
2
You approve the Guild sign-in
Most clients use browser OAuth owned by your coding agent; opencode uses its documented bearer-token preflight. First sign-in creates your Guild profile.
3
Your agent proves it worked
It syncs applicable starter skills, runs the first-use checks, completes one safe Guild action, and reports what is ready.
Browser sign-in first, local install only when useful
Hosted Guild MCP normally uses browser OAuth and needs no local CLI; opencode is the documented bearer-token exception your agent handles. When a supported plugin or local compatibility feature is useful, Guild's one-time installer downloads the published binary, verifies its SHA-256 checksum, installs only for the current user, and carries no credentials. The public installer currently supports Windows x64, Linux x64, and macOS Apple silicon. Later updates are checksum-verified and restore the previous binary if validation fails. Normal setup never requires broader sandbox or filesystem access.
Review the technical playbookOptional detail for reviewers and agents: exact steps, harness setup paths, and local compatibility notes.
Agent playbook
The agent follows these steps; you do not need to execute them yourself.
1
Identify your harness
Work out which coding agent / harness and operating system you are running in (Claude Code, Codex, Cursor, VS Code, ChatGPT, Antigravity, opencode, …). Detect whether the harness exposes its plugin command before choosing plugin or Tools-only mode.
2
Choose one installation lane
For Claude Code, Codex, and Cursor, prefer the shipped Guild plugin/adapter because it registers https://mcp.guild.dacdev.studio/mcp itself; do not also add the MCP server manually. For other harnesses, register the hosted HTTP endpoint in Tools-only mode. Local Guild stdio is retired and unsupported.
3
Authenticate the applicable Guild tools
Use the harness-managed MCP browser OAuth flow for hosted Guild tools. opencode is the exception: it uses GUILD_MCP_TOKEN with oauth=false after a Guild CLI login preflight. Treat optional local doctor/transcript compatibility as a separate credential and never block hosted MCP success on it. Relay any device URL/code immediately and keep the command alive until approval or a clear timeout. Never request broader sandbox or filesystem access for setup. If plugin installation or local lifecycle compatibility is unavailable, finish in hosted MCP Tools-only mode and report the optional items separately.
4
Sync and validate local artifacts
Once Guild tools work, call get_setup_instructions(target=<detected target>) and follow the returned target-specific contract. For harnesses with local artifacts, call install_recommended_artifacts(target=<detected target>, response_mode="full"), apply every write_plan entry where write=true, then read the returned installed inventory file and pass its parsed JSON to first_run_smoke with the same target and scope. Use target="generic" for an unrecognized MCP client. ChatGPT has no local artifact sync.
5
Prove the setup
Run one safe useful Guild action, such as listing available skills, and report a capability matrix: Guild tools, plugin/adapter, optional local lifecycle compatibility, artifact sync, and first-run smoke. Tools-only is a supported completed state when the plugin lane is unavailable; unverified local artifacts must be reported as unverified, not silently treated as complete.
6
Offer governed personalization
After technical setup succeeds, use find_skill and get_skill to load the current "onboarding-interview" skill and offer to run it. Follow that governed workflow exactly; do not substitute or maintain a second hard-coded questionnaire.
Setup path by harness
Every path uses the hosted endpoint https://mcp.guild.dacdev.studio/mcp.
Claude Code
Preferred: install/update the public Guild CLI and its bundled Claude Code plugin. Windows x64 PowerShell: iwr https://guild.dacdev.studio/api/v1/install.ps1 -UseBasicParsing | iex; & $installPath plugin install claude_code. macOS Apple silicon or Linux x64: curl -fsSL https://guild.dacdev.studio/api/v1/install.sh | sh && "$HOME/.local/bin/guild" plugin install claude_code. The plugin registers the hosted MCP server, so do not run a second MCP-add command.
If plugin installation is unavailable, use Tools-only mode: claude mcp add --transport http --scope user guild https://mcp.guild.dacdev.studio/mcp
Codex CLI
Preferred: install/update the public Guild CLI and its bundled Codex plugin. Windows x64 PowerShell: iwr https://guild.dacdev.studio/api/v1/install.ps1 -UseBasicParsing | iex; & $installPath plugin install codex. macOS Apple silicon or Linux x64: curl -fsSL https://guild.dacdev.studio/api/v1/install.sh | sh && "$HOME/.local/bin/guild" plugin install codex. The plugin registers the hosted MCP server; no WSL or second MCP registration is required.
If this Codex build lacks plugin support, use Tools-only mode: run codex mcp add guild --url https://mcp.guild.dacdev.studio/mcp, then run codex mcp login --scopes mcp:apps,mcp:skills:install,mcp:approvals:decide,offline_access guild.
Cursor
Preferred: install/update the public Guild CLI and the shipped Cursor adapter. Windows x64 PowerShell: iwr https://guild.dacdev.studio/api/v1/install.ps1 -UseBasicParsing | iex; & $installPath plugin install cursor. macOS Apple silicon or Linux x64: curl -fsSL https://guild.dacdev.studio/api/v1/install.sh | sh && "$HOME/.local/bin/guild" plugin install cursor. This writes both ~/.cursor/mcp.json and ~/.cursor/hooks.json.
If the adapter is unavailable, use Tools-only mode: add { "mcpServers": { "guild": { "url": "https://mcp.guild.dacdev.studio/mcp", "transport": "http" } } } to ~/.cursor/mcp.json.
In Settings → Apps & Connectors → Create, use connector URL: https://mcp.guild.dacdev.studio/mcp/chatgpt
Hermes
Register the hosted HTTP MCP server https://mcp.guild.dacdev.studio/mcp in your Hermes MCP config. Local Guild stdio is retired.
Antigravity
Add mcpServers.guild.serverUrl = "https://mcp.guild.dacdev.studio/mcp" to ~/.gemini/antigravity/mcp_config.json (desktop) or ~/.gemini/antigravity-cli/mcp_config.json (CLI)
opencode
Install or update the public Guild CLI, then log in from a shell. Windows x64 PowerShell: iwr https://guild.dacdev.studio/api/v1/install.ps1 -UseBasicParsing | iex; & $installPath login. macOS Apple silicon or Linux x64: curl -fsSL https://guild.dacdev.studio/api/v1/install.sh | sh && "$HOME/.local/bin/guild" login. Load GUILD_MCP_TOKEN from ~/.guild-mcp/credentials.json without printing it, then add to opencode.json: { "mcp": { "dac-guild": { "type": "remote", "url": "https://mcp.guild.dacdev.studio/mcp", "headers": { "Authorization": "Bearer {env:GUILD_MCP_TOKEN}" }, "oauth": false } } }.
Other MCP-capable harnesses
Register the hosted HTTP MCP server https://mcp.guild.dacdev.studio/mcp using your harness's MCP config. Local Guild stdio is retired.
Optional local compatibility
Hosted MCP is the primary Guild tool plane. Some harnesses can also install a local plugin or adapter for doctor and lifecycle compatibility. This is reported separately and never blocks a working hosted setup. If plugin installation or local lifecycle compatibility is unavailable, finish in hosted MCP Tools-only mode and report the optional items separately.
Claude Code
Marketplace fallback: /plugin marketplace add DAC-Group/agno-guild then /plugin install dac-guild@dac-guild.
Optional local doctor and transcript compatibility uses a separate Guild CLI credential. Windows x64 PowerShell: $guild = if (Test-Path "C:\source\guild.exe") { "C:\source\guild.exe" } else { Join-Path $env:LOCALAPPDATA "Programs\guild\guild.exe" }; & $guild login --no-browser --scopes "mcp:full offline_access". macOS Apple silicon or Linux x64: "$HOME/.local/bin/guild" login --no-browser --scopes "mcp:full offline_access". Do not block hosted MCP setup on this optional sign-in.
Restart Claude Code once after a fresh CLI install, then verify with /dac-guild:guild-doctor. For later plugin-only refreshes, /reload-plugins is enough.
Codex CLI
The optional Codex SessionEnd hook requires Node.js 22+. New or changed plugin hooks stay disabled until the user reviews them in /hooks; hosted Guild tools remain usable either way.
Optional local doctor and transcript compatibility uses a separate Guild CLI credential. Windows x64 PowerShell: $guild = if (Test-Path "C:\source\guild.exe") { "C:\source\guild.exe" } else { Join-Path $env:LOCALAPPDATA "Programs\guild\guild.exe" }; & $guild login --no-browser --scopes "mcp:full offline_access". macOS Apple silicon or Linux x64: "$HOME/.local/bin/guild" login --no-browser --scopes "mcp:full offline_access". Do not block hosted MCP setup on this optional sign-in.
Restart Codex once after plugin installation, then verify with `guild doctor --harness codex`.
Cursor
The shipped adapter command is guild plugin install cursor. Restart Cursor and verify the Guild MCP server and lifecycle-hook entries load.
Optional local doctor and transcript compatibility uses the separate Guild CLI credential. Windows x64 PowerShell: $guild = if (Test-Path "C:\source\guild.exe") { "C:\source\guild.exe" } else { Join-Path $env:LOCALAPPDATA "Programs\guild\guild.exe" }; & $guild login --no-browser --scopes "mcp:full offline_access". macOS Apple silicon or Linux x64: "$HOME/.local/bin/guild" login --no-browser --scopes "mcp:full offline_access". Do not block hosted MCP setup on it.
Hermes(local adapter coming soon)
Plugin + lifecycle hooks: coming soon (tracked by todo 569). For now, add only the Guild MCP server above — you still get tools, skills, memory, and personality.
Other MCP-capable harnesses
No hook layer here — the Guild MCP server alone still gives you tools, skills, memory, and personality.
Loading manual setup options…
Manual setup and permission repairChoose your harness for a ready-to-paste prompt, direct configuration, or a client-specific permission reconnect.
Choose your harness
Prompt for your agent
Paste this into the local agent that has access to your machine.
Set up Guild in Codex CLI.
Recommended on Windows x64, Linux x64, and macOS Apple silicon — install/update the public Guild CLI, then install its bundled Codex plugin. No WSL or hand-wired hooks file is required:
Windows x64 PowerShell (one command keeps the freshly installed CLI on PATH):
iwr https://guild.dacdev.studio/api/v1/install.ps1 -UseBasicParsing | iex; & $installPath plugin install codex
macOS Apple silicon or Linux x64:
curl -fsSL https://guild.dacdev.studio/api/v1/install.sh | sh && "$HOME/.local/bin/guild" plugin install codex
The Codex plugin path requires Node.js 22+ for its optional SessionEnd hook. Codex keeps new or changed plugin hooks disabled until the user reviews them in /hooks; hosted Guild tools remain usable regardless of that hook decision.
The plugin registers the hosted Guild MCP server; do not add a second MCP block on the recommended path. Complete Guild tools in Codex using hosted MCP OAuth:
codex mcp login --scopes mcp:apps,mcp:skills:install,mcp:approvals:decide,offline_access guild
Optional local doctor and transcript compatibility uses a separate Guild CLI credential. Run this only for those local capabilities; immediately open the printed URL/code and leave the command running until it confirms success:
Windows x64 PowerShell:
$guild = if (Test-Path "C:\source\guild.exe") { "C:\source\guild.exe" } else { Join-Path $env:LOCALAPPDATA "Programs\guild\guild.exe" }; & $guild login --no-browser --scopes "mcp:full offline_access"
macOS Apple silicon or Linux x64:
"$HOME/.local/bin/guild" login --no-browser --scopes "mcp:full offline_access"
If this Codex build does not support plugins, Tools-only mode is a valid completed setup: register the hosted MCP server with Codex, then run the Guild tools login. Upgrade Codex later to add lifecycle hooks:
codex mcp add guild --url https://mcp.guild.dacdev.studio/mcp
codex mcp login --scopes mcp:apps,mcp:skills:install,mcp:approvals:decide,offline_access guild
Restart Codex once after plugin/config and hosted Guild tools sign-in are complete. Do not block hosted MCP success if optional local compatibility is skipped.
After restart, use the Guild MCP setup tools to finish the local runtime setup:
1. Call get_setup_instructions with target="codex".
2. Call install_recommended_artifacts with target="codex", scope="user", profile="starter", response_mode="full".
3. Apply each returned write_plan entry where write=true, creating parent directories.
4. Read the returned installed inventory JSON and pass it to first_run_smoke with the same target and scope.
5. Prove one safe useful action, then report Guild tools, plugin/adapter, optional local lifecycle compatibility, artifact sync, and smoke separately.
6. Restart again only if the newly written skills are not discovered in the current session.
After technical setup succeeds, use find_skill and get_skill to load the current "onboarding-interview" skill, then offer to run that governed workflow. Do not substitute a hard-coded questionnaire.
Never ask the user to grant full filesystem/sandbox access just to install or authenticate Guild; diagnose the actual command, PATH, OAuth, or unsupported-plugin issue.
If the current Codex session cannot see Guild MCP tools yet, tell me: "Restart Codex, then ask me to sync Guild artifacts."
Verify in the fresh session by asking: "what Guild skills are available?"
Direct configuration and commands
Windows x64 PowerShell:
iwr https://guild.dacdev.studio/api/v1/install.ps1 -UseBasicParsing | iex; & $installPath plugin install codex
macOS Apple silicon or Linux x64:
curl -fsSL https://guild.dacdev.studio/api/v1/install.sh | sh && "$HOME/.local/bin/guild" plugin install codex
Then authenticate hosted Guild tools in Codex:
codex mcp login --scopes mcp:apps,mcp:skills:install,mcp:approvals:decide,offline_access guild