gitea
a1dcf09d67
The orchestrator only drove ONE task per invocation, then stopped with ORCHESTRATION_COMPLETE. User had to manually re-trigger for each task. Changes: - Added drive_all() outer loop that scans EVERY task and drives them all - Tasks needing user review are flagged; orchestrator continues to next - Only stops when ALL tasks are terminal or ALL remaining need user input - Output format now shows session summary (completed, awaiting review, blocked) - Session-starter references 'orchestrate' as primary command - Updated continue-from-existing to use drive_all()
968 B
968 B
Session Starter Template
Copy and paste this at the very beginning of every new agent session (before giving your actual task).
Read the following files in order, then wait for my instructions:
- ~/.automaton/.agent.md (global framework router)
- ~/.automaton/.rules.md (global framework rules)
- {project}/.automaton/.agent.md (project-level router, if it exists)
- {project}/.automaton/.rules.md (if it exists)
After reading these files, acknowledge with: ".agent.md and .rules.md loaded. Ready."
How to Use
- Start a fresh session with your agent.
- Paste the block above (replace
{project}with the actual path). - Then give your real request, for example:
- "orchestrate" — drive ALL remaining tasks to completion
- "What should we do next on this project?"
- "Implement the fix-alert-test task"
- "Onboard this project to the agent framework"
This guarantees the agent always follows the routing rules in .agent.md.