DAC

Guild

My Agent

SkillsK
MemoryO
Settings,

Help

Install GuildN
How It Works?
Sign out

Citizen

Install Guild

Guild gives your existing coding agent memory, skills, approvals, and connector tools over MCP.

The easy way: let your agent do it

Already have a coding agent open (Claude Code, Codex, Cursor, VS Code, ChatGPT, …)? Just point it at this page. It figures out the rest — no picking a harness, no copy-pasting a setup prompt.

Tell whatever coding agent you already have open:

Go to https://guild.dacdev.studio/install/agent and set up Guild for me — figure out which harness you're running in, add the Guild MCP server, sign me in through the browser, then sync the starter skills and tell me what you can now do.

Share https://guild.dacdev.studio/install with anyone who wants Guild. The agent can also fetch the raw, machine-readable playbook at https://guild.dacdev.studio/install/agent.

MCP endpoint: https://mcp.guild.dacdev.studio/mcp

What the agent does (the playbook)

This is exactly what the agent follows when it lands on this page. You don't need to read it — it's here so you know what to expect.

  1. 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. 2

    Add the Guild MCP server

    Mount the hosted Guild MCP endpoint https://mcp.guild.dacdev.studio/mcp using your harness's method (see the per-harness list). Always use the hosted HTTP endpoint, not local stdio.

  3. 3

    Install the Guild plugin + lifecycle hooks if your harness supports them

    This layer is ADDITIVE and fail-soft on top of the MCP server. The hooks add governance gating, telemetry, and automatic identity / memory / skill context injection at session start — but MCP-server-only is still a valid end state, so a missing or flaky hook layer never blocks setup. Use the "plugin + hooks" line for your harness below (Claude Code and Codex CLI ship it today; Cursor and Hermes are coming soon, MCP-only for now; ChatGPT and other harnesses get tools / skills / memory / personality from the MCP server with no hook layer). If the plugin install fails, fall back to MCP-server-only — never block the agent loop on the hook layer.

  4. 4

    Sign the user in

    Report two auth states separately: Guild tools is hosted MCP OAuth; Local lifecycle hooks is the local Guild CLI credential. When a device flow starts, relay the URL/code immediately and keep the command alive until approval or a clear timeout. The first hosted sign-in creates the profile automatically. Never ask the user to change sandbox/full-filesystem permissions for Guild setup; diagnose command availability, PATH, OAuth, or harness support instead.

  5. 5

    Run the post-install setup

    Once the Guild MCP tools are available, call get_setup_instructions(target=<your harness>) and follow it. Both setup tools default to target="codex", so always pass your detected harness (e.g. claude_code, cursor, vscode, opencode, antigravity, codex) — otherwise you sync Codex-formatted files into the wrong harness. When it says to sync local artifacts, call install_recommended_artifacts(target=<your harness>, response_mode="full"); the default inventory mode returns no write_plan, so you must request full mode, then write every write_plan entry where write=true (creating parent directories) and restart the harness so the new skills load.

  6. 6

    Offer the quick onboarding interview

    Optionally ask three questions — what should Guild remember about how the user works, which clients/projects/workflows matter most right now, and how proactive the PA should be — and save confirmed answers with the Guild memory / user-context tools.

  7. 7

    Verify

    Return one compact capability result: Guild tools ✓, Plugin ✓/not supported, Lifecycle hooks ✓/not supported, Skills synced ✓/unverified. For Codex, verify with `codex mcp get guild` and `guild doctor --harness codex`; for Claude Code, run `/reload-plugins` and `/dac-guild:guild-doctor`. Tools-only is a successful degraded state, not a failed install.

Adding the Guild MCP server, per harness

The agent uses the row for its own harness. All default to the hosted HTTP endpoint, not local stdio.

Claude Code

  • Run: claude mcp add --transport http --scope user guild https://mcp.guild.dacdev.studio/mcp

Codex CLI

  • Add to ~/.codex/config.toml: [mcp_servers.guild] with 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

  • Add to .cursor/mcp.json: { "mcpServers": { "guild": { "url": "https://mcp.guild.dacdev.studio/mcp", "transport": "http" } } }

VS Code

  • Add to .vscode/mcp.json: { "servers": { "guild": { "type": "http", "url": "https://mcp.guild.dacdev.studio/mcp" } } }

ChatGPT

  • 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 (not local stdio).

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

  • Add to opencode.json: { "mcp": { "dac-guild": { "type": "remote", "url": "https://mcp.guild.dacdev.studio/mcp", "oauth": true } } }

Other MCP-capable harnesses

  • Register the hosted HTTP MCP server https://mcp.guild.dacdev.studio/mcp using your harness's MCP config (not local stdio).

Then install the plugin + lifecycle hooks

This layer is additive and fail-soft. The hooks add governance gating, telemetry, and automatic identity / memory / skill context injection at session start — but adding only the MCP server above is still a valid setup, so a plugin hiccup never strands the agent. If the plugin install fails, fall back to MCP-server-only — never block the agent loop on the hook layer.

Claude Code

  • Install/update the CLI and bundled plugin. Windows PowerShell: iwr https://guild.dacdev.studio/api/v1/install.ps1 -UseBasicParsing | iex; guild plugin install claude_code. macOS/Linux: curl -fsSL https://guild.dacdev.studio/api/v1/install.sh | sh && "$HOME/.local/bin/guild" plugin install claude_code. If the bundled path is unavailable, use the Claude marketplace fallback: /plugin marketplace add DAC-Group/agno-guild then /plugin install dac-guild@dac-guild.
  • Sign in the Local lifecycle hooks without relying on the already-running harness PATH. Windows 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/Linux: "$HOME/.local/bin/guild" login --no-browser --scopes "mcp:full offline_access". Relay the printed device URL/code immediately and keep the process alive until it succeeds. This is independent of the Guild tools MCP OAuth consent.
  • 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 when guild was already available before the refresh.

Codex CLI

  • Install/update the CLI and bundled plugin + 8 lifecycle hooks. Windows PowerShell: iwr https://guild.dacdev.studio/api/v1/install.ps1 -UseBasicParsing | iex; guild plugin install codex. macOS/Linux: curl -fsSL https://guild.dacdev.studio/api/v1/install.sh | sh && "$HOME/.local/bin/guild" plugin install codex. It registers the hosted MCP server and enables hooks/plugin_hooks; no WSL or hand-wired hooks file is required. If this Codex build lacks plugin support, complete Tools-only mode and offer a Codex upgrade path.
  • Sign in the Local lifecycle hooks without relying on the already-running harness PATH. Windows 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/Linux: "$HOME/.local/bin/guild" login --no-browser --scopes "mcp:full offline_access". Relay the printed device URL/code immediately and keep the process alive until it succeeds. This is independent of the Guild tools Codex MCP OAuth login.
  • Restart Codex once after plugin installation and both auth states complete, then verify with `guild doctor --harness codex`.

Cursor(coming soon)

  • Plugin + lifecycle hooks: coming soon (tracked by todo 568). For now, add only the Guild MCP server via the ~/.cursor/mcp.json entry above — you still get tools, skills, memory, and personality.

Hermes(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.

Prefer to set it up by hand?

Pick your harness for a ready-to-paste setup prompt and the direct command.

Pick the harness

Prompt to give your agent

Paste this into the local agent that has access to the user's machine.

Set up Guild in Codex CLI.

Recommended on Windows, macOS, and Linux — install/update the public Guild CLI, then install its bundled Codex plugin. No WSL or hand-wired hooks file is required:
Windows PowerShell (one command keeps the freshly installed CLI on PATH):
iwr https://guild.dacdev.studio/api/v1/install.ps1 -UseBasicParsing | iex; guild plugin install codex
macOS/Linux:
curl -fsSL https://guild.dacdev.studio/api/v1/install.sh | sh && "$HOME/.local/bin/guild" plugin install codex

Complete the two independent auth states:
1. Guild tools in Codex (hosted MCP OAuth):
codex mcp login --scopes mcp:apps,mcp:skills:install,mcp:approvals:decide,offline_access guild
2. Local lifecycle hooks (Guild CLI credential): run this, immediately open the printed URL/code on this phone or another device, and leave the command running until it confirms success:
Windows 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/Linux:
"$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 in ~/.codex/config.toml, then run the Guild tools login. Upgrade Codex later to add lifecycle hooks:
[mcp_servers.guild]
url = "https://mcp.guild.dacdev.studio/mcp"
enabled = true
required = false
startup_timeout_sec = 10
tool_timeout_sec = 60
codex mcp login --scopes mcp:apps,mcp:skills:install,mcp:approvals:decide,offline_access guild

Restart Codex once after the plugin/config and both sign-ins are complete.

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. Write each returned write_plan entry where write=true, creating parent directories.
4. Restart again only if the newly written $ skills are not discovered in the current session.
5. Ask the optional three-question onboarding interview and save confirmed answers with Guild MCP memory/user-context tools.

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 command

Add [mcp_servers.guild] url = "https://mcp.guild.dacdev.studio/mcp" to ~/.codex/config.toml, then run codex mcp login --scopes mcp:apps,mcp:skills:install,mcp:approvals:decide,offline_access guild