Product tour
Understand how Organizations, Projects, Agents, and runs fit together in mosoo.
mosoo runs a selected harness and model in a durable Session. Invoke it directly from a Project key, or save reusable configuration as an optional Agent preset.
The product model
| Resource | What it owns |
|---|---|
| Organization | Your account-level container. The current product is a single-owner experience; team roles and invitations are not available. |
| Project | The isolation boundary for Agents, files, configuration, and usage. A new account starts with a Default Project. |
| Agent | Optional saved runtime/model, instructions, Skills, MCP connections and Environment configuration. |
| Thread / Session | Admitted configuration, native conversation and isolated working files. Follow-up keeps the same ID. |
| Run | One execution inside a Thread. Runs produce events, logs, usage, and files. |
A typical workflow
- Open a Project and configure a model-provider account.
- Create a Project key and keep it on your backend.
- Select a harness, model and instructions, then create a Session directly.
- Send input and files; inspect outcomes, events, artifacts and usage.
- Continue related work with the same Session ID after idle time or reclamation.
- Save an Agent preset when you need reusable configuration; publishing is optional for v2.
Most configuration belongs to the active Project. Provider keys, MCP credentials, Skills, and Environments do not automatically cross Project boundaries.