[Bug] Cursor replay clips completed-call arguments at 2 KiB despite spare aggregate budget #4516

[
  {
    "role": "system",
    "content": "You are a helpful assistant."
  },
  {
    "role": "system",
    "content": "Cursor tool calls: available tool names are exactly `exec`. Use the current tool catalog as ground truth and call only those exact names with their listed argument keys. This turn does not expose neighboring-agent tool names `Read`, `Grep`, `Glob`, `Bash`, `LS`; do not call or suggest them unless the catalog lists them. `exec` is Codex code mode: its body is JavaScript evaluated in a V8 isolate, not a shell command and not Node. Shell, file edits, and MCP are nested helpers called INSIDE that body as `await tools.<name>(...)`, for example `await tools.exec_command({cmd: \"ls\"})`. Read the tool description and the isolate global `ALL_TOOLS` (not `tools.ALL_TOOLS`) for helpers this turn provides; absence from the top-level catalog or from `exec`'s description is not absence. Those nested helpers are not themselves top-level tools, so do not call `exec_command` or `shell_command` at the top level here. Nested `tools.apply_patch(input)` is host-executed: the string must begin exactly with `*** Begin Patch` and end with `*** End Patch`, each marker line being three asterisks, one space, the two words, then end of line with no further asterisks. OpenCodex does not rewrite JavaScript inside exec, so extra asterisks on a marker line are rejected by Codex before the file is touched. Nothing in the isolate is echoed automatically: a bare trailing `await tools.<name>(...)` or final expression value is DISCARDED, and the cell reports empty output. Pass anything you need to read to `text(...)` (or `notify(...)`) in the same cell — for example `text(JSON.stringify(await tools.exec_command({cmd: 'ls'})))` — and treat an empty result as your own missing `text(...)` call rather than a failed command or lost context. There is no `require`, no `module`, and no filesystem or network globals; reach the host only through the nested helpers. Host contract for the nested helpers: `tools.apply_patch(patch)` takes exactly one string, never an object such as `{input: ...}`; the patch text opens with the bare marker line `*** Begin Patch` and closes with the bare marker line `*** End Patch`, written without a code fence, prose, or extra asterisks on those lines (blank lines or indentation around the markers are tolerated; a decorated or missing marker is rejected). The isolate has no `import`, `require`, or module loader; use the globals the exec tool description lists (for example `tools`, `text`, `notify`, `store`/`load`, `ALL_TOOLS`). For a command that may outlive `yield_time_ms`, let `tools.exec_command` return a `session_id` and poll it on later calls with `tools.write_stdin({session_id, chars: \"\"})` instead of blocking a shell in a sleep loop. NEVER attempt Cursor-native Shell, Read, Grep, List, or any tool absent from the catalog — they are not executed in this environment and every probe wastes a turn. The exec code cell (with its nested helpers) is the ONLY execution surface; go to it directly on the FIRST attempt and do not narrate switching surfaces. Cursor product features (Chronicle, screen recording, Notes, Plans, background agents) are available only if this turn's catalog lists a matching tool; do not offer or promise them otherwise. For independent read-only tool-count or batch requests, prefer one response containing multiple tool calls before waiting for results when the runtime supports parallel tool calls. Do not count or report a tool call unless a tool result was actually returned."
  },
  {
    "role": "user",
    "content": [
      {
        "type": "text",
        "text": "Return the value from the end of the completed call. Return MISSING if absent."
      }
    ]
  },
  {
    "role": "assistant",
    "content": [
      {
        "type": "text",
        "text": "[Tool Result]\n[tool_result]\ncall_id: synthetic_call\nname: exec\ninvoked: exec with {\"input\":\"// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic…[arguments truncated]\nis_error: false\noutput:\nSuccess. Updated fixture.txt."
      }
    ]
  }
]

[
  {
    "role": "system",
    "content": "You are a helpful assistant."
  },
  {
    "role": "system",
    "content": "Cursor tool calls: available tool names are exactly `exec`. Use the current tool catalog as ground truth and call only those exact names with their listed argument keys. This turn does not expose neighboring-agent tool names `Read`, `Grep`, `Glob`, `Bash`, `LS`; do not call or suggest them unless the catalog lists them. `exec` is Codex code mode: its body is JavaScript evaluated in a V8 isolate, not a shell command and not Node. Shell, file edits, and MCP are nested helpers called INSIDE that body as `await tools.<name>(...)`, for example `await tools.exec_command({cmd: \"ls\"})`. Read the tool description and the isolate global `ALL_TOOLS` (not `tools.ALL_TOOLS`) for helpers this turn provides; absence from the top-level catalog or from `exec`'s description is not absence. Those nested helpers are not themselves top-level tools, so do not call `exec_command` or `shell_command` at the top level here. Nested `tools.apply_patch(input)` is host-executed: the string must begin exactly with `*** Begin Patch` and end with `*** End Patch`, each marker line being three asterisks, one space, the two words, then end of line with no further asterisks. OpenCodex does not rewrite JavaScript inside exec, so extra asterisks on a marker line are rejected by Codex before the file is touched. Nothing in the isolate is echoed automatically: a bare trailing `await tools.<name>(...)` or final expression value is DISCARDED, and the cell reports empty output. Pass anything you need to read to `text(...)` (or `notify(...)`) in the same cell — for example `text(JSON.stringify(await tools.exec_command({cmd: 'ls'})))` — and treat an empty result as your own missing `text(...)` call rather than a failed command or lost context. There is no `require`, no `module`, and no filesystem or network globals; reach the host only through the nested helpers. Host contract for the nested helpers: `tools.apply_patch(patch)` takes exactly one string, never an object such as `{input: ...}`; the patch text opens with the bare marker line `*** Begin Patch` and closes with the bare marker line `*** End Patch`, written without a code fence, prose, or extra asterisks on those lines (blank lines or indentation around the markers are tolerated; a decorated or missing marker is rejected). The isolate has no `import`, `require`, or module loader; use the globals the exec tool description lists (for example `tools`, `text`, `notify`, `store`/`load`, `ALL_TOOLS`). For a command that may outlive `yield_time_ms`, let `tools.exec_command` return a `session_id` and poll it on later calls with `tools.write_stdin({session_id, chars: \"\"})` instead of blocking a shell in a sleep loop. NEVER attempt Cursor-native Shell, Read, Grep, List, or any tool absent from the catalog — they are not executed in this environment and every probe wastes a turn. The exec code cell (with its nested helpers) is the ONLY execution surface; go to it directly on the FIRST attempt and do not narrate switching surfaces. Cursor product features (Chronicle, screen recording, Notes, Plans, background agents) are available only if this turn's catalog lists a matching tool; do not offer or promise them otherwise. For independent read-only tool-count or batch requests, prefer one response containing multiple tool calls before waiting for results when the runtime supports parallel tool calls. Do not count or report a tool call unless a tool result was actually returned."
  },
  {
    "role": "user",
    "content": [
      {
        "type": "text",
        "text": "Return the value from the end of the completed call. Return MISSING if absent."
      }
    ]
  },
  {
    "role": "assistant",
    "content": [
      {
        "type": "text",
        "text": "[Tool Result]\n[tool_result]\ncall_id: synthetic_call\nname: exec\ninvoked: exec with {\"input\":\"// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\n// synthetic padding\\nwrite_value(\\\"SYNTHETIC_TAIL_71e463b9\\\", \\\"界🙂\\\", \\\"$&\\\", \\\"$$\\\", \\\"$`\\\", \\\"$'\\\")\"}\nis_error: false\noutput:\nSuccess. Updated fixture.txt."
      }
    ]
  }
]