Wyrd docs v0.4.1 Use with your coding agent Reference GitHub

Get started / Use with your coding agent

Use with your coding agent

Point your coding agent at the Wyrd docs, then connect it to your Wyrd server so it can read your declarations, verdicts, and evidence.

Give your agent the docs

FileURLHolds
llms.txthttps://docs.bohmian.ai/wyrd/llms.txtAn index of every page, with where to start
llms-full.txthttps://docs.bohmian.ai/wyrd/llms-full.txtEvery page in full, with its YAML and code

Paste either URL into your agent’s chat, or add it to the agent’s project instructions.

Connect your agent over MCP

Starting from scratch? wyrd init guided starts the server, connects your agent, and has it set up your project. To connect an agent to a server that is already running, you need the agent installed and opened once.

bash
wyrd mcp install --host claude-code
text
claude-code: added /Users/you/.claude.json

Run wyrd mcp install without --host to pick from the agents it finds. Restart the agent to load the entry. The agent starts wyrd mcp proxy, which signs each call with the credential wyrd init saved; the agent’s configuration file never holds it.

Agent--host
Claude Codeclaude-code
Codex CLI and IDEcodex
Cursorcursor
GitHub Copilot CLIcopilot-cli
GitHub Copilot in VS Codevscode
Pipi
Hermes Agenthermes

Check it worked

Ask your agent:

text
Call the wyrd.guide tool with topic "start" and summarize what it says.

The agent calls wyrd.guide and describes the Declare → Observe → Verify workflow. Read tools work at once; write tools need a credential with the matching role. MCP tools lists every tool and its permission.

Advanced

Connect to a deployed server

Sign in to the server, then name it when you install:

bash
wyrd auth login --server https://wyrd.example.com --tenant acme
wyrd mcp install --host claude-code --server https://wyrd.example.com

The URL is stored in that agent’s entry only. Remote servers must use https://.

If it fails

You seeFix
WYRD_CLI_400_MCP_HOST_SELECTION, detected: noneInstall and open the agent once, then rerun
<host>: conflict: … has a wyrd entry that does not run wyrd mcp proxyRename or remove the other wyrd entry, then rerun
The agent log has WYRD_CLI_401_NO_CREDENTIALSRun wyrd init, or wyrd auth login for a deployed server
The agent log has WYRD_CLIENT_503_TRANSPORT_DOWNStart the server, then restart the agent

Next

Run your first verification, then ask your agent to explain its verdicts. What can I build? helps it choose the workflow your project needs.

Last updated