Skip to content

AGENTS.md

Latest commit

 

History

History
78 lines (61 loc) · 2.61 KB

AGENTS.md

File metadata and controls

78 lines (61 loc) · 2.61 KB
Raw

Agent Instructions

This project uses Mote for issue tracking and path coordination. Do not use Beads for new work.

Quick Reference

mote doctor
mote ready
mote show <id>
mote preflight --issue <id> --paths <path> [<path> ...]
mote begin <id> --paths <path> [<path> ...]
mote note <id> --kind progress "what changed"
mote done <id> --note "finished"

Non-Interactive Shell Commands

ALWAYS use non-interactive flags with file operations to avoid hanging on confirmation prompts.

Shell commands like cp, mv, and rm may be aliased to include -i (interactive) mode on some systems, causing the agent to hang indefinitely waiting for y/n input.

Use these forms instead:

# Force overwrite without prompting
cp -f source dest           # NOT: cp source dest
mv -f source dest           # NOT: mv source dest
rm -f file                  # NOT: rm file

# For recursive operations
rm -rf directory            # NOT: rm -r directory
cp -rf source dest          # NOT: cp -r source dest

Other commands that may prompt:

  • scp - use -o BatchMode=yes for non-interactive
  • ssh - use -o BatchMode=yes to fail instead of prompting
  • apt-get - use -y flag
  • brew - use HOMEBREW_NO_AUTO_UPDATE=1 env var

Mote Issue Tracker

Rules

  • Use mote for all task tracking and path reservations.
  • Run mote doctor, open a named session, and inspect mote in-flight before claiming work.
  • Never hand-edit .mote/ops/*.json; Mote operations are the durable record.
  • Reserve exact paths before editing and stage only the operations belonging to the current issue.
  • Do not use TodoWrite, TaskCreate, markdown TODO lists, or Beads as parallel trackers.

Session Completion

When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.

MANDATORY WORKFLOW:

  1. File Mote issues for remaining work - Create issues for anything that needs follow-up
  2. Run quality gates (if code changed) - Tests, linters, builds
  3. Update Mote status - Finish completed work or hand off unfinished work
  4. PUSH TO REMOTE - This is MANDATORY: 
    git pull --rebase
git push
git status  # MUST show "up to date with origin"
  5. Clean up - Clear stashes, prune remote branches
  6. Verify - All changes committed AND pushed
  7. Hand off - Provide context for next session

CRITICAL RULES:

  • Work is NOT complete until git push succeeds
  • NEVER stop before pushing - that leaves work stranded locally
  • NEVER say "ready to push when you are" - YOU must push
  • If push fails, resolve and retry until it succeeds