Ottili Coder runs on your machine through the Coder CLI or the native desktop app. Both share the same account, run queue, and audit trail.
Before you start
You need an Ottili account with Coder enabled. Coder is authenticated through your Ottili identity ("Sign in with Ottili"), so there is no separate Coder password to manage.
Install the desktop app
1. Open the Coder surface from Ottili ONE or your dashboard.
2. Download the desktop app for your platform.
3. Install it like any other desktop application.
4. Launch it and choose Sign in with Ottili*.
The desktop app bundles the local runtime, so you can start local runs without a separate CLI install.
Install the CLI
If you prefer a terminal-driven workflow, the Ottili Coder CLI* drives missions through the unified ottili developer CLI (the coder command group). For a step-by-step guide with installation, authentication via environment variables (OTTILI_WORKSPACE_SLUG, OTTILI_API_TOKEN) and verification, see [Installing the Ottili Coder CLI](/docs/cli-installation). There is no separate login command — the connection is configured against the Unified API.
Verify your environment
Before the first run, check that your machine meets the runner requirements:
ottili doctorThe doctor command of the unified ottili CLI checks, among other things:
- Git is available with read/write access to your repository.
- A runtime is present (the desktop app or a container runtime such as Docker).
- Node.js and Python are available for the runtimes Coder drives.
- Network access to Ottili for auth, queue sync, credits, and audit.
- Optional provider credentials and MCP servers for the task.
Fix any item the doctor command flags, then start your first mission.
Next steps
- Learn how a [mission](/docs/coder-missions) becomes a run.
- Understand [local, cloud, and hybrid runs](/docs/coder-local-cloud-hybrid-runs).
Was this article helpful?
