{
  "checker": {
    "details": {
      "checks": [
        {
          "check": "install",
          "details": {
            "argv": [
              "<host-path>",
              "--version"
            ],
            "kind": "cli",
            "needs_browser": false,
            "needs_credentials": false,
            "returncode": 0,
            "scope": "partial: install",
            "stderr": "",
            "stdout": "auten 1.0",
            "working": false
          },
          "optional": false,
          "status": "PASS"
        },
        {
          "check": "credentials_error",
          "details": {
            "argv": [
              "<host-path>",
              "mcp-bridge"
            ],
            "blocker": "MCP response missing for request 1: argv did not answer as a stdio MCP server (a client CLI that talks to servers is kind cli); stderr: auten: no key on this device \u2014 run `auten login` in a terminal first\n",
            "kind": "mcp",
            "working": false
          },
          "optional": false,
          "status": "FAIL"
        }
      ],
      "scope": "partial checks",
      "working": false
    },
    "status": "FAIL"
  },
  "deviations": [
    "Node/npm not installed in guest; the npx launcher (bin/auten-mcp.js) was not used. Used the native 'auten mcp-bridge' entry from README Client setup instead.",
    "'auten status' without a key entered the interactive first-run menu and cancelled on stdin EOF; used 'auten --version' for the install check instead.",
    "Install script was downloaded to /tmp and run with AUTEN_NO_LAUNCH=1 rather than piped directly, to read exit status."
  ],
  "main_blocker": "No Auten key on this device; mcp-bridge refuses to start. Also no X11 display (DISPLAY unset).",
  "operation": "Installed the Auten runner via README 'curl -fsSL https://auten.ai/install | bash' (with AUTEN_NO_LAUNCH=1 per llms-install.md) and ran 'auten --version' (auten 1.0). Attempted MCP start via 'auten mcp-bridge' (stdio) for initialize + tools/list.",
  "operation_scope": "Install passed. MCP start/tools-list not reached: mcp-bridge exits 1 with 'no key on this device \u2014 run `auten login` in a terminal first'. Needs a user-issued Auten key (auten login, free plan, browser sign-in). Not obtained; no credentials were sought. Also no X11 DISPLAY in the VM (README: headless needs a display), so GUI tools would not work even with a key.",
  "outcome": "blocked",
  "steps": [
    "sudo apt-get update",
    "sudo apt-get install -y python3-venv python3-pyatspi python3-gi xdotool wmctrl scrot xclip libglib2.0-bin tesseract-ocr libsecret-tools",
    "curl -fsSL https://auten.ai/install -o /tmp/auten-install.sh && AUTEN_NO_LAUNCH=1 bash /tmp/auten-install.sh (Installed; binary at ~/.local/bin/auten)",
    "auten --version -> auten 1.0",
    "auten mcp-bridge (stdio initialize/tools/list) -> exit 1, no key on this device"
  ],
  "stuck_step": "README Quick start step 2 / llms-install.md Step 2: 'auten login' (user must connect a key)",
  "suggested_fix": "A user with an Auten account runs 'auten login' in a terminal on the guest (or supplies a key via the documented mechanism), and an X11 display (e.g. Xvfb plus DISPLAY) is provided. Then rerun: printf initialize/tools/list JSON-RPC lines into '<host-path> mcp-bridge'."
}