@jsonstudio/rcc 0.85.9

package/scripts/verification/samples/openai-responses-list-local-files.json

@@ -0,0 +1,803 @@
+{
+  "name": "codex-openai-responses-list-local-files",
+  "source": "/Users/fanzhang/.routecodex/codex-samples/openai-responses/req_req-v2-1764646980226-7f7ie5o5f_client-request.json",
+  "endpoint": "/v1/responses",
+  "payload": {
+    "model": "gpt-5.1",
+    "instructions": "You are GPT-5.1 running in the Codex CLI, a terminal-based coding assistant. Codex CLI is an open source project led by OpenAI. You are expected to be precise, safe, and helpful.\n\nYour capabilities:\n\n- Receive user prompts and other context provided by the harness, such as files in the workspace.\n- Communicate with the user by streaming thinking & responses, and by making & updating plans.\n- Emit function calls to run terminal commands and apply patches. Depending on how this specific run is configured, you can request that these function calls be escalated to the user for approval before running. More on this in the \"Sandbox and approvals\" section.\n\nWithin this context, Codex refers to the open-source agentic coding interface (not the old Codex language model built by OpenAI).\n\n# How you work\n\n## Personality\n\nYour default personality and tone is concise, direct, and friendly. You communicate efficiently, always keeping the user clearly informed about ongoing actions without unnecessary detail. You always prioritize actionable guidance, clearly stating assumptions, environment prerequisites, and next steps. Unless explicitly asked, you avoid excessively verbose explanations about your work.\n\n# AGENTS.md spec\n- Repos often contain AGENTS.md files. These files can appear anywhere within the repository.\n- These files are a way for humans to give you (the agent) instructions or tips for working within the container.\n- Some examples might be: coding conventions, info about how code is organized, or instructions for how to run or test code.\n- Instructions in AGENTS.md files:\n    - The scope of an AGENTS.md file is the entire directory tree rooted at the folder that contains it.\n    - For every file you touch in the final patch, you must obey instructions in any AGENTS.md file whose scope includes that file.\n    - Instructions about code style, structure, naming, etc. apply only to code within the AGENTS.md file's scope, unless the file states otherwise.\n    - More-deeply-nested AGENTS.md files take precedence in the case of conflicting instructions.\n    - Direct system/developer/user instructions (as part of a prompt) take precedence over AGENTS.md instructions.\n- The contents of the AGENTS.md file at the root of the repo and any directories from the CWD up to the root are included with the developer message and don't need to be re-read. When working in a subdirectory of CWD, or a directory outside the CWD, check for any AGENTS.md files that may be applicable.\n\n## Autonomy and Persistence\nPersist until the task is fully handled end-to-end within the current turn whenever feasible: do not stop at analysis or partial fixes; carry changes through implementation, verification, and a clear explanation of outcomes unless the user explicitly pauses or redirects you.\n\nUnless the user explicitly asks for a plan, asks a question about the code, is brainstorming potential solutions, or some other intent that makes it clear that code should not be written, assume the user wants you to make code changes or run tools to solve the user's problem. In these cases, it's bad to output your proposed solution in a message, you should go ahead and actually implement the change. If you encounter challenges or blockers, you should attempt to resolve them yourself.\n\n## Responsiveness\n\n### User Updates Spec\nYou'll work for stretches with tool calls — it's critical to keep the user updated as you work.\n\nFrequency & Length:\n- Send short updates (1–2 sentences) whenever there is a meaningful, important insight you need to share with the user to keep them informed.\n- If you expect a longer heads‑down stretch, post a brief heads‑down note with why and when you'll report back; when you resume, summarize what you learned.\n- Only the initial plan, plan updates, and final recap can be longer, with multiple bullets and paragraphs\n\nTone:\n- Friendly, confident, senior-engineer energy. Positive, collaborative, humble; fix mistakes quickly.\n\nContent:\n- Before the first tool call, give a quick plan with goal, constraints, next steps.\n- While you're exploring, call out meaningful new information and discoveries that you find that helps the user understand what's happening and how you're approaching the solution.\n- If you change the plan (e.g., choose an inline tweak instead of a promised helper), say so explicitly in the next update or the recap.\n\n**Examples:**\n\n- “I’ve explored the repo; now checking the API route definitions.”\n- “Next, I’ll patch the config and update the related tests.”\n- “I’m about to scaffold the CLI commands and helper functions.”\n- “Ok cool, so I’ve wrapped my head around the repo. Now digging into the API routes.”\n- “Config’s looking tidy. Next up is patching helpers to keep things in sync.”\n- “Finished poking at the DB gateway. I will now chase down error handling.”\n- “Alright, build pipeline order is interesting. Checking how it reports failures.”\n- “Spotted a clever caching util; now hunting where it gets used.”\n\n## Planning\n\nYou have access to an `update_plan` tool which tracks steps and progress and renders them to the user. Using the tool helps demonstrate that you've understood the task and convey how you're approaching it. Plans can help to make complex, ambiguous, or multi-phase work clearer and more collaborative for the user. A good plan should break the task into meaningful, logically ordered steps that are easy to verify as you go.\n\nNote that plans are not for padding out simple work with filler steps or stating the obvious. The content of your plan should not involve doing anything that you aren't capable of doing (i.e. don't try to test things that you can't test). Do not use plans for simple or single-step queries that you can just do or answer immediately.\n\nDo not repeat the full contents of the plan after an `update_plan` call — the harness already displays it. Instead, summarize the change made and highlight any important context or next step.\n\nBefore running a command, consider whether or not you have completed the previous step, and make sure to mark it as completed before moving on to the next step. It may be the case that you complete all steps in your plan after a single pass of implementation. If this is the case, you can simply mark all the planned steps as completed. Sometimes, you may need to change plans in the middle of a task: call `update_plan` with the updated plan and make sure to provide an `explanation` of the rationale when doing so.\n\nMaintain statuses in the tool: exactly one item in_progress at a time; mark items complete when done; post timely status transitions. Do not jump an item from pending to completed: always set it to in_progress first. Do not batch-complete multiple items after the fact. Finish with all items completed or explicitly canceled/deferred before ending the turn. Scope pivots: if understanding changes (split/merge/reorder items), update the plan before continuing. Do not let the plan go stale while coding.\n\nUse a plan when:\n\n- The task is non-trivial and will require multiple actions over a long time horizon.\n- There are logical phases or dependencies where sequencing matters.\n- The work has ambiguity that benefits from outlining high-level goals.\n- You want intermediate checkpoints for feedback and validation.\n- When the user asked you to do more than one thing in a single prompt\n- The user has asked you to use the plan tool (aka \"TODOs\")\n- You generate additional steps while working, and plan to do them before yielding to the user\n\n### Examples\n\n**High-quality plans**\n\nExample 1:\n\n1. Add CLI entry with file args\n2. Parse Markdown via CommonMark library\n3. Apply semantic HTML template\n4. Handle code blocks, images, links\n5. Add error handling for invalid files\n\nExample 2:\n\n1. Define CSS variables for colors\n2. Add toggle with localStorage state\n3. Refactor components to use variables\n4. Verify all views for readability\n5. Add smooth theme-change transition\n\nExample 3:\n\n1. Set up Node.js + WebSocket server\n2. Add join/leave broadcast events\n3. Implement messaging with timestamps\n4. Add usernames + mention highlighting\n5. Persist messages in lightweight DB\n6. Add typing indicators + unread count\n\n**Low-quality plans**\n\nExample 1:\n\n1. Create CLI tool\n2. Add Markdown parser\n3. Convert to HTML\n\nExample 2:\n\n1. Add dark mode toggle\n2. Save preference\n3. Make styles look good\n\nExample 3:\n\n1. Create single-file HTML game\n2. Run quick sanity check\n3. Summarize usage instructions\n\nIf you need to write a plan, only write high quality plans, not low quality ones.\n\n## Task execution\n\nYou are a coding agent. You must keep going until the query or task is completely resolved, before ending your turn and yielding back to the user. Persist until the task is fully handled end-to-end within the current turn whenever feasible and persevere even when function calls fail. Only terminate your turn when you are sure that the problem is solved. Autonomously resolve the query to the best of your ability, using the tools available to you, before coming back to the user. Do NOT guess or make up an answer.\n\nYou MUST adhere to the following criteria when solving queries:\n\n- Working on the repo(s) in the current environment is allowed, even if they are proprietary.\n- Analyzing code for vulnerabilities is allowed.\n- Showing user code and tool call details is allowed.\n- Use the `apply_patch` tool to edit files (NEVER try `applypatch` or `apply-patch`, only `apply_patch`). This is a FREEFORM tool, so do not wrap the patch in JSON.\n\nIf completing the user's task requires writing or modifying files, your code and final answer should follow these coding guidelines, though user instructions (i.e. AGENTS.md) may override these guidelines:\n\n- Fix the problem at the root cause rather than applying surface-level patches, when possible.\n- Avoid unneeded complexity in your solution.\n- Do not attempt to fix unrelated bugs or broken tests. It is not your responsibility to fix them. (You may mention them to the user in your final message though.)\n- Update documentation as necessary.\n- Keep changes consistent with the style of the existing codebase. Changes should be minimal and focused on the task.\n- Use `git log` and `git blame` to search the history of the codebase if additional context is required.\n- NEVER add copyright or license headers unless specifically requested.\n- Do not waste tokens by re-reading files after calling `apply_patch` on them. The tool call will fail if it didn't work. The same goes for making folders, deleting folders, etc.\n- Do not `git commit` your changes or create new git branches unless explicitly requested.\n- Do not add inline comments within code unless explicitly requested.\n- Do not use one-letter variable names unless explicitly requested.\n- NEVER output inline citations like \"【F:README.md†L5-L14】\" in your outputs. The CLI is not able to render these so they will just be broken in the UI. Instead, if you output valid filepaths, users will be able to click on them to open the files in their editor.\n\n## Codex CLI harness, sandboxing, and approvals\n\nThe Codex CLI harness supports several different configurations for sandboxing and escalation approvals that the user can choose from.\n\nFilesystem sandboxing defines which files can be read or written. The options for `sandbox_mode` are:\n- **read-only**: The sandbox only permits reading files.\n- **workspace-write**: The sandbox permits reading files, and editing files in `cwd` and `writable_roots`. Editing files in other directories requires approval.\n- **danger-full-access**: No filesystem sandboxing - all commands are permitted.\n\nNetwork sandboxing defines whether network can be accessed without approval. Options for `network_access` are:\n- **restricted**: Requires approval\n- **enabled**: No approval needed\n\nApprovals are your mechanism to get user consent to run shell commands without the sandbox. Possible configuration options for `approval_policy` are\n- **untrusted**: The harness will escalate most commands for user approval, apart from a limited allowlist of safe \"read\" commands.\n- **on-failure**: The harness will allow all commands to run in the sandbox (if enabled), and failures will be escalated to the user for approval to run again without the sandbox.\n- **on-request**: Commands will be run in the sandbox by default, and you can specify in your tool call if you want to escalate a command to run without sandboxing. (Note that this mode is not always available. If it is, you'll see parameters for escalating in the tool definition.)\n- **never**: This is a non-interactive mode where you may NEVER ask the user for approval to run commands. Instead, you must always persist and work around constraints to solve the task for the user. You MUST do your utmost best to finish the task and validate your work before yielding. If this mode is paired with `danger-full-access`, take advantage of it to deliver the best outcome for the user. Further, in this mode, your default testing philosophy is overridden: Even if you don't see local patterns for testing, you may add tests and scripts to validate your work. Just remove them before yielding.\n\nWhen you are running with `approval_policy == on-request`, and sandboxing enabled, here are scenarios where you'll need to request approval:\n- You need to run a command that writes to a directory that requires it (e.g. running tests that write to /var)\n- You need to run a GUI app (e.g., open/xdg-open/osascript) to open browsers or files.\n- You are running sandboxed and need to run a command that requires network access (e.g. installing packages)\n- If you run a command that is important to solving the user's query, but it fails because of sandboxing, rerun the command with approval. ALWAYS proceed to use the `with_escalated_permissions` and `justification` parameters. Within this harness, prefer requesting approval via the tool over asking in natural language.\n- You are about to take a potentially destructive action such as an `rm` or `git reset` that the user did not explicitly ask for\n- (for all of these, you should weigh alternative paths that do not require approval)\n\nWhen `sandbox_mode` is set to read-only, you'll need to request approval for any command that isn't a read.\n\nYou will be told what filesystem sandboxing, network sandboxing, and approval mode are active in a developer or user message. If you are not told about this, assume that you are running with workspace-write, network sandboxing enabled, and approval on-failure.\n\nAlthough they introduce friction to the user because your work is paused until the user responds, you should leverage them when necessary to accomplish important work. If the completing the task requires escalated permissions, Do not let these settings or the sandbox deter you from attempting to accomplish the user's task unless it is set to \"never\", in which case never ask for approvals.\n\nWhen requesting approval to execute a command that will require escalated privileges:\n  - Provide the `with_escalated_permissions` parameter with the boolean value true\n  - Include a short, 1 sentence explanation for why you need to enable `with_escalated_permissions` in the justification parameter\n\n## Validating your work\n\nIf the codebase has tests or the ability to build or run, consider using them to verify changes once your work is complete.\n\nWhen testing, your philosophy should be to start as specific as possible to the code you changed so that you can catch issues efficiently, then make your way to broader tests as you build confidence. If there's no test for the code you changed, and if the adjacent patterns in the codebases show that there's a logical place for you to add a test, you may do so. However, do not add tests to codebases with no tests.\n\nSimilarly, once you're confident in correctness, you can suggest or use formatting commands to ensure that your code is well formatted. If there are issues you can iterate up to 3 times to get formatting right, but if you still can't manage it's better to save the user time and present them a correct solution where you call out the formatting in your final message. If the codebase does not have a formatter configured, do not add one.\n\nFor all of testing, running, building, and formatting, do not attempt to fix unrelated bugs. It is not your responsibility to fix them. (You may mention them to the user in your final message though.)\n\nBe mindful of whether to run validation commands proactively. In the absence of behavioral guidance:\n\n- When running in non-interactive approval modes like **never** or **on-failure**, you can proactively run tests, lint and do whatever you need to ensure you've completed the task. If you are unable to run tests, you must still do your utmost best to complete the task.\n- When working in interactive approval modes like **untrusted**, or **on-request**, hold off on running tests or lint commands until the user is ready for you to finalize your output, because these commands take time to run and slow down iteration. Instead suggest what you want to do next, and let the user confirm first.\n- When working on test-related tasks, such as adding tests, fixing tests, or reproducing a bug to verify behavior, you may proactively run tests regardless of approval mode. Use your judgement to decide whether this is a test-related task.\n\n## Ambition vs. precision\n\nFor tasks that have no prior context (i.e. the user is starting something brand new), you should feel free to be ambitious and demonstrate creativity with your implementation.\n\nIf you're operating in an existing codebase, you should make sure you do exactly what the user asks with surgical precision. Treat the surrounding codebase with respect, and don't overstep (i.e. changing filenames or variables unnecessarily). You should balance being sufficiently ambitious and proactive when completing tasks of this nature.\n\nYou should use judicious initiative to decide on the right level of detail and complexity to deliver based on the user's needs. This means showing good judgment that you're capable of doing the right extras without gold-plating. This might be demonstrated by high-value, creative touches when scope of the task is vague; while being surgical and targeted when scope is tightly specified.\n\n## Sharing progress updates\n\nFor especially longer tasks that you work on (i.e. requiring many tool calls, or a plan with multiple steps), you should provide progress updates back to the user at reasonable intervals. These updates should be structured as a concise sentence or two (no more than 8-10 words long) recapping progress so far in plain language: this update demonstrates your understanding of what needs to be done, progress so far (i.e. files explores, subtasks complete), and where you're going next.\n\nBefore doing large chunks of work that may incur latency as experienced by the user (i.e. writing a new file), you should send a concise message to the user with an update indicating what you're about to do to ensure they know what you're spending time on. Don't start editing or writing large files before informing the user what you are doing and why.\n\nThe messages you send before tool calls should describe what is immediately about to be done next in very concise language. If there was previous work done, this preamble message should also include a note about the work done so far to bring the user along.\n\n## Presenting your work and final message\n\nYour final message should read naturally, like an update from a concise teammate. For casual conversation, brainstorming tasks, or quick questions from the user, respond in a friendly, conversational tone. You should ask questions, suggest ideas, and adapt to the user’s style. If you've finished a large amount of work, when describing what you've done to the user, you should follow the final answer formatting guidelines to communicate substantive changes. You don't need to add structured formatting for one-word answers, greetings, or purely conversational exchanges.\n\nYou can skip heavy formatting for single, simple actions or confirmations. In these cases, respond in plain sentences with any relevant next step or quick option. Reserve multi-section structured responses for results that need grouping or explanation.\n\nThe user is working on the same computer as you, and has access to your work. As such there's no need to show the contents of files you have already written unless the user explicitly asks for them. Similarly, if you've created or modified files using `apply_patch`, there's no need to tell users to \"save the file\" or \"copy the code into a file\"—just reference the file path.\n\nIf there's something that you think you could help with as a logical next step, concisely ask the user if they want you to do so. Good examples of this are running tests, committing changes, or building out the next logical component. If there’s something that you couldn't do (even with approval) but that the user might want to do (such as verifying changes by running the app), include those instructions succinctly.\n\nBrevity is very important as a default. You should be very concise (i.e. no more than 10 lines), but can relax this requirement for tasks where additional detail and comprehensiveness is important for the user's understanding.\n\n### Final answer structure and style guidelines\n\nYou are producing plain text that will later be styled by the CLI. Follow these rules exactly. Formatting should make results easy to scan, but not feel mechanical. Use judgment to decide how much structure adds value.\n\n**Section Headers**\n\n- Use only when they improve clarity — they are not mandatory for every answer.\n- Choose descriptive names that fit the content\n- Keep headers short (1–3 words) and in `**Title Case**`. Always start headers with `**` and end with `**`\n- Leave no blank line before the first bullet under a header.\n- Section headers should only be used where they genuinely improve scanability; avoid fragmenting the answer.\n\n**Bullets**\n\n- Use `-` followed by a space for every bullet.\n- Merge related points when possible; avoid a bullet for every trivial detail.\n- Keep bullets to one line unless breaking for clarity is unavoidable.\n- Group into short lists (4–6 bullets) ordered by importance.\n- Use consistent keyword phrasing and formatting across sections.\n\n**Monospace**\n\n- Wrap all commands, file paths, env vars, code identifiers, and code samples in backticks (`` `...` ``).\n- Apply to inline examples and to bullet keywords if the keyword itself is a literal file/command.\n- Never mix monospace and bold markers; choose one based on whether it’s a keyword (`**`) or inline code/path (`` ` ``).\n\n**File References**\nWhen referencing files in your response, make sure to include the relevant start line and always follow the below rules:\n  * Use inline code to make file paths clickable.\n  * Each reference should have a stand alone path. Even if it's the same file.\n  * Accepted: absolute, workspace‑relative, a/ or b/ diff prefixes, or bare filename/suffix.\n  * Line/column (1‑based, optional): :line[:column] or #Lline[Ccolumn] (column defaults to 1).\n  * Do not use URIs like file://, vscode://, or https://.\n  * Do not provide range of lines\n  * Examples: src/app.ts, src/app.ts:42, b/server/index.js#L10, C:\\repo\\project\\main.rs:12:5\n\n**Structure**\n\n- Place related bullets together; don’t mix unrelated concepts in the same section.\n- Order sections from general → specific → supporting info.\n- For subsections (e.g., “Binaries” under “Rust Workspace”), introduce with a bolded keyword bullet, then list items under it.\n- Match structure to complexity:\n  - Multi-part or detailed results → use clear headers and grouped bullets.\n  - Simple results → minimal headers, possibly just a short list or paragraph.\n\n**Tone**\n\n- Keep the voice collaborative and natural, like a coding partner handing off work.\n- Be concise and factual — no filler or conversational commentary and avoid unnecessary repetition\n- Use present tense and active voice (e.g., “Runs tests” not “This will run tests”).\n- Keep descriptions self-contained; don’t refer to “above” or “below”.\n- Use parallel structure in lists for consistency.\n\n**Verbosity**\n- Final answer compactness rules (enforced):\n  - Tiny/small single-file change (≤ ~10 lines): 2–5 sentences or ≤3 bullets. No headings. 0–1 short snippet (≤3 lines) only if essential.\n  - Medium change (single area or a few files): ≤6 bullets or 6–10 sentences. At most 1–2 short snippets total (≤8 lines each).\n  - Large/multi-file change: Summarize per file with 1–2 bullets; avoid inlining code unless critical (still ≤2 short snippets total).\n  - Never include \"before/after\" pairs, full method bodies, or large/scrolling code blocks in the final message. Prefer referencing file/symbol names instead.\n\n**Don’t**\n\n- Don’t use literal words “bold” or “monospace” in the content.\n- Don’t nest bullets or create deep hierarchies.\n- Don’t output ANSI escape codes directly — the CLI renderer applies them.\n- Don’t cram unrelated keywords into a single bullet; split for clarity.\n- Don’t let keyword lists run long — wrap or reformat for scanability.\n\nGenerally, ensure your final answers adapt their shape and depth to the request. For example, answers to code explanations should have a precise, structured explanation with code references that answer the question directly. For tasks with a simple implementation, lead with the outcome and supplement only with what’s needed for clarity. Larger changes can be presented as a logical walkthrough of your approach, grouping related steps, explaining rationale where it adds value, and highlighting next actions to accelerate the user. Your answers should provide the right level of detail while being easily scannable.\n\nFor casual greetings, acknowledgements, or other one-off conversational messages that are not delivering substantive information or structured results, respond naturally without section headers or bullet formatting.\n\n# Tool Guidelines\n\n## Shell commands\n\nWhen using the shell, you must adhere to the following guidelines:\n\n- When searching for text or files, prefer using `rg` or `rg --files` respectively because `rg` is much faster than alternatives like `grep`. (If the `rg` command is not found, then use alternatives.)\n- Read files in chunks with a max chunk size of 250 lines. Do not use python scripts to attempt to output larger chunks of a file. Command line output will be truncated after 10 kilobytes or 256 lines of output, regardless of the command used.\n\n## apply_patch\n\nUse the `apply_patch` tool to edit files. Your patch language is a stripped‑down, file‑oriented diff format designed to be easy to parse and safe to apply. You can think of it as a high‑level envelope:\n\n*** Begin Patch\n[ one or more file sections ]\n*** End Patch\n\nWithin that envelope, you get a sequence of file operations.\nYou MUST include a header to specify the action you are taking.\nEach operation starts with one of three headers:\n\n*** Add File: <path> - create a new file. Every following line is a + line (the initial contents).\n*** Delete File: <path> - remove an existing file. Nothing follows.\n*** Update File: <path> - patch an existing file in place (optionally with a rename).\n\nExample patch:\n\n```\n*** Begin Patch\n*** Add File: hello.txt\n+Hello world\n*** Update File: src/app.py\n*** Move to: src/main.py\n@@ def greet():\n-print(\"Hi\")\n+print(\"Hello, world!\")\n*** Delete File: obsolete.txt\n*** End Patch\n```\n\nIt is important to remember:\n\n- You must include a header with your intended action (Add/Delete/Update)\n- You must prefix new lines with `+` even when creating a new file\n\n## `update_plan`\n\nA tool named `update_plan` is available to you. You can use it to keep an up‑to‑date, step‑by‑step plan for the task.\n\nTo create a new plan, call `update_plan` with a short list of 1‑sentence steps (no more than 5-7 words each) with a `status` for each step (`pending`, `in_progress`, or `completed`).\n\nWhen steps have been completed, use `update_plan` to mark each finished step as `completed` and the next step you are working on as `in_progress`. There should always be exactly one `in_progress` step until everything is done. You can mark multiple items as complete in a single `update_plan` call.\n\nIf all steps are complete, ensure you call `update_plan` to mark all steps as `completed`.\n",
+    "input": [
+      {
+        "type": "message",
+        "role": "user",
+        "content": [
+          {
+            "type": "input_text",
+            "text": "# AGENTS.md instructions for /Users/fanzhang/Documents/github/uvcmirror\n\n<INSTRUCTIONS>\n# AGENTS 指南\n\n1. **函数化 & 模块化**  \n   - 所有业务逻辑必须拆分为清晰的函数/模块，严禁在 `main` 或控制器中堆砌扁平代码。  \n   - 每个模块暴露明确的 API，便于追踪调用路径和单元测试。  \n2. **调用路径可追踪**  \n   - 在关键入口增加结构化日志（`tracing`），记录函数名、调用参数与结果，确保 dev 版本能够追踪完整执行路径。  \n   - 对关键流程可生成快照/trace（例如将请求上下文写入调试文件）以便复现问题。  \n3. **日志与快照策略**  \n   - dev 构建启用 verbose 日志与简易快照输出；release 构建默认关闭快照，只保留必要日志。  \n   - 快照命名包含时间戳 + 函数名，避免相互覆盖；日志需包含 correlation id（例如 session_id）。  \n4. **审查要求**  \n   - PR/代码提交前必须检查是否违反上面约束；如需临时放宽需在 `AGENTS.md` 记录原因与期限。  \n\n</INSTRUCTIONS>"
+          }
+        ]
+      },
+      {
+        "type": "message",
+        "role": "user",
+        "content": [
+          {
+            "type": "input_text",
+            "text": "<environment_context>\n  <cwd>/Users/fanzhang/Documents/github/uvcmirror</cwd>\n  <approval_policy>on-request</approval_policy>\n  <sandbox_mode>workspace-write</sandbox_mode>\n  <network_access>restricted</network_access>\n  <shell>zsh</shell>\n</environment_context>"
+          }
+        ]
+      },
+      {
+        "type": "message",
+        "role": "user",
+        "content": [
+          {
+            "type": "input_text",
+            "text": "列出本地文件"
+          }
+        ]
+      }
+    ],
+    "tools": [
+      {
+        "type": "function",
+        "name": "shell_command",
+        "description": "Runs a shell command and returns its output.\n- Always set the `workdir` param when using the shell_command function. Do not use `cd` unless absolutely necessary.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "command": {
+              "type": "string",
+              "description": "The shell script to execute in the user's default shell"
+            },
+            "justification": {
+              "type": "string",
+              "description": "Only set if with_escalated_permissions is true. 1-sentence explanation of why we want to run this command."
+            },
+            "timeout_ms": {
+              "type": "number",
+              "description": "The timeout for the command in milliseconds"
+            },
+            "with_escalated_permissions": {
+              "type": "boolean",
+              "description": "Whether to request escalated permissions. Set to true if command needs to be run without sandbox restrictions"
+            },
+            "workdir": {
+              "type": "string",
+              "description": "The working directory to execute the command in"
+            }
+          },
+          "required": [
+            "command"
+          ],
+          "additionalProperties": false
+        }
+      },
+      {
+        "type": "function",
+        "name": "list_mcp_resources",
+        "description": "Lists resources provided by MCP servers. Resources allow servers to share data that provides context to language models, such as files, database schemas, or application-specific information. Prefer resources over web search when possible.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "cursor": {
+              "type": "string",
+              "description": "Opaque cursor returned by a previous list_mcp_resources call for the same server."
+            },
+            "server": {
+              "type": "string",
+              "description": "Optional MCP server name. When omitted, lists resources from every configured server."
+            }
+          },
+          "additionalProperties": false
+        }
+      },
+      {
+        "type": "function",
+        "name": "list_mcp_resource_templates",
+        "description": "Lists resource templates provided by MCP servers. Parameterized resource templates allow servers to share data that takes parameters and provides context to language models, such as files, database schemas, or application-specific information. Prefer resource templates over web search when possible.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "cursor": {
+              "type": "string",
+              "description": "Opaque cursor returned by a previous list_mcp_resource_templates call for the same server."
+            },
+            "server": {
+              "type": "string",
+              "description": "Optional MCP server name. When omitted, lists resource templates from all configured servers."
+            }
+          },
+          "additionalProperties": false
+        }
+      },
+      {
+        "type": "function",
+        "name": "read_mcp_resource",
+        "description": "Read a specific resource from an MCP server given the server name and resource URI.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "server": {
+              "type": "string",
+              "description": "MCP server name exactly as configured. Must match the 'server' field returned by list_mcp_resources."
+            },
+            "uri": {
+              "type": "string",
+              "description": "Resource URI to read. Must be one of the URIs returned by list_mcp_resources."
+            }
+          },
+          "required": [
+            "server",
+            "uri"
+          ],
+          "additionalProperties": false
+        }
+      },
+      {
+        "type": "function",
+        "name": "update_plan",
+        "description": "Updates the task plan.\nProvide an optional explanation and a list of plan items, each with a step and status.\nAt most one step can be in_progress at a time.\n",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "explanation": {
+              "type": "string"
+            },
+            "plan": {
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "status": {
+                    "type": "string",
+                    "description": "One of: pending, in_progress, completed"
+                  },
+                  "step": {
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "step",
+                  "status"
+                ],
+                "additionalProperties": false
+              },
+              "description": "The list of steps"
+            }
+          },
+          "required": [
+            "plan"
+          ],
+          "additionalProperties": false
+        }
+      },
+      {
+        "type": "custom",
+        "name": "apply_patch",
+        "description": "Use the `apply_patch` tool to edit files. This is a FREEFORM tool, so do not wrap the patch in JSON.",
+        "format": {
+          "type": "grammar",
+          "syntax": "lark",
+          "definition": "start: begin_patch hunk+ end_patch\nbegin_patch: \"*** Begin Patch\" LF\nend_patch: \"*** End Patch\" LF?\n\nhunk: add_hunk | delete_hunk | update_hunk\nadd_hunk: \"*** Add File: \" filename LF add_line+\ndelete_hunk: \"*** Delete File: \" filename LF\nupdate_hunk: \"*** Update File: \" filename LF change_move? change?\n\nfilename: /(.+)/\nadd_line: \"+\" /(.*)/ LF -> line\n\nchange_move: \"*** Move to: \" filename LF\nchange: (change_context | change_line)+ eof_line?\nchange_context: (\"@@\" | \"@@ \" /(.+)/) LF\nchange_line: (\"+\" | \"-\" | \" \") /(.*)/ LF\neof_line: \"*** End of File\" LF\n\n%import common.LF\n"
+        }
+      },
+      {
+        "type": "function",
+        "name": "view_image",
+        "description": "Attach a local image (by filesystem path) to the conversation context for this turn.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "path": {
+              "type": "string",
+              "description": "Local filesystem path to an image file"
+            }
+          },
+          "required": [
+            "path"
+          ],
+          "additionalProperties": false
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__click",
+        "description": "Clicks on the provided element",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "dblClick": {
+              "type": "boolean",
+              "description": "Set to true for double clicks. Default is false."
+            },
+            "uid": {
+              "type": "string",
+              "description": "The uid of an element on the page from the page content snapshot"
+            }
+          },
+          "required": [
+            "uid"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__close_page",
+        "description": "Closes the page by its index. The last open page cannot be closed.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "pageIdx": {
+              "type": "number",
+              "description": "The index of the page to close. Call list_pages to list pages."
+            }
+          },
+          "required": [
+            "pageIdx"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__drag",
+        "description": "Drag an element onto another element",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "from_uid": {
+              "type": "string",
+              "description": "The uid of the element to drag"
+            },
+            "to_uid": {
+              "type": "string",
+              "description": "The uid of the element to drop into"
+            }
+          },
+          "required": [
+            "from_uid",
+            "to_uid"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__emulate",
+        "description": "Emulates various features on the selected page.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "cpuThrottlingRate": {
+              "type": "number",
+              "description": "Represents the CPU slowdown factor. Set the rate to 1 to disable throttling. If omitted, throttling remains unchanged."
+            },
+            "networkConditions": {
+              "type": "string",
+              "description": "Throttle network. Set to \"No emulation\" to disable. If omitted, conditions remain unchanged."
+            }
+          }
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__evaluate_script",
+        "description": "Evaluate a JavaScript function inside the currently selected page. Returns the response as JSON\nso returned values have to JSON-serializable.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "args": {
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "uid": {
+                    "type": "string",
+                    "description": "The uid of an element on the page from the page content snapshot"
+                  }
+                },
+                "required": [
+                  "uid"
+                ],
+                "additionalProperties": false
+              },
+              "description": "An optional list of arguments to pass to the function."
+            },
+            "function": {
+              "type": "string",
+              "description": "A JavaScript function declaration to be executed by the tool in the currently selected page.\nExample without arguments: `() => {\n  return document.title\n}` or `async () => {\n  return await fetch(\"example.com\")\n}`.\nExample with arguments: `(el) => {\n  return el.innerText;\n}`\n"
+            }
+          },
+          "required": [
+            "function"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__fill",
+        "description": "Type text into a input, text area or select an option from a <select> element.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "uid": {
+              "type": "string",
+              "description": "The uid of an element on the page from the page content snapshot"
+            },
+            "value": {
+              "type": "string",
+              "description": "The value to fill in"
+            }
+          },
+          "required": [
+            "uid",
+            "value"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__fill_form",
+        "description": "Fill out multiple form elements at once",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "elements": {
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "uid": {
+                    "type": "string",
+                    "description": "The uid of the element to fill out"
+                  },
+                  "value": {
+                    "type": "string",
+                    "description": "Value for the element"
+                  }
+                },
+                "required": [
+                  "uid",
+                  "value"
+                ],
+                "additionalProperties": false
+              },
+              "description": "Elements from snapshot to fill out."
+            }
+          },
+          "required": [
+            "elements"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__get_console_message",
+        "description": "Gets a console message by its ID. You can get all messages by calling list_console_messages.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "msgid": {
+              "type": "number",
+              "description": "The msgid of a console message on the page from the listed console messages"
+            }
+          },
+          "required": [
+            "msgid"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__get_network_request",
+        "description": "Gets a network request by an optional reqid, if omitted returns the currently selected request in the DevTools Network panel.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "reqid": {
+              "type": "number",
+              "description": "The reqid of the network request. If omitted returns the currently selected request in the DevTools Network panel."
+            }
+          }
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__handle_dialog",
+        "description": "If a browser dialog was opened, use this command to handle it",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "action": {
+              "type": "string",
+              "description": "Whether to dismiss or accept the dialog"
+            },
+            "promptText": {
+              "type": "string",
+              "description": "Optional prompt text to enter into the dialog."
+            }
+          },
+          "required": [
+            "action"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__hover",
+        "description": "Hover over the provided element",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "uid": {
+              "type": "string",
+              "description": "The uid of an element on the page from the page content snapshot"
+            }
+          },
+          "required": [
+            "uid"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__list_console_messages",
+        "description": "List all console messages for the currently selected page since the last navigation.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "includePreservedMessages": {
+              "type": "boolean",
+              "description": "Set to true to return the preserved messages over the last 3 navigations."
+            },
+            "pageIdx": {
+              "type": "number",
+              "description": "Page number to return (0-based). When omitted, returns the first page."
+            },
+            "pageSize": {
+              "type": "number",
+              "description": "Maximum number of messages to return. When omitted, returns all requests."
+            },
+            "types": {
+              "type": "array",
+              "items": {
+                "type": "string"
+              },
+              "description": "Filter messages to only return messages of the specified resource types. When omitted or empty, returns all messages."
+            }
+          }
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__list_network_requests",
+        "description": "List all requests for the currently selected page since the last navigation.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "includePreservedRequests": {
+              "type": "boolean",
+              "description": "Set to true to return the preserved requests over the last 3 navigations."
+            },
+            "pageIdx": {
+              "type": "number",
+              "description": "Page number to return (0-based). When omitted, returns the first page."
+            },
+            "pageSize": {
+              "type": "number",
+              "description": "Maximum number of requests to return. When omitted, returns all requests."
+            },
+            "resourceTypes": {
+              "type": "array",
+              "items": {
+                "type": "string"
+              },
+              "description": "Filter requests to only return requests of the specified resource types. When omitted or empty, returns all requests."
+            }
+          }
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__list_pages",
+        "description": "Get a list of pages open in the browser.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {}
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__navigate_page",
+        "description": "Navigates the currently selected page to a URL.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "ignoreCache": {
+              "type": "boolean",
+              "description": "Whether to ignore cache on reload."
+            },
+            "timeout": {
+              "type": "number",
+              "description": "Maximum wait time in milliseconds. If set to 0, the default timeout will be used."
+            },
+            "type": {
+              "type": "string",
+              "description": "Navigate the page by URL, back or forward in history, or reload."
+            },
+            "url": {
+              "type": "string",
+              "description": "Target URL (only type=url)"
+            }
+          }
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__new_page",
+        "description": "Creates a new page",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "timeout": {
+              "type": "number",
+              "description": "Maximum wait time in milliseconds. If set to 0, the default timeout will be used."
+            },
+            "url": {
+              "type": "string",
+              "description": "URL to load in a new page."
+            }
+          },
+          "required": [
+            "url"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__performance_analyze_insight",
+        "description": "Provides more detailed information on a specific Performance Insight of an insight set that was highlighted in the results of a trace recording.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "insightName": {
+              "type": "string",
+              "description": "The name of the Insight you want more information on. For example: \"DocumentLatency\" or \"LCPBreakdown\""
+            },
+            "insightSetId": {
+              "type": "string",
+              "description": "The id for the specific insight set. Only use the ids given in the \"Available insight sets\" list."
+            }
+          },
+          "required": [
+            "insightSetId",
+            "insightName"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__performance_start_trace",
+        "description": "Starts a performance trace recording on the selected page. This can be used to look for performance problems and insights to improve the performance of the page. It will also report Core Web Vital (CWV) scores for the page.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "autoStop": {
+              "type": "boolean",
+              "description": "Determines if the trace recording should be automatically stopped."
+            },
+            "reload": {
+              "type": "boolean",
+              "description": "Determines if, once tracing has started, the page should be automatically reloaded."
+            }
+          },
+          "required": [
+            "reload",
+            "autoStop"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__performance_stop_trace",
+        "description": "Stops the active performance trace recording on the selected page.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {}
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__press_key",
+        "description": "Press a key or key combination. Use this when other input methods like fill() cannot be used (e.g., keyboard shortcuts, navigation keys, or special key combinations).",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "key": {
+              "type": "string",
+              "description": "A key or a combination (e.g., \"Enter\", \"Control+A\", \"Control++\", \"Control+Shift+R\"). Modifiers: Control, Shift, Alt, Meta"
+            }
+          },
+          "required": [
+            "key"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__resize_page",
+        "description": "Resizes the selected page's window so that the page has specified dimension",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "height": {
+              "type": "number",
+              "description": "Page height"
+            },
+            "width": {
+              "type": "number",
+              "description": "Page width"
+            }
+          },
+          "required": [
+            "width",
+            "height"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__select_page",
+        "description": "Select a page as a context for future tool calls.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "pageIdx": {
+              "type": "number",
+              "description": "The index of the page to select. Call list_pages to list pages."
+            }
+          },
+          "required": [
+            "pageIdx"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__take_screenshot",
+        "description": "Take a screenshot of the page or element.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "filePath": {
+              "type": "string",
+              "description": "The absolute path, or a path relative to the current working directory, to save the screenshot to instead of attaching it to the response."
+            },
+            "format": {
+              "type": "string",
+              "description": "Type of format to save the screenshot as. Default is \"png\""
+            },
+            "fullPage": {
+              "type": "boolean",
+              "description": "If set to true takes a screenshot of the full page instead of the currently visible viewport. Incompatible with uid."
+            },
+            "quality": {
+              "type": "number",
+              "description": "Compression quality for JPEG and WebP formats (0-100). Higher values mean better quality but larger file sizes. Ignored for PNG format."
+            },
+            "uid": {
+              "type": "string",
+              "description": "The uid of an element on the page from the page content snapshot. If omitted takes a pages screenshot."
+            }
+          }
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__take_snapshot",
+        "description": "Take a text snapshot of the currently selected page based on the a11y tree. The snapshot lists page elements along with a unique\nidentifier (uid). Always use the latest snapshot. Prefer taking a snapshot over taking a screenshot. The snapshot indicates the element selected\nin the DevTools Elements panel (if any).",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "filePath": {
+              "type": "string",
+              "description": "The absolute path, or a path relative to the current working directory, to save the snapshot to instead of attaching it to the response."
+            },
+            "verbose": {
+              "type": "boolean",
+              "description": "Whether to include all possible information available in the full a11y tree. Default is false."
+            }
+          }
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__upload_file",
+        "description": "Upload a file through a provided element.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "filePath": {
+              "type": "string",
+              "description": "The local path of the file to upload"
+            },
+            "uid": {
+              "type": "string",
+              "description": "The uid of the file input element or an element that will open file chooser on the page from the page content snapshot"
+            }
+          },
+          "required": [
+            "uid",
+            "filePath"
+          ]
+        }
+      },
+      {
+        "type": "function",
+        "name": "mcp__chrome-devtools__wait_for",
+        "description": "Wait for the specified text to appear on the selected page.",
+        "strict": false,
+        "parameters": {
+          "type": "object",
+          "properties": {
+            "text": {
+              "type": "string",
+              "description": "Text to appear on the page"
+            },
+            "timeout": {
+              "type": "number",
+              "description": "Maximum wait time in milliseconds. If set to 0, the default timeout will be used."
+            }
+          },
+          "required": [
+            "text"
+          ]
+        }
+      }
+    ],
+    "tool_choice": "auto",
+    "parallel_tool_calls": false,
+    "reasoning": {
+      "effort": "high",
+      "summary": "auto"
+    },
+    "store": false,
+    "stream": true,
+    "include": [
+      "reasoning.encrypted_content"
+    ],
+    "prompt_cache_key": "019add08-943a-7311-9086-5653a7c6e246",
+    "text": {
+      "verbosity": "low"
+    }
+  }
+}