Install Guild

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

Find your setup

DAC distributes Guild through your Codex workspace and your Claude team, so most people install little or nothing. Pick the row that describes you.

Codex or ChatGPT on DAC Enterprise
Nothing to install
DAC Guild is managed for your workspace, so it is already there. Start a task and ask Guild for something. If a prompt to connect appears, complete it once.
Claude Code on the DAC Claude team
Nothing local to install
The managed plugin and hosted Guild connection are provided by the team. Approve Guild browser sign-in when prompted; there is nothing local to install or configure.
Everything else
Use the detail below
Another MCP client (Cursor, VS Code, ChatGPT, OpenCode, and others use the generic hosted MCP setup), API-key authentication, a personal rather than DAC Enterprise or Team account, or a remote or scripted install. These are rare. Open the advanced sections below, or hand the whole playbook to an agent and let it work out the lane.

Whichever lane you are in, connect Microsoft 365 once at Settings → Connections to unlock email, calendar, Teams, and files.

After you connect: make Guild yours

Name your agent, add a portrait, choose its voice, and try a Quickpages project update from the onboarding guide.

Open onboarding guide

Need help or use another coding agent?Give an agent the universal setup request when your managed plugin is unavailable or you need a remote, scripted, or another-harness setup. The agent detects the lane so you do not have to.

Tell whatever coding agent you already have open:

Go to https://guild.dacgroup.com/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, connect and prove Guild tools first, show me what works now, then explore Guild skills from the remote catalog.

Guild currently supports DAC colleagues using their DAC Microsoft account. Share https://guild.dacgroup.com/install within DAC, or give an agent the raw playbook at https://guild.dacgroup.com/install/agent.

Hosted MCP for every setup

Codex gets Guild from the DAC ChatGPT Enterprise workspace and Claude Code from the DAC Claude team plugin. Both channels install and update the plugin for you, so keep that managed owner and avoid adding a second Guild MCP registration. Remote, scripted, and other supported harness setups can use the agent-guided playbook or the manual section below. Those paths connect directly to hosted Guild MCP.

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 and Codex have dedicated setup; every other MCP client (Cursor, VS Code, ChatGPT, OpenCode, Hermes, Antigravity, …) uses the generic hosted MCP setup. Detect whether the harness exposes its plugin command before choosing plugin or Tools-only mode.
2
Choose one installation lane
Claude Code and Codex normally arrive managed, with nothing to install. Preserve a managed plugin's owner and never duplicate its MCP registration. Claude native telemetry is organization-managed. Codex desktop uses the DAC workspace plugin when available. Every other harness registers the hosted HTTP endpoint; Guild ships no plugin or hooks for it.
3
Authenticate the applicable Guild tools
Use the harness-managed MCP browser OAuth flow for hosted Guild tools. A harness without browser OAuth can use a separately provisioned scoped MCP bearer. In Claude Code, authenticate the plugin's Guild server with `claude mcp login "plugin:dac-guild:guild"` or interactive `/mcp`. Show any interactive authorization page to the user immediately, keep the login command alive, and check its result. Never request broader sandbox or filesystem access for setup. If a native plugin is unavailable, connect hosted MCP directly and report which plugin features are missing.
4
Prove Guild tools and show value
Call named Guild tools directly when advertised. In the default code profile, dispatch get_setup_instructions and get_connection_readiness through call_tool(name="<tool>", arguments={...}). Use target=<detected target>, follow the connected-user contract, confirm identity and available systems without dumping scopes or tool inventories, then offer up to three safe prompts matched to what is connected. For Codex, never launch a nested `codex exec` as a substitute for readiness. First test Guild directly in the current task. Check `codex plugin list`, `codex mcp list`, and a Guild skill lookup. If the current task lacks the newly installed tools or guidance, explain that it may retain its initial plugin context and suggest the user start a new Codex task. Provide a copyable handoff containing the user's actual request and verified setup state, without credentials; create a task only if the user explicitly asks. Restart the app only if that new task still does not load the installed plugin or tools. Use target="claude_code" or target="codex" for those harnesses and target="generic" for every other MCP client.
5
Explore Guild skills
For normal work, call find_skill(query="<the user request>", load_best_match=true) or get_skill for an advertised slug; server-side skills are current without local sync. Plugin-managed skills update through their plugin owner. A selected skill with requires_install uses its returned install args with install_artifact. Only when the user explicitly requests a bulk local export, invoke install_recommended_artifacts(target=<detected target>, response_mode="full"), directly when advertised or through call_tool in the default code profile. Apply every write_plan entry where write=true, read and parse the JSON at the returned inventory_path, then pass that post-write inventory to first_run_smoke through the same profile-aware dispatch. Report Guild tools, plugin/adapter, telemetry status, and local artifact export separately.
6
Make Guild yours and try Quickpages
Offer optional personalization at https://guild.dacgroup.com/my-agent/settings#onboarding: name the agent, generate or upload a photo, choose its personality, and edit personal preferences. Users can revisit Settings or ask for a change anytime, such as 'Always show screenshots inline in monday.com task updates.' Follow get_setup_instructions for the current context read, merge, save, and readback workflow; preserve unrelated preferences and report pending review honestly. Showcase Quickpages with 'Draft a Quickpage project update with an executive summary, screenshots, and next steps.' Discover the current tools or skill, preview first, and confirm the audience before publishing; a demo is not publication consent and DAC access remains the default. This optional personalization path is separate from the governed priorities interview.
7
Offer governed personalization
After the user has seen what works now, call find_skill(query="onboarding interview", load_best_match=true) and follow loaded_skill.skill_md. If get_skill is needed and is not advertised directly, dispatch it through call_tool(name="get_skill", arguments={"slug":"onboarding-interview"}). Offer the governed skill's brief, skippable flow exactly; do not substitute or maintain a second hard-coded questionnaire.

Setup path by harness

Every path uses the hosted endpoint https://mcp.guild.dacgroup.com/mcp.

Claude Code

The DAC Guild plugin and native telemetry policy are pushed to Claude Code by the team, and updates come through the organization's plugin channel. Preserve that managed owner and avoid duplicate Guild MCP registrations. Its bundled server uses https://mcp.guild.dacgroup.com/mcp. Authenticate the plugin's Guild server with `claude mcp login "plugin:dac-guild:guild"`, or in interactive `/mcp` select the plugin's Guild server and choose Authenticate. Complete the browser consent in a visible browser and keep the flow alive until it finishes. Restart Claude Code only when the managed plugin was newly enabled or refreshed.
Verify Claude native telemetry separately through managed policy, Collector receipt, owned raw archive, normalization, and the derived Langfuse projection.
When the managed plugin is absent, register the hosted Guild MCP endpoint through Claude Code's native MCP controls.

Codex

On a DAC ChatGPT Enterprise workspace there is normally nothing to install: DAC Guild is workspace-managed, so start a task and ask Guild for something. First test Guild directly in the current task. Check `codex plugin list`, `codex mcp list`, and a Guild skill lookup. If the current task lacks the newly installed tools or guidance, explain that it may retain its initial plugin context and suggest the user start a new Codex task. Provide a copyable handoff containing the user's actual request and verified setup state, without credentials; create a task only if the user explicitly asks. Restart the app only if that new task still does not load the installed plugin or tools.
If the entry is missing or disconnected: In Codex desktop, select the DAC workspace and open Plugins. If DAC Guild is available in the workspace-provided section, install or enable it and use its connection control. The workspace plugin supplies Guild skills and its connection; Compliance API ingestion supplies tracing.
For remote, scripted, or UI-blocked environments, register hosted MCP with codex mcp add guild --url https://mcp.guild.dacgroup.com/mcp, then authenticate with codex mcp login guild.
If plugin installation is blocked, use Tools-only mode: run codex mcp add guild --url https://mcp.guild.dacgroup.com/mcp, then codex mcp login guild. Hosted tools and Compliance API tracing still work; report packaged local plugin skills separately.

Other MCP clients

Cursor, VS Code, ChatGPT, OpenCode, Hermes, Antigravity, and every other MCP client use the generic setup: register the hosted HTTP MCP server https://mcp.guild.dacgroup.com/mcp in the client's MCP config (commonly { "mcpServers": { "guild": { "url": "https://mcp.guild.dacgroup.com/mcp" } } }), then approve the Guild browser sign-in.
In ChatGPT, use Settings → Apps & Connectors → Create with connector URL: https://mcp.guild.dacgroup.com/mcp/chatgpt

Harness integration

Hosted MCP supplies Guild tools. Claude Code uses organization-managed native telemetry. Every other MCP client connects directly to hosted MCP. Codex desktop normally gets the Guild plugin from its workspace catalog; direct MCP registration covers remote or blocked catalog installs. If a native plugin is unavailable, connect hosted MCP directly and report which plugin features are missing.

Claude Code

If the managed plugin is missing or out of date, ask the organization administrator to repair delivery through the organization's plugin channel.

Other MCP clients

Guild ships no plugin or hooks for these clients. The hosted Guild MCP server alone gives you tools, skills, memory, and personality.

Loading manual setup options…

Go to https://guild.dacgroup.com/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, connect and prove Guild tools first, show me what works now, then explore Guild skills from the remote catalog.

Hosted MCP for every setup

Harness integration

Install Guild

Find your setup

Codex or ChatGPT on DAC Enterprise

Claude Code on the DAC Claude team

Everything else

After you connect: make Guild yours

Hosted MCP for every setup

Agent playbook

Identify your harness

Choose one installation lane

Authenticate the applicable Guild tools

Prove Guild tools and show value

Explore Guild skills

Make Guild yours and try Quickpages

Offer governed personalization

Setup path by harness

Claude Code

Codex

Other MCP clients

Harness integration

Claude Code

Other MCP clients

Install Guild

Find your setup

Codex or ChatGPT on DAC Enterprise

Claude Code on the DAC Claude team

Everything else

After you connect: make Guild yours

Hosted MCP for every setup

Agent playbook

Identify your harness

Choose one installation lane

Authenticate the applicable Guild tools

Prove Guild tools and show value

Explore Guild skills

Make Guild yours and try Quickpages

Offer governed personalization

Setup path by harness

Claude Code

Codex

Other MCP clients

Harness integration

Claude Code

Other MCP clients