Agent Hosts

Agent Hosts

A "host" is an app that runs an AI agent and talks to MCP servers: Claude Code, Cursor, Codex and so on. logos setup detects them and, after asking you, connects each one to your vault.

What each host gets

Tier	Hosts	What you get
Plugin	Claude Code	The server, the skills, and hooks that restore context and record activity without being asked
MCP + session hooks	Cursor, Codex	The server, plus a session-start hook that opens each new session with your last checkpoint
MCP only	Everyone else	The tools, used when the model chooses to call them. Say "resume this project"

The Cursor and Codex hooks are merged into ~/.cursor/hooks.json and ~/.codex/hooks.json, with a .logos-backup beside each. Codex won't run a hook you haven't approved: approve it in Codex's /hooks.

Supported and wired hosts

Host	Wired by setup	How	Verified
Claude Code	yes	plugin, plus claude mcp add --scope user	✅
Codex	yes	codex mcp add	✅
Cursor	yes	merges ~/.cursor/mcp.json	✅
Claude Desktop	yes	merges claude_desktop_config.json	✅
Cline (VS Code, Cursor, Windsurf)	yes	merges the extension's cline_mcp_settings.json	help wanted
Cline CLI	yes	merges ~/.cline/data/settings/cline_mcp_settings.json	help wanted
Devin for Terminal	yes	merges ~/.config/devin/mcp_config.json	help wanted
GitHub Copilot CLI	yes	merges ~/.copilot/mcp-config.json (or $COPILOT_HOME)	help wanted
GitHub Copilot in VS Code	yes	merges VS Code's user mcp.json	help wanted
opencode	yes	merges ~/.config/opencode/opencode.json(c)	help wanted
Amp	yes (macOS, Linux)	merges ~/.config/amp/settings.json	help wanted
Grok Build	yes	writes [mcp_servers.logos] in ~/.grok/config.toml	help wanted
Windsurf, Roo Code, Zed, Gemini CLI, JetBrains AI, Continue.dev	not yet	manual config below	help wanted
Aider	—	Aider has no MCP client	—

"Verified" means logos doctor --integration passes: the host launches the server, completes the handshake, writes a checkpoint, reads it back through resume, and the markdown lands in the configured vault. If you run it against a "help wanted" host and it passes, please open an issue or PR with the output.

Wiring a host by hand

logos setup --print-config prints the block for your machine. In general:

{
  "mcpServers": {
    "logos": {
      "command": "/absolute/path/to/logos",
      "args": ["mcp", "serve"],
      "env": { "LOGOS_VAULT": "/absolute/path/to/vault" }
    }
  }
}

Both paths must be absolute. A host starts the server from whatever directory it likes, so a relative LOGOS_VAULT points somewhere you will never look. Logos would seem to work while knowing nothing.

For TOML-configured hosts, use logos setup --print-config --format toml. For a config file in an unusual location, logos setup --config <path> merges it in for you.

Portable config with npx

{
  "mcpServers": {
    "logos": { "command": "npx", "args": ["-y", "@noeton/logos", "mcp", "serve"] }
  }
}

This needs no install and works on any machine, but npm checks the registry on every start. On native Windows, use "command": "cmd" with "args": ["/c", "npx", "-y", "@noeton/logos", "mcp", "serve"].

One-click

• Add to Cursor
• Add to VS Code

Seeing it work

Every write returns a receipt (✓ Logos · checkpoint saved to logos) and the agent is asked to repeat it. To look for yourself:

Host	Show the tool calls
Claude Code	Ctrl+O toggles full tool output; /mcp lists servers and their health
Claude Desktop	Click the tool call's disclosure triangle
Cursor	Tool calls expand in the chat pane

logos doctor answers the same question from outside the agent, with counts.

Adding support for a new host

A host is four fields in internal/setup/hosts.go: Name, Detect, Where and Register. mergeJSON already handles the risky parts: it refuses a malformed file rather than overwriting it, writes a backup, keeps other servers, and writes atomically. If the host has its own registration command, use viaCLI. Then run logos doctor --integration and open a PR with the output.