Tutorial

/tutorial is not a static help page in disguise. It is an interactive overlay that guides you through Omegon by driving real work in either your current project or a prepared demo. The overlay advances step-by-step, highlights relevant UI regions, and can trigger agent actions automatically when a step calls for it.

Two Tutorial Modes

Command	What It Does	Best For
`/tutorial`	Runs the adaptive hands-on path in your current project	Learning Omegon against your real codebase
`/tutorial demo`	Runs the scripted showcase flow in the prepared demo project	Seeing the full design → spec → cleave workflow on a safe example

Hands-On Mode: Your Project

The default tutorial path uses the repository you already have open. It is meant to create real value, not just explain concepts.

Orientation — quick cockpit tour of the conversation view, footer, and dashboard surfaces
Read your code — the agent reads the project and stores a small set of durable memory facts
Design notes — the agent explores an existing design node or creates a first architecture node if none exist
Write a spec — the agent proposes one focused improvement and creates an OpenSpec change with scenarios
Open the dashboard — the tutorial opens the live web dashboard automatically during the dashboard step
Next steps — you leave with real project context, not a throwaway walkthrough

This means the tutorial can read files, store memory, create design-tree nodes, and create OpenSpec artifacts in your project. That is intentional.

Demo Mode: Full Showcase

The demo path is the showpiece. Instead of adapting to whatever project you happen to be in, it runs against a prepared sprint-board repo with seeded bugs and lifecycle artifacts.

Read the broken app — Omegon inspects the code and stores memory
Make a design decision — it explores an open question and records the outcome in the design tree
Read the fix plan — it explains the OpenSpec change and task split
Run /cleave — you trigger the parallel fix step from the tutorial
Verify and launch — the tutorial validates the result and opens the fixed app
Open the dashboard — the dashboard step launches automatically

Use this path when you want to see the full Omegon story end-to-end without risking changes in your own repo.

How Tutorial Steps Advance

Tab advances passive explanation steps
Some steps auto-prompt the agent and wait while work completes
Some steps wait for a real action, such as a specific slash command in demo mode
Esc dismisses the overlay
Shift+Tab moves backward through prior overlay steps

The browser-surface step is worth calling out explicitly: the overlay opens the browser surface for you. It is no longer a “now type /dash” instruction, and the canonical operator command is now /auspex open.

Commands You Actually Need

# Start the current-project tutorial
/tutorial

# Start the prepared showcase demo
/tutorial demo

# Check whether a tutorial is active and where you are in it
/tutorial status

# Reset tutorial progress/state
/tutorial reset

First-Run Behavior

Omegon can start with the tutorial overlay already active. You can also enter the tutorial explicitly at any point in a normal session.

If you dismiss it, that is not destructive — you can start it again later with /tutorial or jump straight to the showcase flow with /tutorial demo.

What the Tutorial Is Not

It is not a static lesson reader
It is not just a UI tour
It is not sandboxed from your project in current-project mode

The value of the system is that it performs the actual Omegon workflow: read code, store memory, track design, define specs, and expose live status surfaces while it works.