Agent Autoconfig
Writes MCP configuration and instruction files so Claude Code, Gemini, Copilot and Cursor all point at the RobOS MCP router.
packages/agent-autoconfig
Agent Autoconfig keeps the config files of several coding agents pointing at one MCP server entry, robos, which runs robos-mcp-router/cli.js --stdio. It also writes an AGENTS.md for the project.
What it writes
The sync runs when the app starts and again when you click Sync All Agent Configurations. It overwrites these files:
| Agent | MCP config (under your home directory) | Instruction file (in ~/workspace) |
|---|---|---|
| Universal standard | none | AGENTS.md |
| Claude Code | .claude/settings.json |
CLAUDE.md |
| Gemini / Antigravity | .gemini/antigravity/mcp/robos.json |
GEMINI.md |
| GitHub Copilot CLI | .config/github-copilot/mcp.json |
COPILOT.md |
| Cursor / OpenAI Codex | .cursor/mcp.json |
CODEX.md |
Each MCP entry runs node /usr/local/share/robos/robos-mcp-router/cli.js --stdio with ROBOS_ENV=desktop and ROBOS_MCP_AUTO=true. That path is where the router is installed in a RobOS VM, so the generated config only works where the router exists at that path.
The sync replaces the whole contents of these files, including an existing .claude/settings.json. Back up any settings you want to keep before running the app.
What you do in it
- Select an agent in the Supported AI Coding Assistants & Standards list to preview its generated MCP JSON and its instruction file.
- Click Universal AGENTS.md to preview the universal file.
- Click Sync All Agent Configurations to rewrite everything.
Limits
The “Active Task Context” and “EKGraph Knowledge Context” sections of the generated AGENTS.md come from constants in autoconfig.js (task TASK-101, repo nddipiazza/robos, 142 architecture nodes). The app does not read your current task or knowledge graph yet. The :19151 figure in the header is a static label.
Source: packages/agent-autoconfig. npm test runs node --test there.
More in Agent Services & MCP Servers
Agent Daemon (agentd)
Keeps a registry of sub-agent sessions, each with its own home directory and environment, behind a Unix socket and a small window.
Agent Profile Daemon
Creates short-lived agent profiles with their own home directory (tmpfs when run as root) and runs commands with that home and environment.
Agent Session Library
Node.js client for the agentd socket, plus a small demo window and a simulated test-driven-development runner.
CI Monitor MCP Server
An MCP server that lets agents list Buildkite builds and read failed-job logs, backed by the connection set up in CI Monitor.
Dev Tools MCP Server
An MCP server with a small catalog of developer CLI tools; "install" and "check" read and write a JSON file and do not touch the system.
Engineering Knowledge Graph MCP Server
An MCP server that lets agents search and edit a small node store, query and propose changes to the SDLC graph, and look up schema types.
IDE Bridge MCP Server
An MCP server that forwards IDE commands (open file, breakpoints, run configurations, refactorings) to the RobOS IntelliJ plugin on port 63343.
MCP Router
Single MCP endpoint that lists the tools of the servers in the registry and routes tool calls to them, with built-in fallbacks.
MCP Server Framework
Node.js library for building small Model Context Protocol servers, with an HTTP and a stdio transport and a shared registry file.
RobOS CLI Tools
Four shell scripts for scripts and agents: send a notification, set the active task, append to the work journal, and emit or read events.
System MCP Server
MCP server with six tools for preferences, notifications, a tool inventory, file-name search and the active task, backed by a JSON file with sample data.
Task Manager MCP Server
MCP server with seven tools for listing, creating and advancing tasks stored in ~/.config/robos/tasks/tasks.json.
Workspace Manager MCP Server
MCP server with six workspace tools, backed by a JSON file of sample workspaces. Several tools return canned results and do not run anything.