Open a robot in VS Code, Cursor, Claude Code or Codex

Work on a saved robot with your own editor or coding assistant. You need Git and Node 24. In the workbench, choose Open in, pick your tool and paste the command into a terminal:

npx @clunkyard/cli open ROBOT_ID --in code     # or cursor, claude, codex

The command:

  1. Signs you in through your browser the first time. Approve the sign-in and this computer gets its own agent key, saved in your user configuration directory and named Git: and the computer's name in Account → Access keys. No key passes through a URL or your shell history.
  2. Clones the robot, https://clunkyard.com/git/ROBOT_ID.git, into a folder named after its project, with Git reading the key from the CLI's credential store for that server only (Git). It reuses a clone already there, says if it is behind, and moves a clone made with the old @clunkyard/git helper to the new address, history and all.
  3. Adds local settings, which Git ignores through .git/info/exclude, so a push sends only your robot:
    • AGENTS.md, and CLAUDE.md importing it: the language reference, the rules sheet and the local commands, for any assistant.
    • .mcp.json (Claude Code and VS Code), .cursor/mcp.json and .codex/config.toml: the Clunkyard MCP server, for hosted practice matches, match events and build results. Each tool asks once before using a project's server: Claude Code to approve it, Codex to trust the folder. The first call opens a Clunkyard sign-in page.
    • .vscode/tasks.json: build, local match, and push then wait for the hosted build. A file the robot already has is left as it is. The build cache (.clunkyard/) and local replays are kept out of Git too.
  4. Opens the folder in VS Code or Cursor, or starts Claude Code or Codex in it, in the same terminal.

Signing in again on the same computer replaces its key.

Leave out --in to only clone and set up. Add a folder name after the robot ID to clone somewhere else. On a computer you reach over SSH, without a local browser, sign in first with npx @clunkyard/cli login --token-stdin and an agent key from your Account page.

The loop

npx @clunkyard/cli build
npx @clunkyard/cli match 42 2d classic
git commit -am "Lead the target"
git push origin main
npx @clunkyard/cli hosted-build ROBOT_ID

A local match uses the same engine as hosted matches. A push is a commit: it saves a revision and starts its hosted build. hosted-build waits for that build and prints its diagnostics, using the key the sign-in saved; the workbench and My bots show it too. If the push is refused because the robot changed elsewhere, run git pull --no-rebase origin main, build and test again, and push. More in Private Git and Develop locally.

Connect only the assistant

To use the MCP server without a clone, add https://clunkyard.com/mcp to your tool. The first call opens a Clunkyard sign-in page in your browser.

Tool Add the Clunkyard MCP server
Claude Code claude mcp add --transport http clunkyard https://clunkyard.com/mcp, then /mcp to sign in
Claude on the web or desktop Customize → Connectors → Add custom connector, with the URL above
Codex codex mcp add clunkyard --url https://clunkyard.com/mcp, then codex mcp login clunkyard
VS Code The workbench's Add to VS Code link, or code --add-mcp '{"name":"clunkyard","type":"http","url":"https://clunkyard.com/mcp"}'
Cursor The workbench's Add to Cursor link, or the .cursor/mcp.json entry above

Connect an assistant (MCP) lists the tools and permissions.

Download this page as Markdown