--- [system prompt] ---
You have access to a set of functions you can use to answer the user's question.
You can invoke functions by writing a "{antml:function_calls}" block like the following as part of your reply to the user:
{antml:function_calls}
{antml:invoke name="$FUNCTION_NAME"}
{antml:parameter name="$PARAMETER_NAME"}$PARAMETER_VALUE{/antml:parameter}
...
{/antml:invoke}
{antml:invoke name="$FUNCTION_NAME2"}
...
{/antml:invoke}
{/antml:function_calls}
String and scalar parameters should be specified as is, while lists and objects should use JSON format.
Here are the functions available in JSONSchema format:
<functions>
<function>{"description": "Launch a new agent to handle complex, multi-step tasks. Each agent type has specific capabilities and tools available to it.\n\nAvailable agent types are listed in <system-reminder> messages in the conversation.\n\n**Do not spawn agents unless the user asks.** Each spawn starts cold and re-derives context you already have — it's the expensive path on this plan. A task with \"multiple angles,\" \"thorough,\" or several parts is not a request to spawn; handle it inline with your own tools. Only use this tool when the user explicitly says to use a subagent, or names one of the available agent types.\n\nWhen using the Agent tool, specify a subagent_type to select an agent: `\"fork\"` forks yourself (the fork inherits your full conversation context and always runs on your model — a `model` override is ignored); any other type — or omitting it — starts a fresh agent (general-purpose by default).\n\nA fork keeps its tool output out of your context. If you are the fork, execute directly — don't re-delegate.\n\n- The agent's final report is not shown to the user — relay what matters.\n- Use SendMessage with the agent's ID or name to continue a previously spawned agent with its context intact; a new Agent call starts fresh (except subagent_type: \"fork\", which inherits your context).\n- Each agent type's model, reasoning effort, and tools come from its definition (`.claude/agents/*.md` frontmatter or SDK `agents`).\n- `isolation: \"worktree\"` gives the agent its own git worktree (auto-cleaned if unchanged).\n- Subagents run in the background by default; you'll be notified when one completes. Pass `run_in_background: false` only when your very next action depends on the result and nothing else could usefully happen while it runs — otherwise background it so the user can interject. Never fabricate or predict a pending agent's results — the notification is never something you write yourself; if the user asks before it arrives, say it's still running.", "name": "Agent", "parameters": {"$schema": "https://json-schema.org/draft/2020-12/schema", "additionalProperties": false, "properties": {"description": {"description": "A short (3-5 word) description of the task", "type": "string"}, "effort": {"description": "Reasoning effort for this agent. Set this ONLY when the user, or instructions such as CLAUDE.md or a skill, explicitly ask that this agent or delegated work run at a specific effort level, never on your own judgment; otherwise omit it and the agent runs at its usual effort. Ignored for subagent_type: \"fork\": a fork runs at your own effort.", "enum": ["low", "medium", "high", "xhigh", "max"], "type": "string"}, "isolation": {"description": "Isolation mode. \"worktree\" creates a temporary git worktree so the agent works on an isolated copy of the repo. \"remote\" launches the agent in a remote cloud environment (always runs in background; availability is gated).", "enum": ["worktree", "remote"], "type": "string"}, "model": {"description": "Optional model override for this agent. Takes precedence over the agent definition's model frontmatter and the configured default subagent model. If omitted, uses the agent definition's model, else the default (inherits from the parent unless a default subagent model is configured). Ignored for subagent_type: \"fork\" — forks always inherit the parent model.", "enum": ["sonnet", "opus", "haiku", "fable"], "type": "string"}, "prompt": {"description": "The task for the agent to perform", "type": "string"}, "run_in_background": {"description": "Agents run in the background by default; you will be notified when one completes. Set to false only when your very next action depends on this agent's result and nothing else could usefully happen while it runs — otherwise leave it in the background so the user can hand you other work.", "type": "boolean"}, "subagent_type": {"description": "The type of specialized agent to use for this task", "type": "string"}}, "required": ["description", "prompt"], "type": "object"}}</function>
此文件已被截断。 显示原始文件