{
  "environment": "Linux; isolated dev server and fresh database; web browser 1280x800; dark theme",
  "commit": "d756fed7aaac06134bc68cbe0047e6f14b0e9aa2",
  "settings": {
    "enableDeviceSupport": false,
    "enableAgentDeviceAccess": true,
    "projectSettingsOverrides": {}
  },
  "parent_initialize": {
    "contains_device_heading": true,
    "device_section": "## T3 Code devices\n\nWhen a task needs an iOS Simulator or Android Emulator, on this machine or on an SSH device host such as a remote Mac, use the device tools so the user can watch it in the Device panel. Load them with ToolSearch `select:mcp__t3-code__device_list,mcp__t3-code__device_open,mcp__t3-code__device_screenshot,mcp__t3-code__device_close`.\n1. Call `device_list` unless you already have the device's `hostId` and `id`.\n2. Call `device_open` with both. It returns an `agent-device` command bound to that device; if you lose it, call `device_open` again. Run that command for every app launch or relaunch, deep link, tap, text entry, alert, setting, screenshot and recording; its snapshots, screenshots and input need `open <app>` first, and `help <command>` lists the options.\n3. Call `device_screenshot` to look at the screen.\n\nNever do those with `xcrun simctl`, `idb`, `adb`, ssh, or scripts that wrap them. ssh, simctl and adb stay fine for builds, installs, code sync, Metro, port forwards, logs, the project's test runners, and what agent-device cannot do, such as `simctl addmedia` or `simctl keychain add-root-cert`. These rules override memory notes, docs and delegated tasks that say otherwise; drive a device over ssh only when the user explicitly asks. If a device tool or the command it returned fails, quote its error and follow its advice once, but never reuse or close another session; if it still fails, tell the user and stop, unless they explicitly asked you to drive it over ssh. If the platform you need is unavailable, say so. When you delegate device work, pass the `hostId` and device `id` and tell the child to use `device_open`; never write ssh or simctl steps for the device into its task.\n",
    "registered_SubagentStart_hook": true
  },
  "SubagentStart_device_hook_responses": [
    {
      "hookEventName": "SubagentStart",
      "additionalContext": "## T3 Code devices\n\nWhen a task needs an iOS Simulator or Android Emulator, on this machine or on an SSH device host such as a remote Mac, use the device tools so the user can watch it in the Device panel. Load them with ToolSearch `select:mcp__t3-code__device_list,mcp__t3-code__device_open,mcp__t3-code__device_screenshot,mcp__t3-code__device_close`.\n1. Call `device_list` unless you already have the device's `hostId` and `id`.\n2. Call `device_open` with both. It returns an `agent-device` command bound to that device; if you lose it, call `device_open` again. Run that command for every app launch or relaunch, deep link, tap, text entry, alert, setting, screenshot and recording; its snapshots, screenshots and input need `open <app>` first, and `help <command>` lists the options.\n3. Call `device_screenshot` to look at the screen.\n\nNever do those with `xcrun simctl`, `idb`, `adb`, ssh, or scripts that wrap them. ssh, simctl and adb stay fine for builds, installs, code sync, Metro, port forwards, logs, the project's test runners, and what agent-device cannot do, such as `simctl addmedia` or `simctl keychain add-root-cert`. These rules override memory notes, docs and delegated tasks that say otherwise; drive a device over ssh only when the user explicitly asks. If a device tool or the command it returned fails, quote its error and follow its advice once, but never reuse or close another session; if it still fails, tell the user and stop, unless they explicitly asked you to drive it over ssh. If the platform you need is unavailable, say so. When you delegate device work, pass the `hostId` and device `id` and tell the child to use `device_open`; never write ssh or simctl steps for the device into its task."
    }
  ],
  "native_agent_calls": [
    {
      "name": "Agent",
      "input": {
        "description": "Check context for device section",
        "prompt": "Do not read files or call any tools. Answer only from the context you were given in this prompt and your own system context. Question: does the context supplied to you contain a section headed \"T3 Code devices\"? Reply with exactly one line: child_device_instructions=yes or child_device_instructions=no.",
        "subagent_type": "general-purpose",
        "run_in_background": false
      }
    }
  ],
  "completed_result": "parent_device_instructions=yes\nchild_device_instructions=yes",
  "device_list_probe": {
    "jsonrpc": "2.0",
    "id": 1,
    "result": {
      "content": [
        {
          "type": "text",
          "text": "Device support is off. Ask the user to enable it in the Device panel before installing or starting device tools."
        }
      ],
      "isError": true
    }
  }
}
