Operator console

The operator console is the daily-use face of Ódinn Forge. Start it with:

odinn start

The single-user console is available at http://127.0.0.1:18790/. Loading the home page establishes an authenticated, HttpOnly browser session with the local gateway.

Core workspace

• Chat is where you work with the configured model.
• Projects group related conversations and goals.
• Sessions preserve durable conversation history.
• Goals keep outcomes visible and scoped.
• Memory presents suggested and active durable context.
• Cron Jobs schedule registered tools while the gateway is running.
• Tasks shows meaningful user, agent, and automation work.
• Activity combines an operational overview with searchable history.
• Automatic improvements explains the bounded reliability loop and its restore points.

Agent SDK and Skills SDK pages let you inspect and manage package metadata. Registration does not execute or trust a package.

Labs

The collapsible Labs group contains seven separate experimental pages. Each offers a guided workflow, while contract-shaped input and endpoint details remain under advanced disclosure. Every Lab is off until you deliberately enable its feature flag.

Automatic improvements is not one of the seven Labs. It is a separate bounded feature that starts enabled by default.

Authentication boundary

The browser uses a same-site bootstrap cookie. Cookie-authenticated changes require an exact matching origin. Scripts must use the owner-only gateway bearer token; do not copy that token into documentation, bug reports, shell history, or source control.

Remote access

Never expose the single-user gateway directly to a network. Remote operation uses the dedicated TLS multi-user host, which provisions a separate application state and workspace boundary per user. Read Remote hosting before deploying it.

If the console will not start, run odinn doctor and see Troubleshooting.