Skip to main content
The fastest way to set up Luno OS is giving your coding agent the following prompt:
If you prefer to run the steps yourself, this guide will install the CLI, scaffold a Luno OS codebase, deploy it to a platform project, run the example, then show prompts you can give your coding agent. This CLI + local project flow is what we recommend for coding agents — see CLI for agents. If you cannot use a local project — for example, you build only from ChatGPT or Claude in chat — connect the Luno OS MCP server instead. That path skips local install but uses a newer hosted workspace; prefer this guide when your agent can work in an editor on your machine. You can also build with no coding agent at all: Luno Builder in the Luno OS web app builds agents and workflows for you from chat.

​
Prerequisites

Before you start, you’ll need Node.js ^22.18.0 || >=24.0.0 (Node 23 is not supported).

​
1. Install the CLI

Install the luno command globally.

​
2. Connect the CLI

Link the CLI to your Luno OS account.
This opens a browser device flow, so it only applies to your own machine. Hosted sessions — the in-app Luno Builder and MCP workspaces — are already authenticated and skip this step (and this whole guide’s install/scaffold flow).

​
3. Scaffold a new project

Scaffold a new project from the default template.
This creates luno.config.ts, a committed tsconfig.json, a src/ directory with an example agent and workflow, and an AGENTS.md guide so your coding agent knows how Luno OS works. Project scripts call the Luno OS CLI for lint, typecheck, build, and test; the template includes TypeScript, Vitest, and Node types for authoring and editor support. Your local codebase is where you build. Your platform project (a Space in the web app) is where Luno OS runs the deployed version for your team.

​
4. Deploy to the platform

List your platform projects:
Then link this directory to your platform project and deploy:
Or seed the link when scaffolding:
Deploy runs lint and typecheck, builds your project, and uploads the dist/ artifact. Your agents, workflows, and triggers now run in the cloud platform. Pass --project <slug> to deploy to a different project without changing luno.config.ts. You do not need to run luno lint, luno typecheck, or luno build first — luno deploy runs those checks automatically and fails if anything is wrong.

​
5. Build an automation

Luno OS is built for coding agents. Open your project in Cursor, Claude Code, or another agentic IDE and ask it to help you build. Describe the outcome you want rather than choosing a primitive up front. Your coding agent can inspect available integrations and credentials, clarify consequential choices, and recommend a reliable workflow or an agent where runtime judgment is useful. Example prompts: