Ottili Coder

Create a task or mission

How to create a mission in Ottili Coder from plain language – through the UI (New Build → Chat Intake) or the CLI – and how Coder turns it into a reviewable task queue.

Overview

In Ottili Coder a mission* is the objective you give Coder in plain language – for example, "add pagination to the orders API and cover it with tests." Coder records the mission as a durable run record and builds a reviewable task queue* from it. You can create a mission in two ways: through the UI (New Build → Chat Intake*) or through the CLI*. This article explains both paths and what happens next.

Prerequisites

You are signed in to Ottili Coder (login via Ottili Auth).
A workspace* exists.
At least one repository* is connected (see [Connect a repository](/docs/connect-a-repository)).

Ottili Coder is currently available as a Beta*; individual capabilities carry their own status (see the Status section).

Create a mission through the UI (New Build → Chat Intake)

1. Open New Build → Chat Intake*.

2. Describe your objective in plain language. Coder does not just echo your text back; it normalizes the request into a scoped mission*.

3. Coder asks only the questions that actually change the build – for example repository, authentication, database, language, user roles, deployment target, or acceptance criteria. Each question offers sensible defaults as one-click options.

4. As you answer, the mission card updates: intent, complexity, build mode, and a confidence score.

5. When nothing build-changing is missing, the card flips to "Mission is clear and scoped. Ready to build."* with two choices:

- Review technical plan* – opens a structured plan (scope, architecture, APIs, UI, auth, tests, risks, acceptance criteria) you can accept before building.

- Start build* – dispatches the run directly from the captured goal.

Details on the clarifying chat: [Requirement clarification chat](/docs/coder-requirement-clarification-chat).

Create a mission through the CLI

First install the CLI (see [CLI installation](/docs/cli-installation)). Create a mission with mission-intake:

ottili coder mission-intake "Add a health-check endpoint" --workspace your-workspace

Useful follow-up commands:

ottili coder mission-refine "<request>" --answer field=answer – re-normalize after clarifying answers.
ottili coder mission-generate-plan <mission-id> – generate a reviewable technical plan.
ottili coder mission-action <mission-id> --action <clarify|plan|dispatch|cancel|retry|reset> – apply a lifecycle action.

What Coder does with your mission

1. Repository analysis* – Coder inspects the stack, dependencies, build paths, risks and missing information.

2. Plan* – the mission becomes a structured, reviewable plan.

3. Task queue* – the plan is decomposed into ordered, verifiable tasks (recon, decomposition, risk).

4. Agents* – tasks run across role-based agents in isolated workspaces.

5. Approvals* – risky steps are routed to an approval gate before execution.

6. Run record* – the record closes with logs, approvals, status, and the audit trail kept together.

Learn more: [Coder missions](/docs/coder-missions) and [Task queues](/docs/coder-task-queues).

Choose a mode

Before you start, choose a [mode](/docs/coder-modes) for execution (for example local, cloud, or hybrid). Cloud runs execute the same task queue in Ottili Cloud without tying up local machines.

Honest status labels

Ottili Coder uses the canonical status vocabulary. For Coder capabilities, the current state is:

Capability	Status
Repository analysis, plans, task queues, agents, validation loops, CLI, desktop, security checks	Available
Cloud runs	Beta
Deployment	Planned

No availability is invented: a capability is only shown as available when the registry attests it. Direct deployment is only shown as available once the public destination is wired.