# Connect Ramble to this coding agent You are a coding agent, and the user asked you to follow this file. Before you change anything, tell the user exactly which files you will write and which commands you will run, and wait for a yes. Do not start until they say yes. Ramble (https://ramble.sh) records a person talking through what is wrong with an app and turns it into findings: their own words, a timestamp and a screenshot. This file connects you to it with two things: an MCP server named ramble at https://ramble.sh/mcp, and a skill named ramble (the /ramble command). If the user gave you this file from another address, a self-hosted Ramble, use that address instead of https://ramble.sh everywhere below: the MCP URL and the skill URL alike. If you run that address's install.sh, run it with RAMBLE_INSTALL_BASE set to the same address, or it will wire everything to the default address, https://ramble.sh, instead. The user never pastes a token, key or password. Do not ask them for one, and do not look for one. The installer gets its own agent token through one click in the user's browser: it can read their rambles, add notes and statuses, and ask them to record, and nothing else. It lasts a year and the user can revoke it any time under Connected agents at https://ramble.sh/mine. The installer writes it into each agent's own config and never prints it. You will not see it, and you must not look for it in those files. ## What this will change 1. Run the Ramble installer. It finds the coding agents on this machine, and for each one adds the MCP server ramble with the token from the click. Cursor's file ~/.cursor/mcp.json and Codex's ~/.codex/config.toml are edited directly and end up readable only by the user. 2. Write one file, the skill, to each agent's skills folder and to ~/.agents/skills/ramble/SKILL.md. The only thing the installer downloads besides itself is https://ramble.sh/skills/ramble/SKILL.md. 3. Tell the user what is left, if anything. Nothing else is installed or changed. Show this list to the user now, with the exact paths for the agent you are, and wait for the yes. ## 1. Download the installer and show the plan Download it to a temporary file, outside the user's project, and read it. It is short, plain text, and runs nothing until you run it: curl -fsSL https://ramble.sh/install.sh -o "${TMPDIR:-/tmp}/ramble-install.sh" Run it with --dry-run. That prints every path it would write and every command it would run, writes nothing and contacts nothing: sh "${TMPDIR:-/tmp}/ramble-install.sh" --dry-run Show the user that output as the plan, and wait for their yes. ## 2. Run it sh "${TMPDIR:-/tmp}/ramble-install.sh" Tell the user before you start: a browser tab is about to open, it shows a short code, and they should check that the same code is printed in the output and then click Connect. The installer waits up to ten minutes for the click. If your shell tool only shows output when a command ends, run the command in the background or with a timeout of at least eleven minutes, and read the code from its output as soon as it appears and show it to the user. If there is no browser on this machine, or the user is connected over ssh, add --no-browser. The installer then prints a link for the user to open on any device where they are signed in to Ramble. When it finishes, tell the user which agents it set up, from its output. A step that says "done" is set up and signed in. If a step says it failed or was skipped, say so and give the user the line it printed. ## 3. Tell the user what is left - Type /ramble in the agent. - Start a new session in the agent, so it loads the new server: you ran this inside an agent that was already open. If /ramble cannot see Ramble in the new session, run /mcp and check that ramble is listed. - VS Code with Copilot is added by address only: the user opens the MCP list in VS Code, starts ramble and signs in when it asks. - Rambles recorded before signing in belong to the browser they were recorded in. Signing in on ramble.sh in that same browser moves them into the account. Rambles recorded before Ramble tracked browsers cannot be moved. Do not run /ramble yourself until the user says they are ready. ## If you cannot run the installer If the installer cannot run here (no shell, no curl, or a machine where it fails), add the server by address with your own command and let the user sign in from inside the agent. Run only the block for your agent. Claude Code: claude mcp add --transport http --scope user ramble https://ramble.sh/mcp Cursor: add this to ~/.cursor/mcp.json, keeping every server already there. Create the file if it is missing. If the file does not parse, do not touch it; show the user the snippet instead. {"mcpServers": {"ramble": {"url": "https://ramble.sh/mcp"}}} VS Code with Copilot: code --add-mcp '{"name":"ramble","type":"http","url":"https://ramble.sh/mcp"}' Codex: codex mcp add ramble --url https://ramble.sh/mcp Gemini CLI: gemini mcp add --transport http -s user ramble https://ramble.sh/mcp Zed: do not edit the user's settings file, it may contain comments. Show the user this snippet to put under context_servers in their Zed settings: {"ramble": {"url": "https://ramble.sh/mcp"}} Cline, and any agent that cannot sign in through a browser: this route needs a personal token. The user signs in at https://ramble.sh/mine, opens Connected agents, makes a New agent token, and runs the add command from that page in their own terminal. The token must never pass through this chat. Claude.ai and Claude Desktop: the user opens Settings, then Connectors, then Add custom connector, and enters https://ramble.sh/mcp. That gives tools only, not the /ramble command. Any other agent: add a remote MCP server named ramble, transport streamable HTTP, URL https://ramble.sh/mcp, using your own mechanism. If the command says ramble already exists, say so and go on. Do not remove or replace it. Then write the skill. Skills folder for your agent: - Claude Code: ~/.claude/skills/ramble/SKILL.md - Cursor: ~/.cursor/skills/ramble/SKILL.md - VS Code with Copilot: ~/.copilot/skills/ramble/SKILL.md - Gemini CLI: ~/.gemini/skills/ramble/SKILL.md - Codex and every other agent: ~/.agents/skills/ramble/SKILL.md Also write ~/.agents/skills/ramble/SKILL.md, which most agents read. Download the file once with curl, or with your own fetch tool, and write the same bytes to each place: mkdir -p ~/.claude/skills/ramble curl -fsSL https://ramble.sh/skills/ramble/SKILL.md -o ~/.claude/skills/ramble/SKILL.md Use the folder for your agent in that command, then copy the file to ~/.agents/skills/ramble/. Read the first lines of what you wrote and check that it starts with a line of three dashes and has the line name: ramble. If a SKILL.md already exists there, tell the user and ask before replacing it. Then tell the user the connection is added but not signed in yet, and give the step for your agent: - Claude Code: run /mcp, choose ramble, choose Authenticate, finish in the browser. This one step cannot be done for them. - Codex: run codex mcp login ramble. - Gemini CLI: run /mcp auth ramble inside Gemini CLI. - Cursor and VS Code: open the MCP settings, find ramble, and choose to sign in or connect. Do not run /ramble yourself until the user says they have signed in.