Skip to main content

​
Runner

The Autodock runner catches the hardest server-side bugs in realtime. It listens to many different signals coming in and out of a server, including HTTP traffic, Docker logs, and database connections, and makes them available to coding agents. It is available as an MCP server that starts automatically on all Autodock dev boxes.
Mike’s tip: I had the idea to develop this runner when working at Veeton on gnarly bugs that mixed together Clerk, Orb, Stripe, Postgres, and several Docker containers running simultaneously. There was no way to get proper timestamped logs for all of these services into my agent for rapid iteration, and I spent tons of time piping to logfiles. The runner fixes that.

​
Commands Available Inside Your Environment

Once you’re SSH’d into your Autodock environment, these commands are available:
CommandDescription
autodock mcp [provider]Get MCP connection instructions (claude-code, vscode, cursor, cline)
autodock ide [editor]Get IDE connection instructions (vscode, cursor, jetbrains)
autodock port exposeExpose a port from inside the environment
autodock port listList exposed ports
autodock port unexposeRemove an exposed port
autodock urlsShow environment URLs
autodock lifecycle byeDisconnect or terminate the environment
autodock versionShow version

​
Built-in MCP Server

Every Autodock environment runs an MCP server on port 8080 that gives AI tools direct access to:
  • File system operations
  • Command execution
  • HTTP traffic logs
  • Docker container logs
  • Database connection logs
Connect your AI tool to the runner MCP from inside the environment for real-time debugging.