@yanlinglabs/winter-conformance 0.0.15 → 0.0.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/official/differential-harness.d.ts +90 -0
- package/goldens/advertised-set-round.trace.json +2 -2
- package/goldens/multi-turn.trace.json +4 -4
- package/goldens/plain-query.trace.json +2 -2
- package/goldens/resume.trace.json +4 -4
- package/goldens/sendmessage-child-round.trace.json +2 -1
- package/goldens/subagent-permission-round.trace.json +2 -1
- package/goldens/subagent-spawn-round.trace.json +2 -1
- package/package.json +1 -1
|
@@ -0,0 +1,90 @@
|
|
|
1
|
+
export declare const CLAUDE_VERSION = "0.3.250";
|
|
2
|
+
export declare const OFFICIAL_MODEL = "claude-haiku-4-5";
|
|
3
|
+
export type RawFrame = Record<string, unknown>;
|
|
4
|
+
export type ResolvedBinary = {
|
|
5
|
+
binaryPath: string;
|
|
6
|
+
} | {
|
|
7
|
+
reason: string;
|
|
8
|
+
};
|
|
9
|
+
/**
|
|
10
|
+
* Resolves (fetching + installing on first use, into a CACHED prefix reused across runs) the pinned
|
|
11
|
+
* claude binary. Returns `{reason}` -- never throws -- for every reason it might be unavailable, so
|
|
12
|
+
* every caller's `describe.skipIf` can report the reason plainly.
|
|
13
|
+
*/
|
|
14
|
+
export declare function resolvePinnedClaudeBinary(): Promise<ResolvedBinary>;
|
|
15
|
+
export interface OfficialRoots {
|
|
16
|
+
root: string;
|
|
17
|
+
home: string;
|
|
18
|
+
cfg: string;
|
|
19
|
+
cwd: string;
|
|
20
|
+
}
|
|
21
|
+
/** Fresh mkdtemp HOME/CLAUDE_CONFIG_DIR/cwd under one owned root -- never the real `~/.claude`. */
|
|
22
|
+
export declare function makeOfficialRoots(prefix: string): OfficialRoots;
|
|
23
|
+
export declare function cleanupRoots(r: OfficialRoots): void;
|
|
24
|
+
/**
|
|
25
|
+
* The explicit, minimal env every spawn in this family uses -- never a `process.env` spread. `extra`
|
|
26
|
+
* merges last (an env var a specific scenario needs, e.g. `CLAUDE_CODE_FORK_SUBAGENT`).
|
|
27
|
+
*/
|
|
28
|
+
export declare function minimalOfficialEnv(opts: {
|
|
29
|
+
home: string;
|
|
30
|
+
cfg: string;
|
|
31
|
+
baseUrl: string;
|
|
32
|
+
extra?: Record<string, string>;
|
|
33
|
+
}): Record<string, string>;
|
|
34
|
+
export interface SseEvent {
|
|
35
|
+
event: string;
|
|
36
|
+
data: unknown;
|
|
37
|
+
}
|
|
38
|
+
export declare function sseResponse(events: SseEvent[]): Response;
|
|
39
|
+
/** One assistant turn carrying N `tool_use` blocks (batched, as a model that calls several tools at
|
|
40
|
+
* once does -- scenario 4's two sibling forks are one assistant message with two blocks). */
|
|
41
|
+
export declare function sseToolUseTurn(blocks: Array<{
|
|
42
|
+
id: string;
|
|
43
|
+
name: string;
|
|
44
|
+
input: unknown;
|
|
45
|
+
}>, opts?: {
|
|
46
|
+
msgId?: string;
|
|
47
|
+
}): SseEvent[];
|
|
48
|
+
export declare function sseTextTurn(text: string, opts?: {
|
|
49
|
+
msgId?: string;
|
|
50
|
+
}): SseEvent[];
|
|
51
|
+
/**
|
|
52
|
+
* A `Bun.serve` fake of the Anthropic Messages API that keeps the RAW request body (never just
|
|
53
|
+
* `.messages`, unlike `task-frames-differential.test.ts`'s own inline server -- request-layout
|
|
54
|
+
* scenarios need `system`/`tools`/every top-level key too) and routes every POST by content through
|
|
55
|
+
* the caller's `route` callback. Every request is logged to stderr (structural facts only -- request
|
|
56
|
+
* count, path, message count/roles -- never the system/tools prose, matching this whole file
|
|
57
|
+
* family's own logging discipline). Non-POST hits (health-check pings) get a benign ack.
|
|
58
|
+
*/
|
|
59
|
+
export declare function startCapturingLoopback(route: (messages: RawFrame[], body: RawFrame, count: number) => Response, logPrefix?: string): {
|
|
60
|
+
url: string;
|
|
61
|
+
requests: RawFrame[];
|
|
62
|
+
stop: () => void;
|
|
63
|
+
};
|
|
64
|
+
export interface OfficialStreamSession {
|
|
65
|
+
/** Writes one NDJSON `type:"user"` frame to stdin and flushes -- the exact shape the pinned binary's `--input-format stream-json` accepts, verified against a real spawn (spike, 2026-09-17). */
|
|
66
|
+
send(text: string): void;
|
|
67
|
+
/** Reads (and buffers) stdout frames until `pred` matches one (inclusive); returns every frame seen so far, from the start of the stream. Throws with the stderr tail on timeout. */
|
|
68
|
+
readUntil(pred: (frame: RawFrame) => boolean, timeoutMs?: number): Promise<RawFrame[]>;
|
|
69
|
+
/** Waits `graceMs`, returning whatever NEW frames (since the last `readUntil`/`drainQuiet` call) arrived in that window -- used to prove nothing MORE arrives unprompted (P16-3's held-vs-immediate `result` claim). */
|
|
70
|
+
drainQuiet(graceMs: number): Promise<RawFrame[]>;
|
|
71
|
+
/** Every frame seen so far, in order (same backing array `readUntil`/`drainQuiet` read from). */
|
|
72
|
+
allFrames: RawFrame[];
|
|
73
|
+
/** Ends stdin -- the binary's own `--input-format stream-json` exits once it sees EOF and no task is holding it open. */
|
|
74
|
+
close(): void;
|
|
75
|
+
exited: Promise<number | null>;
|
|
76
|
+
stderrTail(n?: number): string;
|
|
77
|
+
}
|
|
78
|
+
/**
|
|
79
|
+
* Spawns the pinned binary with stdin held open (`-p --input-format stream-json --output-format
|
|
80
|
+
* stream-json --verbose`), the shape scenarios 1/2/5 need (a two-turn or open-ended conversation in
|
|
81
|
+
* ONE process, matching R3a's "streaming-input hosts... never get a held result" claim and R4's
|
|
82
|
+
* "index-0 stable across turns" claim -- both need turns inside a single live session, not two
|
|
83
|
+
* separate `--resume` invocations). `opts.args` are extra flags appended after the fixed base set.
|
|
84
|
+
*/
|
|
85
|
+
export declare function spawnOfficialStreamJson(opts: {
|
|
86
|
+
binaryPath: string;
|
|
87
|
+
env: Record<string, string>;
|
|
88
|
+
cwd: string;
|
|
89
|
+
args?: string[];
|
|
90
|
+
}): OfficialStreamSession;
|
|
@@ -66,7 +66,7 @@
|
|
|
66
66
|
"content": [
|
|
67
67
|
{
|
|
68
68
|
"type": "text",
|
|
69
|
-
"text": "echo: <system-reminder>\
|
|
69
|
+
"text": "echo: <system-reminder>\nAvailable agent types for the Agent tool:\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \"src/components/**/*.tsx\"), grep for symbols or keywords (eg. \"API endpoints\"), or answer \"where is X defined / which files reference Y.\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \"quick\" for a single targeted lookup, \"medium\" for moderate exploration, or \"very thorough\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\n</system-reminder>\n\n<system-reminder>\nAs you answer the user's questions, you can use the following context:\n# currentDate\nToday's date is <FIXTURE-DATE>.\n\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\n</system-reminder>\n\n\nhi"
|
|
70
70
|
}
|
|
71
71
|
]
|
|
72
72
|
}
|
|
@@ -80,7 +80,7 @@
|
|
|
80
80
|
"type": "result",
|
|
81
81
|
"subtype": "success",
|
|
82
82
|
"is_error": false,
|
|
83
|
-
"result": "echo: <system-reminder>\
|
|
83
|
+
"result": "echo: <system-reminder>\nAvailable agent types for the Agent tool:\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \"src/components/**/*.tsx\"), grep for symbols or keywords (eg. \"API endpoints\"), or answer \"where is X defined / which files reference Y.\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \"quick\" for a single targeted lookup, \"medium\" for moderate exploration, or \"very thorough\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\n</system-reminder>\n\n<system-reminder>\nAs you answer the user's questions, you can use the following context:\n# currentDate\nToday's date is <FIXTURE-DATE>.\n\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\n</system-reminder>\n\n\nhi",
|
|
84
84
|
"permission_denials": []
|
|
85
85
|
}
|
|
86
86
|
}
|
|
@@ -67,7 +67,7 @@
|
|
|
67
67
|
"content": [
|
|
68
68
|
{
|
|
69
69
|
"type": "text",
|
|
70
|
-
"text": "echo: <system-reminder>\
|
|
70
|
+
"text": "echo: <system-reminder>\nAvailable agent types for the Agent tool:\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \"src/components/**/*.tsx\"), grep for symbols or keywords (eg. \"API endpoints\"), or answer \"where is X defined / which files reference Y.\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \"quick\" for a single targeted lookup, \"medium\" for moderate exploration, or \"very thorough\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\n</system-reminder>\n\n<system-reminder>\nAs you answer the user's questions, you can use the following context:\n# currentDate\nToday's date is <FIXTURE-DATE>.\n\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\n</system-reminder>\n\n\nfirst"
|
|
71
71
|
}
|
|
72
72
|
]
|
|
73
73
|
}
|
|
@@ -81,7 +81,7 @@
|
|
|
81
81
|
"type": "result",
|
|
82
82
|
"subtype": "success",
|
|
83
83
|
"is_error": false,
|
|
84
|
-
"result": "echo: <system-reminder>\
|
|
84
|
+
"result": "echo: <system-reminder>\nAvailable agent types for the Agent tool:\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \"src/components/**/*.tsx\"), grep for symbols or keywords (eg. \"API endpoints\"), or answer \"where is X defined / which files reference Y.\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \"quick\" for a single targeted lookup, \"medium\" for moderate exploration, or \"very thorough\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\n</system-reminder>\n\n<system-reminder>\nAs you answer the user's questions, you can use the following context:\n# currentDate\nToday's date is <FIXTURE-DATE>.\n\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\n</system-reminder>\n\n\nfirst",
|
|
85
85
|
"permission_denials": []
|
|
86
86
|
}
|
|
87
87
|
},
|
|
@@ -95,7 +95,7 @@
|
|
|
95
95
|
"content": [
|
|
96
96
|
{
|
|
97
97
|
"type": "text",
|
|
98
|
-
"text": "echo:
|
|
98
|
+
"text": "echo: second"
|
|
99
99
|
}
|
|
100
100
|
]
|
|
101
101
|
}
|
|
@@ -109,7 +109,7 @@
|
|
|
109
109
|
"type": "result",
|
|
110
110
|
"subtype": "success",
|
|
111
111
|
"is_error": false,
|
|
112
|
-
"result": "echo:
|
|
112
|
+
"result": "echo: second",
|
|
113
113
|
"permission_denials": []
|
|
114
114
|
}
|
|
115
115
|
}
|
|
@@ -67,7 +67,7 @@
|
|
|
67
67
|
"content": [
|
|
68
68
|
{
|
|
69
69
|
"type": "text",
|
|
70
|
-
"text": "echo: <system-reminder>\
|
|
70
|
+
"text": "echo: <system-reminder>\nAvailable agent types for the Agent tool:\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \"src/components/**/*.tsx\"), grep for symbols or keywords (eg. \"API endpoints\"), or answer \"where is X defined / which files reference Y.\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \"quick\" for a single targeted lookup, \"medium\" for moderate exploration, or \"very thorough\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\n</system-reminder>\n\n<system-reminder>\nAs you answer the user's questions, you can use the following context:\n# currentDate\nToday's date is <FIXTURE-DATE>.\n\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\n</system-reminder>\n\n\nhi"
|
|
71
71
|
}
|
|
72
72
|
]
|
|
73
73
|
}
|
|
@@ -81,7 +81,7 @@
|
|
|
81
81
|
"type": "result",
|
|
82
82
|
"subtype": "success",
|
|
83
83
|
"is_error": false,
|
|
84
|
-
"result": "echo: <system-reminder>\
|
|
84
|
+
"result": "echo: <system-reminder>\nAvailable agent types for the Agent tool:\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \"src/components/**/*.tsx\"), grep for symbols or keywords (eg. \"API endpoints\"), or answer \"where is X defined / which files reference Y.\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \"quick\" for a single targeted lookup, \"medium\" for moderate exploration, or \"very thorough\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\n\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\n</system-reminder>\n\n<system-reminder>\nAs you answer the user's questions, you can use the following context:\n# currentDate\nToday's date is <FIXTURE-DATE>.\n\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\n</system-reminder>\n\n\nhi",
|
|
85
85
|
"permission_denials": []
|
|
86
86
|
}
|
|
87
87
|
}
|
|
@@ -67,7 +67,7 @@
|
|
|
67
67
|
"content": [
|
|
68
68
|
{
|
|
69
69
|
"type": "text",
|
|
70
|
-
"text": "[{\"role\":\"user\",\"content\":\"<system-reminder>\\
|
|
70
|
+
"text": "[{\"role\":\"user\",\"content\":[{\"type\":\"text\",\"text\":\"<system-reminder>\\nAvailable agent types for the Agent tool:\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\"src/components/**/*.tsx\\\"), grep for symbols or keywords (eg. \\\"API endpoints\\\"), or answer \\\"where is X defined / which files reference Y.\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\"quick\\\" for a single targeted lookup, \\\"medium\\\" for moderate exploration, or \\\"very thorough\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\n</system-reminder>\\n\"},{\"type\":\"text\",\"text\":\"<system-reminder>\\nAs you answer the user's questions, you can use the following context:\\n# currentDate\\nToday's date is <FIXTURE-DATE>.\\n\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\n</system-reminder>\\n\\n\"},{\"type\":\"text\",\"text\":\"first\"}]}]"
|
|
71
71
|
}
|
|
72
72
|
]
|
|
73
73
|
}
|
|
@@ -81,7 +81,7 @@
|
|
|
81
81
|
"type": "result",
|
|
82
82
|
"subtype": "success",
|
|
83
83
|
"is_error": false,
|
|
84
|
-
"result": "[{\"role\":\"user\",\"content\":\"<system-reminder>\\
|
|
84
|
+
"result": "[{\"role\":\"user\",\"content\":[{\"type\":\"text\",\"text\":\"<system-reminder>\\nAvailable agent types for the Agent tool:\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\"src/components/**/*.tsx\\\"), grep for symbols or keywords (eg. \\\"API endpoints\\\"), or answer \\\"where is X defined / which files reference Y.\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\"quick\\\" for a single targeted lookup, \\\"medium\\\" for moderate exploration, or \\\"very thorough\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\n</system-reminder>\\n\"},{\"type\":\"text\",\"text\":\"<system-reminder>\\nAs you answer the user's questions, you can use the following context:\\n# currentDate\\nToday's date is <FIXTURE-DATE>.\\n\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\n</system-reminder>\\n\\n\"},{\"type\":\"text\",\"text\":\"first\"}]}]",
|
|
85
85
|
"permission_denials": []
|
|
86
86
|
}
|
|
87
87
|
},
|
|
@@ -153,7 +153,7 @@
|
|
|
153
153
|
"content": [
|
|
154
154
|
{
|
|
155
155
|
"type": "text",
|
|
156
|
-
"text": "[{\"role\":\"user\",\"content\"
|
|
156
|
+
"text": "[{\"role\":\"user\",\"content\":[{\"type\":\"text\",\"text\":\"<system-reminder>\\nAvailable agent types for the Agent tool:\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\"src/components/**/*.tsx\\\"), grep for symbols or keywords (eg. \\\"API endpoints\\\"), or answer \\\"where is X defined / which files reference Y.\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\"quick\\\" for a single targeted lookup, \\\"medium\\\" for moderate exploration, or \\\"very thorough\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\n</system-reminder>\\n\"},{\"type\":\"text\",\"text\":\"<system-reminder>\\nAs you answer the user's questions, you can use the following context:\\n# currentDate\\nToday's date is <FIXTURE-DATE>.\\n\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\n</system-reminder>\\n\\n\"},{\"type\":\"text\",\"text\":\"first\"}]},{\"role\":\"assistant\",\"content\":\"[{\\\"role\\\":\\\"user\\\",\\\"content\\\":[{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"<system-reminder>\\\\nAvailable agent types for the Agent tool:\\\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\\\\\"src/components/**/*.tsx\\\\\\\"), grep for symbols or keywords (eg. \\\\\\\"API endpoints\\\\\\\"), or answer \\\\\\\"where is X defined / which files reference Y.\\\\\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\\\\\"quick\\\\\\\" for a single targeted lookup, \\\\\\\"medium\\\\\\\" for moderate exploration, or \\\\\\\"very thorough\\\\\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\\\n\\\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\\\n</system-reminder>\\\\n\\\"},{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"<system-reminder>\\\\nAs you answer the user's questions, you can use the following context:\\\\n# currentDate\\\\nToday's date is <FIXTURE-DATE>.\\\\n\\\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\\\n</system-reminder>\\\\n\\\\n\\\"},{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"first\\\"}]}]\"},{\"role\":\"user\",\"content\":\"second\"}]"
|
|
157
157
|
}
|
|
158
158
|
]
|
|
159
159
|
}
|
|
@@ -167,7 +167,7 @@
|
|
|
167
167
|
"type": "result",
|
|
168
168
|
"subtype": "success",
|
|
169
169
|
"is_error": false,
|
|
170
|
-
"result": "[{\"role\":\"user\",\"content\"
|
|
170
|
+
"result": "[{\"role\":\"user\",\"content\":[{\"type\":\"text\",\"text\":\"<system-reminder>\\nAvailable agent types for the Agent tool:\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\"src/components/**/*.tsx\\\"), grep for symbols or keywords (eg. \\\"API endpoints\\\"), or answer \\\"where is X defined / which files reference Y.\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\"quick\\\" for a single targeted lookup, \\\"medium\\\" for moderate exploration, or \\\"very thorough\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\n\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\n</system-reminder>\\n\"},{\"type\":\"text\",\"text\":\"<system-reminder>\\nAs you answer the user's questions, you can use the following context:\\n# currentDate\\nToday's date is <FIXTURE-DATE>.\\n\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\n</system-reminder>\\n\\n\"},{\"type\":\"text\",\"text\":\"first\"}]},{\"role\":\"assistant\",\"content\":\"[{\\\"role\\\":\\\"user\\\",\\\"content\\\":[{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"<system-reminder>\\\\nAvailable agent types for the Agent tool:\\\\n- claude: Catch-all for any task that doesn't fit a more specific agent. (Tools: *)\\\\n- Explore: Fast read-only search agent for locating code. Use it to find files by pattern (eg. \\\\\\\"src/components/**/*.tsx\\\\\\\"), grep for symbols or keywords (eg. \\\\\\\"API endpoints\\\\\\\"), or answer \\\\\\\"where is X defined / which files reference Y.\\\\\\\" Do NOT use it for code review, design-doc auditing, cross-file consistency checks, or open-ended analysis — it reads excerpts rather than whole files and will miss content past its read window. When calling, specify search breadth: \\\\\\\"quick\\\\\\\" for a single targeted lookup, \\\\\\\"medium\\\\\\\" for moderate exploration, or \\\\\\\"very thorough\\\\\\\" to search across multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\\\n- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)\\\\n- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)\\\\n\\\\nWhen you launch multiple agents for independent work, send them in a single message with multiple tool uses so they run concurrently.\\\\n</system-reminder>\\\\n\\\"},{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"<system-reminder>\\\\nAs you answer the user's questions, you can use the following context:\\\\n# currentDate\\\\nToday's date is <FIXTURE-DATE>.\\\\n\\\\n IMPORTANT: this context may or may not be relevant to your tasks. You should not respond to this context unless it is highly relevant to your task.\\\\n</system-reminder>\\\\n\\\\n\\\"},{\\\"type\\\":\\\"text\\\",\\\"text\\\":\\\"first\\\"}]}]\"},{\"role\":\"user\",\"content\":\"second\"}]",
|
|
171
171
|
"permission_denials": []
|
|
172
172
|
}
|
|
173
173
|
}
|