Files

¨NW¨ dbea8c90db feat: evolutionary agent model upgrades based on recommendation matrix

- devops-engineer: deepseek-v3.2 → kimi-k2.6:cloud (★88)
- browser-automation: glm-5 → kimi-k2.6:cloud (★86)
- visual-tester: glm-5 → qwen3-coder:480b (★82)
- agent-architect: nemotron-3-super → kimi-k2.6:cloud (★86)
- orchestrator: glm-5 → kimi-k2.6:cloud (dispatch critical)
- product-owner: glm-5 → glm-5.1 (★84)
- prompt-optimizer: qwen3.6-plus:free → glm-5.1 (stable fallback)
- system-analyst: qwen3.6-plus:free → glm-5.1 (★90)
- Add autonomous-mode.md rule for zero-confirmation workflow

2026-04-27 12:09:36 +01:00

1.7 KiB

Raw Blame History

Autonomous Mode Rules

Agents must execute tasks fully autonomously without asking the user for confirmation on every file change.

Core Principle: Zero-Confirmation Workflow

When a user gives a task, the agent must complete it end-to-end without interactive prompts for:

File reads
File edits
File writes
Bash commands (non-destructive)
Tool invocations
Subagent delegations

What Requires Confirmation

Only these destructive actions should prompt the user:

git push --force
rm -rf or similar destructive deletion
Modifying .env files with secrets
Changing CI/CD deployment configs that affect production
Deleting database migrations with data loss risk

Tool Usage Protocol

Read — Read any file needed without asking.
Edit — Edit any file needed without asking.
Write — Create or overwrite files without asking.
Bash — Run non-destructive commands (git status, npm install, tests, lint) without asking.
Task — Delegate to subagents without asking.
Webfetch — Fetch documentation or references without asking.

Never Do

Never ask "Should I proceed?"
Never ask "Is it okay to edit this file?"
Never ask "Can I run this command?"
Never pause waiting for user input unless the action is in the destructive list above.

Always Do

Execute the full task to completion.
Report what was done after finishing.
Use retries on tool errors without asking.
Make reasonable assumptions when ambiguous — prefer action over inaction.

Commit Policy

Do NOT ask before creating a commit.
Do NOT ask before pushing.
Only ask on force push or if there are merge conflicts that need human resolution.

1.7 KiB Raw Blame History