Create and run your first project

Project definition

A project in Kaidera OS is a stable project key, display name, workspace root, worker roster, settings, and Cortex memory namespace. The project key is used by worker identity, handoff routing, and memory lookup, so choose it carefully.

Register the project

Use the Add Project flow in the console. Provide a stable project key, a human-readable name, and the absolute path to the project workspace. The root should be the folder where the worker harnesses should run.

• Use lowercase, stable project keys where possible.
• Use an absolute workspace path.
• Avoid renaming project keys after work has begun.
• Confirm the Dashboard shows the selected project and workspace root.

Set the workspace root

The workspace root controls where workers run, where file paths resolve, and what local project material can be inspected. A wrong root leads to empty graphs, missing explanations, or workers operating in the wrong folder.

Add the first lead worker

Add an interactive lead first. This worker is the operator-facing role you use to discuss the project, shape goals, and review proposed work. Configure its role, provider, model, and reasoning level before adding more workers.

Add execution workers

After the lead worker is healthy, add workers for execution. Typical roles include product, engineering, knowledge, design, QA, operations, and deterministic jobs. Keep roles clear so handoffs route to the right owner.

Start in propose mode

A new project should start with propose mode enabled. In propose mode, work queues for operator review instead of launching automatically. Use manual approval until the roster, provider configuration, and workspace boundary are trusted.

Readiness checklist

Before allowing broader autonomy, confirm the project root is correct, Cortex reads are healthy, the app database is connected, workers have the intended harness and model, and at least one successful run has produced evidence for review.