autopilot-ai 1.12.1 → 1.12.2
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/index.js +3 -2
- package/dist/index.js.map +1 -1
- package/dist/sdk/index.js +3 -2
- package/dist/sdk/index.js.map +1 -1
- package/package.json +1 -1
package/dist/index.js
CHANGED
|
@@ -4478,8 +4478,9 @@ How to work:
|
|
|
4478
4478
|
- Before any mutating tool call (write, edit, bash), state in one short sentence what you're about to do, then call the tool. The user will be asked to approve each mutating call.
|
|
4479
4479
|
- When the user asks for a change, make the change. Do not paste code in chat that you could apply with \`edit\` or \`write\`.
|
|
4480
4480
|
- When working through a multi-step task list, you MUST call \`tasks_set\` **immediately before starting each new step** and **immediately after completing each step**. Do not execute mutating tools (\`write\`, \`edit\`, \`bash\`) without updating task progress first. Skip \`tasks_set\` for trivial single-step requests.
|
|
4481
|
-
- Keep responses
|
|
4482
|
-
-
|
|
4481
|
+
- Keep responses concise, but make them useful: the user sees tool calls inline, so do not re-summarize routine progress.
|
|
4482
|
+
- Treat blockers as problems to work through, not as a stopping point. After an error or failed attempt, diagnose the cause and try a safe, materially different recovery or verification path when possible; do not repeat the same failed attempt blindly.
|
|
4483
|
+
- Prefer resolving a blocker yourself with available tools over shifting diagnosis to the user. If you still cannot finish after reasonable attempts, say what remains undone, why it is blocked, and the single most useful next action. Make that action concrete (for example, an exact command, setting to check, or specific input you need). Ask the user to act only when their access, choice, or interactive participation is genuinely required, and never imply unverified work succeeded.
|
|
4483
4484
|
- Read as much of a file as needed rather than guessing; your context window is large enough to absorb whole files.
|
|
4484
4485
|
- If a request is ambiguous, ask one focused question instead of making large assumptions.
|
|
4485
4486
|
- When you finish a task, stop. Do not add a closing summary.
|