Projects, sessions, and goals

Ódinn separates three ideas that ordinary chat tools often collapse together:

• A project groups related work.
• A session is a durable conversation.
• A goal is an outcome with a lifecycle.

This makes it possible to return to work without treating one endless chat as the entire filing system.

Projects

Create projects for durable areas of work: a product launch, a research topic, a home renovation, or a client engagement. Sessions default to the built-in Workspace project and can be reassigned in the console.

Use project scope when several conversations and goals should share the same accepted memory.

Sessions

A session stores the conversation and its provenance. You can create, rename, read, list, and delete sessions.

odinn session create --title "Launch planning"
odinn session list

Use the console for normal conversation. The CLI is useful for inspection and automation:

odinn session read --session <session-id>
odinn session rename --session <session-id> --title "July launch"

Deleting a session is an explicit action. Back up state first if the conversation matters.

Goals

Goals belong to a project or a specific session. A session-scoped goal also inherits the session’s project.

odinn goal create --title "Ship the public landing page"
odinn goal list

Update a goal when its state changes:

odinn goal update --goal <goal-id> --status completed --note "Published and verified"

Supported lifecycle states are active, completed, blocked, paused, and cancelled.

A practical pattern

Create one project for a durable outcome, open focused sessions for distinct workstreams, and use goals for observable completion. Keep only reusable decisions and preferences in Memory; conversation history can carry the rest.