radx-agent

Install RADX OS agent integration for any coding agent.

npx radx-agent init                 # detect agents, write adapters at project scope
npx radx-agent init --scope user    # home-level (~/.claude, ~/.codex/AGENTS.md)
npx radx-agent init --target agents # AGENTS.md only (Codex/Cursor/Amp/…)
npx radx-agent init --token <tok> --url https://<deployment>.convex.site
npx radx-agent init --no-mcp        # skip MCP registration, just print the config
npx radx-agent init --dry-run       # print planned writes, touch nothing

npx radx-agent@latest update        # refresh the installed adapters to the latest
                                    # published package — config (~/.config/radx/.env)
                                    # is left untouched. Same flags as init.
npx radx-agent version              # print the installed package version

Self-update. update re-writes the managed adapter files (SKILL.md / AGENTS.md block / .mcp.json) from the package's bundled dist/, idempotently and preserving any host content. Run via npx radx-agent@latest update, it pulls the newest published integration — the supported way for an agent to bring itself current. It never edits the canonical prose (that stays single-sourced in source/radx.md) and never touches your token.

The prose lives in exactly one place — source/radx.md. npm run build:agent regenerates the Claude plugin SKILL.md, the CLAUDE.md managed block, and the baked dist/ artifacts the installer ships. CI fails if dist/ is stale.

Targets:

• Claude — standalone SKILL.md at the chosen scope.
• AGENTS.md — an idempotent managed block (the open standard Codex/Cursor/Amp read).

The MCP server (mcp/radx-mcp.mjs, 13 tools) is the primary tool interface for agents, and the radx CLI is the capabilities documented here. init:

• writes ~/.config/radx/.env (refusing to overwrite a different existing token without --yes);
• registers the MCP server automatically — at project/repo scope it writes a portable .mcp.json (merged idempotently, preserving any other servers); at user scope it runs claude mcp add --scope user. Pass --no-mcp to skip this and just print the config to paste yourself.

The MCP server is bundled into the published package (dist/radx-mcp.mjs, with @modelcontextprotocol/sdk as a dependency), so the registered MCP serverPath resolves both in-repo and from an npx radx-agent install. The server reads RADX_URL (your deployment's .convex.site) + RADX_TOKEN from ~/.config/radx/.env, so no secrets live in the MCP config.