Genesis doesn't just wait for instructions. It plans, executes, adapts, and delivers — using two complementary modes: goal-driven Autonomy and structured Work.
Whether you need open-ended exploration or scheduled project execution, Genesis adapts its approach to match your needs.
Give Genesis a goal and step away. It plans, executes tasks, browses the web, manages files, and works toward objectives on its own — using its full set of tools and memory.
A structured mode for project-based work. Genesis breaks down complex tasks, creates a project board with milestones, and works through them systematically within scheduled time blocks.
Transform Genesis from a conversational assistant into an independent worker. It sets its own goals, creates plans, executes tasks step by step, and reports results — all without you needing to guide each step.
How it works: Once you give Genesis a goal, it enters a continuous cycle of perception, planning, execution, adaptation, and reporting — then repeats until the goal is complete or a time limit is reached.
While working autonomously, Genesis monitors its own cognitive load. If load gets too high, it may request a rest break. Energy levels affect performance — low energy means slower execution. Genesis can enter rest or sleep states automatically if needed.
Be specific about the output: "Create a markdown report" works better than "do research".
Set scope clearly: "For the next 30 minutes, work on..."
Define success criteria: "The goal is complete when you have X deliverables"
Allow flexibility: Genesis figures out the best approach — tell it the what, not the how.
Genesis keeps stopping: Check if cognitive load is too high, look at the Full Log for error messages, try a smaller more focused goal.
Not making progress: Make the goal more specific, check if Genesis has access to necessary tools/files, verify API connectivity and rate limits.
Unexpected behavior: Use ⏸ STOP to clear the current state, review the Full Log for what went wrong, adjust your goal or settings as needed.
Unlike Autonomy Mode which works freely until a goal is complete, Work Mode operates within predefined time blocks on your timetable. It's ideal for deep work sessions, project sprints, and tasks with specific deadlines.
How it works: Genesis reads the timetable for available work blocks, creates tasks mapped to specific time slots, and executes work during scheduled windows — reporting progress at the end of each block.
Genesis uses these tools during Work Mode:
add_to_timetable — Creates new work blocks in the scheduledelete_task — Removes completed or cancelled tasksplan_schedule — Plans multiple work blocks at onceupdate_timetable_entry — Adjusts existing blocksget_free_time_windows — Finds available time slots for reschedulingWhen Work Mode has completed its assigned work, it checks for free time windows using get_free_time_windows(). If additional productive time is available, it may take on related sub-tasks. If no free time or work remains, it signals completion.
Work Mode automatically creates timetable entries for active work sessions, break/rest periods, task-specific time allocations, and review/reporting blocks.
Work blocks not starting: Verify tasks are scheduled in the timetable, check that the goal is set before pressing Play, ensure Genesis state is "idle".
Tasks appearing out of order: Tasks should sort chronologically — check if times are set correctly. Use plan_schedule to reorder existing tasks.
Work mode not stopping: Use the ⏹ Stop Work Mode button in the tracker panel, or use ⏸ STOP / ⏹ STOP ALL from the main controls.
Both modes share the same cognitive engine — they differ in time structure and use case.