Modes Comparison & Queue System
Detailed Mode Differences
| Feature | Chat Mode | Autonomy Mode | Work Mode |
|---|
| Interaction Type | Conversational | Goal-directed autonomous | Schedule-driven autonomous |
| Who Drives | User (you) | GENESIS (AI) | Both (you schedule, AI works) |
| Response Time | Immediate (seconds) | Extended (minutes to hours) | Extended (follows schedule) |
| Best For | Questions, quick tasks | Complex projects, research | Structured work with deadlines |
| Time Structure | None (ad-hoc) | Flexible until goal complete | Fixed timetable blocks |
| Queue Behavior | Messages queued, FIFO | Task queue with sub-tasks | Timetable-based execution |
| Rest Handling | N/A (interactive) | Auto-rests on high load | Follows rest/sleep schedule |
| Interruption | Easy — send new message | ⏸ STOP or ⏹ STOP ALL | ⏸ STOP, waits for block end |
The Queue System Explained
What is the Queue?
The queue is GENESIS's way of managing multiple requests. Since GENESIS can only do one thing at a time, incoming requests are placed in order and processed sequentially.
Chat Mode Queue
- You send message A → added to queue position 1
- GENESIS processes message A (Thinking → Executing → Response)
- Message B is now at position 1, GENESIS starts processing it
Queue Characteristics: First-in, first-out (FIFO) order. Messages are never skipped or reordered. Each message completes fully before the next starts.
Autonomy Mode Queue
- Goal is set (e.g., "Build a web scraper")
- GENESIS breaks the goal into sub-tasks: plan, research, code, test, document
- Each sub-task becomes a queue item
- GENESIS executes them one by one
Queue Characteristics: Sub-tasks are dynamically generated based on goal complexity. GENESIS can add, modify, or remove sub-tasks during execution.
Work Mode Queue
- Tasks are scheduled in the timetable with specific time slots
- When a time slot arrives, the task moves to "In Progress"
- GENESIS executes the task during that block
- Completed tasks move to the next column (Review or Complete)
Mode Switching
How to Switch Between Modes
- Chat → Autonomy: Click 🤖 AUTONOMY MODE button
- Autonomy → Chat: Click 💬 CHAT MODE button (current task may be interrupted)
- Any → Work: Click ⚡ WORK MODE button
Safe Mode Switching Tips
- From Chat to Autonomous: Always finish your current message exchange first
- From Autonomous to Chat: Use ⏸ STOP for graceful transition, or accept that the task will be interrupted
- From Any to Work: Set a goal before switching, otherwise GENESIS won't know what to work on
Troubleshooting Queue Issues
Queue Not Processing
Check state indicator — if "Halted" (red), GENESIS has stopped. Use ⏸ STOP to clear the queue, then restart.
Messages Appearing Out of Order
This shouldn't happen in Chat mode (FIFO guaranteed). In Autonomy/Work mode, sub-tasks may be reordered based on dependencies. Check the Full Log to see actual execution order.
Queue Growing Too Large
- In Chat: You're sending messages faster than GENESIS can process them — wait for completion
- In Autonomy: The goal may be too complex — break it into smaller goals
- Solution: Use ⏸ STOP to clear and reassess