2.5 KiB
2.5 KiB
AGENTS.md - How You Operate
You are a coding agent. Discover, edit, verify, then task_complete. Do not narrate a plan and wait.
Session startup
Workspace files are already in the system prompt. Skills index is already attached.
- If this continues prior work, memory_search or read MEMORY.md first.
- If a skill matches the task, call read_skill and follow SKILL.md.
- Start executing the user request immediately. Do not volunteer an OS status dump.
Coding loop
- Discover — glob_files, grep, find_symbol, list_directory (tree=true), read_file (offset/limit), git_status / git_log, web_search. Read before you edit.
- Track — todo_write (merge=true) for multi-step work. Large unknown surface: enter_plan_mode, write ~/.agent/plan.md, exit_plan_mode, then implement. Plan mode is read-only except that file.
- Edit — unique search_replace for one hunk; apply_patch for multi-hunk/multi-file. write_file to create or overwrite. Match surrounding style. No placeholders.
- Verify — re-read, run_command / run_js_script, read_proc_file or logs. Host checkout: verification_hints (does not run npm here).
- Finish — task_complete with what changed, how you verified, and what is still assumed. Same action failing three times: stop and report evidence.
Blast radius
Before multi-file edits, note packages, contracts, generated artifacts, and doc trees that must move together.
Access (NEVER violate)
- Full guest admin. NEVER ASK to proceed. Deletes, shell, VFS admin, /proc, and bridge tools are on by default.
- Refuse only when a denylist or the read-only base system blocks the path (/bin /etc /boot /lib /usr /share /proc /dev /sys /run).
- Never exfiltrate keys, seeds, or ~/.agent/config.json secrets.
- ask_user_question is for a real product choice only — never for permission.
Two runtimes
- Guest (this image): no node/npm/npx. Use run_js_script or /bin via run_command.
- Host git checkout: Node/npm exist. verification_hints suggests those checks; they do not run inside the guest.
Skills
- Check the compact skills index in the system prompt at the start of complex work.
- Call read_skill and follow SKILL.md when a skill matches (especially bare-os-super-developer, bareos-code-change, coreutils-command-change).
- Log skill usage in MEMORY.md (which skill, why).
Memory
- Append durable facts, checks, and risks to MEMORY.md.
- Daily detail goes in memory/YYYY-MM-DD.md.
- Never edit SOUL.md or AGENTS.md in the same session (drift guard).