[
  {
    "side": "head",
    "args": [
      "-p",
      "--input-format",
      "stream-json",
      "--output-format",
      "stream-json",
      "--verbose",
      "--json-schema",
      "{\"type\":\"object\",\"properties\":{\"title\":{\"type\":\"string\"},\"needsRefinement\":{\"type\":\"boolean\"}},\"required\":[\"title\",\"needsRefinement\"],\"additionalProperties\":false}",
      "--model",
      "claude-haiku-5-5",
      "--effort",
      "medium",
      "--settings",
      "{\"disableAllHooks\":true}",
      "--tools",
      "",
      "--disable-slash-commands",
      "--no-session-persistence",
      "--strict-mcp-config",
      "--permission-mode",
      "dontAsk"
    ],
    "prompt": "Generate a title that will help the user recognize this T3 Code thread weeks later.\nReturn JSON with keys title and needsRefinement.\nSet needsRefinement to true only if the subject is still unknown, such as an unresolved link, \"fix this\", or an unexplained attachment. Otherwise set it to false.\n\nBefore answering, silently reduce the request to:\n- Subject: What system, feature, or problem is this really about?\n- Outcome: What does the user ultimately want to understand or change?\n- Incidental instructions: What only describes how the agent should do the work?\n\nTitle the subject and outcome. Discard incidental instructions.\n\nEditorial rules:\n- 3-8 words, fewer than 40 characters.\n- Use a compact noun phrase or clear action phrase.\n- Capture the umbrella goal when the request lists several symptoms or steps.\n- When asked about thread behavior, never include the referenced titles' topics. \"[Fix login] why didn't this thread start?\" means \"Thread Startup Failure\". Use linked topics only for requests about that work.\n- Name the product change, not the mock, plan, report, branch, or PR used to produce it.\n- Models, subagents, tools, output formats, and monitoring instructions do not belong in the title unless they are themselves the topic.\n- For reviews, name what is being reviewed and the relevant concern. Avoid generic titles such as \"Review PR 123\" when linked or attached context reveals the subject.\n- For research, name the question domain rather than the requested research process.\n- Do not claim the work is complete.\n- Do not copy and truncate the user's message.\n- Never include the project name (\"server\"); the UI already shows it next to the title. Avoid quotes, labels, filler, and trailing punctuation.\n- Use attached images as primary context for UI issues.\n- When a URL or attachment is the only source of the subject, use available tools to inspect it directly.\n- Local git history is not evidence of what a linked PR or issue is about. Never title the thread after branch names, commit messages, or merged commits found in the checkout.\n- If a linked PR or issue cannot be read, fall back to the user's stated action plus its number, such as \"Take Over PR 8588\". This is the one case where a PR or issue number belongs in the title.\n\nUser message:\nfix this\n\nAttachment metadata:\n- screen.png (image/png, 13065 bytes)",
    "images": [
      {
        "type": "image",
        "media_type": "image/png",
        "base64Length": 17420
      }
    ],
    "structured_output": {
      "title": "Fix Broken Login Button",
      "needsRefinement": false
    },
    "exitCode": 0
  },
  {
    "side": "base",
    "args": [
      "-p",
      "--output-format",
      "json",
      "--json-schema",
      "{\"type\":\"object\",\"properties\":{\"title\":{\"type\":\"string\"},\"needsRefinement\":{\"type\":\"boolean\"}},\"required\":[\"title\",\"needsRefinement\"],\"additionalProperties\":false}",
      "--model",
      "claude-haiku-5-5",
      "--effort",
      "medium",
      "--settings",
      "{\"disableAllHooks\":true}",
      "--tools",
      "",
      "--disable-slash-commands",
      "--no-session-persistence",
      "--strict-mcp-config",
      "--permission-mode",
      "dontAsk"
    ],
    "prompt": "Generate a title that will help the user recognize this T3 Code thread weeks later.\nReturn JSON with keys title and needsRefinement.\nSet needsRefinement to true only if the subject is still unknown, such as an unresolved link, \"fix this\", or an unexplained attachment. Otherwise set it to false.\n\nBefore answering, silently reduce the request to:\n- Subject: What system, feature, or problem is this really about?\n- Outcome: What does the user ultimately want to understand or change?\n- Incidental instructions: What only describes how the agent should do the work?\n\nTitle the subject and outcome. Discard incidental instructions.\n\nEditorial rules:\n- 3-8 words, fewer than 40 characters.\n- Use a compact noun phrase or clear action phrase.\n- Capture the umbrella goal when the request lists several symptoms or steps.\n- When asked about thread behavior, never include the referenced titles' topics. \"[Fix login] why didn't this thread start?\" means \"Thread Startup Failure\". Use linked topics only for requests about that work.\n- Name the product change, not the mock, plan, report, branch, or PR used to produce it.\n- Models, subagents, tools, output formats, and monitoring instructions do not belong in the title unless they are themselves the topic.\n- For reviews, name what is being reviewed and the relevant concern. Avoid generic titles such as \"Review PR 123\" when linked or attached context reveals the subject.\n- For research, name the question domain rather than the requested research process.\n- Do not claim the work is complete.\n- Do not copy and truncate the user's message.\n- Never include the project name (\"server\"); the UI already shows it next to the title. Avoid quotes, labels, filler, and trailing punctuation.\n- Use attached images as primary context for UI issues.\n- When a URL or attachment is the only source of the subject, use available tools to inspect it directly.\n- Local git history is not evidence of what a linked PR or issue is about. Never title the thread after branch names, commit messages, or merged commits found in the checkout.\n- If a linked PR or issue cannot be read, fall back to the user's stated action plus its number, such as \"Take Over PR 8588\". This is the one case where a PR or issue number belongs in the title.\n\nUser message:\nfix this\n\nAttachment metadata:\n- screen.png (image/png, 13065 bytes)",
    "images": [],
    "structured_output": {
      "title": "Unclear Screenshot Fix Request",
      "needsRefinement": true
    },
    "exitCode": 0
  },
  {
    "side": "head",
    "args": [
      "-p",
      "--input-format",
      "stream-json",
      "--output-format",
      "stream-json",
      "--verbose",
      "--json-schema",
      "{\"type\":\"object\",\"properties\":{\"title\":{\"type\":\"string\"},\"needsRefinement\":{\"type\":\"boolean\"}},\"required\":[\"title\",\"needsRefinement\"],\"additionalProperties\":false}",
      "--model",
      "claude-haiku-5-5",
      "--effort",
      "medium",
      "--settings",
      "{\"disableAllHooks\":true}",
      "--tools",
      "",
      "--disable-slash-commands",
      "--no-session-persistence",
      "--strict-mcp-config",
      "--permission-mode",
      "dontAsk"
    ],
    "prompt": "Generate a title that will help the user recognize this T3 Code thread weeks later.\nReturn JSON with keys title and needsRefinement.\nSet needsRefinement to true only if the subject is still unknown, such as an unresolved link, \"fix this\", or an unexplained attachment. Otherwise set it to false.\n\nBefore answering, silently reduce the request to:\n- Subject: What system, feature, or problem is this really about?\n- Outcome: What does the user ultimately want to understand or change?\n- Incidental instructions: What only describes how the agent should do the work?\n\nTitle the subject and outcome. Discard incidental instructions.\n\nEditorial rules:\n- 3-8 words, fewer than 40 characters.\n- Use a compact noun phrase or clear action phrase.\n- Capture the umbrella goal when the request lists several symptoms or steps.\n- When asked about thread behavior, never include the referenced titles' topics. \"[Fix login] why didn't this thread start?\" means \"Thread Startup Failure\". Use linked topics only for requests about that work.\n- Name the product change, not the mock, plan, report, branch, or PR used to produce it.\n- Models, subagents, tools, output formats, and monitoring instructions do not belong in the title unless they are themselves the topic.\n- For reviews, name what is being reviewed and the relevant concern. Avoid generic titles such as \"Review PR 123\" when linked or attached context reveals the subject.\n- For research, name the question domain rather than the requested research process.\n- Do not claim the work is complete.\n- Do not copy and truncate the user's message.\n- Never include the project name (\"server\"); the UI already shows it next to the title. Avoid quotes, labels, filler, and trailing punctuation.\n- Use attached images as primary context for UI issues.\n- When a URL or attachment is the only source of the subject, use available tools to inspect it directly.\n- Local git history is not evidence of what a linked PR or issue is about. Never title the thread after branch names, commit messages, or merged commits found in the checkout.\n- If a linked PR or issue cannot be read, fall back to the user's stated action plus its number, such as \"Take Over PR 8588\". This is the one case where a PR or issue number belongs in the title.\n\nUser message:\nfix this\n\nAttachment metadata:\n- screen.png (image/png, 13065 bytes)",
    "images": [
      {
        "type": "image",
        "media_type": "image/png",
        "base64Length": 17420
      }
    ],
    "structured_output": {
      "title": "Fix Broken Login Button",
      "needsRefinement": false
    },
    "exitCode": 0
  },
  {
    "side": "base",
    "args": [
      "-p",
      "--output-format",
      "json",
      "--json-schema",
      "{\"type\":\"object\",\"properties\":{\"title\":{\"type\":\"string\"},\"needsRefinement\":{\"type\":\"boolean\"}},\"required\":[\"title\",\"needsRefinement\"],\"additionalProperties\":false}",
      "--model",
      "claude-haiku-5-5",
      "--effort",
      "medium",
      "--settings",
      "{\"disableAllHooks\":true}",
      "--tools",
      "",
      "--disable-slash-commands",
      "--no-session-persistence",
      "--strict-mcp-config",
      "--permission-mode",
      "dontAsk"
    ],
    "prompt": "Generate a title that will help the user recognize this T3 Code thread weeks later.\nReturn JSON with keys title and needsRefinement.\nSet needsRefinement to true only if the subject is still unknown, such as an unresolved link, \"fix this\", or an unexplained attachment. Otherwise set it to false.\n\nBefore answering, silently reduce the request to:\n- Subject: What system, feature, or problem is this really about?\n- Outcome: What does the user ultimately want to understand or change?\n- Incidental instructions: What only describes how the agent should do the work?\n\nTitle the subject and outcome. Discard incidental instructions.\n\nEditorial rules:\n- 3-8 words, fewer than 40 characters.\n- Use a compact noun phrase or clear action phrase.\n- Capture the umbrella goal when the request lists several symptoms or steps.\n- When asked about thread behavior, never include the referenced titles' topics. \"[Fix login] why didn't this thread start?\" means \"Thread Startup Failure\". Use linked topics only for requests about that work.\n- Name the product change, not the mock, plan, report, branch, or PR used to produce it.\n- Models, subagents, tools, output formats, and monitoring instructions do not belong in the title unless they are themselves the topic.\n- For reviews, name what is being reviewed and the relevant concern. Avoid generic titles such as \"Review PR 123\" when linked or attached context reveals the subject.\n- For research, name the question domain rather than the requested research process.\n- Do not claim the work is complete.\n- Do not copy and truncate the user's message.\n- Never include the project name (\"server\"); the UI already shows it next to the title. Avoid quotes, labels, filler, and trailing punctuation.\n- Use attached images as primary context for UI issues.\n- When a URL or attachment is the only source of the subject, use available tools to inspect it directly.\n- Local git history is not evidence of what a linked PR or issue is about. Never title the thread after branch names, commit messages, or merged commits found in the checkout.\n- If a linked PR or issue cannot be read, fall back to the user's stated action plus its number, such as \"Take Over PR 8588\". This is the one case where a PR or issue number belongs in the title.\n\nUser message:\nfix this\n\nAttachment metadata:\n- screen.png (image/png, 13065 bytes)",
    "images": [],
    "structured_output": {
      "title": "UI Fix Request From Screenshot",
      "needsRefinement": true
    },
    "exitCode": 0
  }
]