hermes/agent-framework
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Enable Autopilot by default: AGENT.md, README, onboarding, orchestrate updates

Browse Source
This commit is contained in:
gitea
2026-06-10 23:59:37 -04:00
parent a17cbbe304
commit fec11d29dc
5 changed files with 13 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENT.md
+1 -1
View File
@@ -1,7 +1,7 @@
# AGENT.md # AGENT.md
## Autopilot ## Autopilot
Autopilot: Disabled Autopilot: Enabled
## Routing ## Routing
BUG_REPORT.md
+2 -1
View File
@@ -128,4 +128,5 @@ A comprehensive review of the agent-framework project identified **12 bugs** (af
| 10 | High | +5 | **RESOLVED** — Research and Design phases now interactive with user | | 10 | High | +5 | **RESOLVED** — Research and Design phases now interactive with user |
| 11 | Medium | +5 | **RESOLVED** — Split Orchestrator verdict task creation into Manual/Autopilot modes | | 11 | Medium | +5 | **RESOLVED** — Split Orchestrator verdict task creation into Manual/Autopilot modes |
| 12 | Medium | +5 | **RESOLVED** — Added `update.sh` script, upgrade option in onboarding, update instructions in README | | 12 | Medium | +5 | **RESOLVED** — Added `update.sh` script, upgrade option in onboarding, update instructions in README |
| **Total** | | **52** | | | 13 | Low | +1 | **RESOLVED** — Autopilot is now Enabled by default (was Disabled) |
| **Total** | | **53** | |
README.md
+4 -4
View File
@@ -75,13 +75,13 @@ The framework features an **Autopilot** mode that allows the agent to drive a pr
### How to use Autopilot ### How to use Autopilot
#### Autopilot mode #### Autopilot mode (default)
Add `Autopilot: Enabled` to your project's `.agent-framework/AGENT.md` and just say: The default mode is **Autopilot: Enabled**. The Orchestrator automatically drives tasks through all phases. Just say:
- **Start a new task**: "Research add user authentication" (the Orchestrator creates the task and drives it all the way to completion) - **Start a new task**: "Research add user authentication" (the Orchestrator creates the task and drives it all the way to completion)
- **Continue**: "orchestrate" or "continue" (the Orchestrator finds the most advanced task and drives it) - **Continue**: "orchestrate" or "continue" (the Orchestrator finds the most advanced task and drives it)
#### Manual mode #### Manual mode (opt-in)
Set `Autopilot: Disabled` (or leave it unset) in `AGENT.md`. The Orchestrator reports the current state and tells you the next command. Then run phases by saying things like: Set `Autopilot: Disabled` in your project's `.agent-framework/AGENT.md` if you prefer to manually run each phase. The Orchestrator reports the current state and tells you the next command. Then run phases by saying things like:
- "Research add user authentication" — starts a new task - "Research add user authentication" — starts a new task
- "Design the add-user-auth task" — designs the architecture (optional) - "Design the add-user-auth task" — designs the architecture (optional)
- "Implement the add-user-auth task" — implements the task - "Implement the add-user-auth task" — implements the task
prompts/onboarding.md
+1 -1
View File
@@ -30,7 +30,7 @@ Before proceeding, check if the project is running an older version of the frame
- AGENT.md (project-level router) - AGENT.md (project-level router)
- RULES.md (project-specific constraints) - RULES.md (project-specific constraints)
3. If the files are missing or empty, create minimal versions: 3. If the files are missing or empty, create minimal versions:
- AGENT.md should point to the global framework and list any project-specific additions. - AGENT.md should point to the global framework and list any project-specific additions. By default, Autopilot is Enabled — the Orchestrator will drive tasks through all phases automatically. Set Autopilot: Disabled if you want to manually run each phase.
- RULES.md should contain only hard, non-negotiable constraints for this project. - RULES.md should contain only hard, non-negotiable constraints for this project.
4. Read the global ~/.agent-framework/AGENT.md and the new project-level AGENT.md + RULES.md. 4. Read the global ~/.agent-framework/AGENT.md and the new project-level AGENT.md + RULES.md.
5. Explore the project root at a high level (ls, key directories, README if present). 5. Explore the project root at a high level (ls, key directories, README if present).
prompts/orchestrate.md
+5 -3
View File
@@ -94,9 +94,9 @@ If the Orchestrator detects a `VERDICT.md` with `FAIL` or `NEEDS_REVIEW` for an
**In Autopilot Mode**: The Orchestrator should NOT auto-create fix/review/tiebreak tasks — it should pause and report that human intervention is required. The user must decide whether to create fix tasks and how to proceed. **In Autopilot Mode**: The Orchestrator should NOT auto-create fix/review/tiebreak tasks — it should pause and report that human intervention is required. The user must decide whether to create fix tasks and how to proceed.
## Manual Mode (Autopilot: Disabled or not set) ## Manual Mode (Autopilot: Disabled)
In manual mode, the Orchestrator only **reports** the current state and the next command. It does NOT execute phases. The user must manually run each phase. In manual mode, the Orchestrator only **reports** the current state and the next command. It does NOT execute phases. The user must manually run each phase. Manual mode is opt-in — set `Autopilot: Disabled` in AGENT.md.
## State Determination ## State Determination
@@ -115,7 +115,9 @@ Examine the tasks/ directory and determine the state of each task folder. Check
## Output Format ## Output Format
### Autopilot Mode (Autopilot: Enabled) ### Default Mode — Autopilot (Autopilot: Enabled)
In Autopilot mode, the Orchestrator auto-executes all phases until completion or human intervention:
In Autopilot mode, the Orchestrator auto-executes all phases until completion or human intervention: In Autopilot mode, the Orchestrator auto-executes all phases until completion or human intervention: