> ## Documentation Index
> Fetch the complete documentation index at: https://docs.os.meetluno.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI onboarding

> Onboard your AI agent to Luno OS.

Luno OS is designed for building *with* your coding agent. This page helps your coding agent get set up with Luno OS. For a step-by-step walkthrough you run yourself, see the [Quickstart](https://docs.os.meetluno.ai/quickstart.md).

**Recommended:** a local project plus the [CLI for agents](https://docs.os.meetluno.ai/build-with-ai/cli-for-agents.md). That is the default we document and the most stable loop for agents in an editor. The [Luno OS MCP server](https://docs.os.meetluno.ai/build-with-ai/mcp-for-agents.md) is an alternative for chat-first agents with no local install — see [Build over MCP instead](#build-over-mcp-instead) below.

You can also build without a coding agent entirely: [Luno Builder](https://docs.os.meetluno.ai/build-with-ai/platform-agent.md) is a built-in building agent in the Luno OS web app. This page is about onboarding your own coding agent; Luno Builder needs no onboarding.

## Give your agent the setup prompt

The fastest path to setting up Luno OS is giving your agent the following prompt:

```
Read https://os.meetluno.ai/start.md then help me create my first agent.
```

## What your agent gets

`luno init` scaffolds a project that's ready for a coding agent from the first commit:

| File | What it gives your agent |
| - | - |
| `AGENTS.md` | Baseline context: the CLI, project layout, discovery, and working habits |
| `CLAUDE.md` | Symlink to `AGENTS.md` so Claude Code picks it up automatically |
| `tsconfig.json` | Strict TypeScript config for `src/` |
| `package.json` | `@meetluno/luno` pinned to the CLI's release, plus `build`, `lint`, `typecheck`, `test`, and `deploy` scripts |
| `src/` | An example agent, workflow, and action with tests and an eval, to read and extend |

Beyond this baseline, your agent reads the full docs on demand with `luno docs search` and `luno docs query` — see [docs for agents](https://docs.os.meetluno.ai/build-with-ai/docs-for-agents.md).

Most coding agents read `AGENTS.md` automatically when they open the project, so they're oriented before you ask for anything.

## Start building

With the project open in your coding agent, just describe what you want. For example:

```
Build a morning brief agent. It should scan my Google Calendar, Gmail inbox, and Linear issues each weekday morning and send me a short briefing in Slack.
```

```
Build a meeting recap agent. It should trigger whenever one of my Google Meet calls finishes, turn the transcript into action items, and send me a recap in Slack.
```

## Build over MCP instead

Use this path only when local CLI setup is not an option — for example, a chat-first agent in ChatGPT or Claude with no repo on disk.

Connect the [Luno OS MCP server](https://docs.os.meetluno.ai/build-with-ai/mcp-for-agents.md). Your agent works in a hosted workspace with the same docs access and deploy loop, so you skip `luno init` entirely. The MCP hosted-workspace experience is newer than the CLI; when your agent can run in an editor locally, start with the setup prompt above instead.

## Give your agent the docs

This page is often the first thing an agent reads. You can hand it Luno OS's docs in a context-aware way:

1. **All the docs (llms.txt)**

   Point your agent at the complete, machine-readable docs index:

   ```
   Here are the Luno OS docs: https://os.meetluno.ai/docs/llms.txt
   ```

2. **A single page as markdown**

   Append `.md` to any docs URL to get a clean markdown version:

   ```
   Docs for this page: https://os.meetluno.ai/docs/build-with-ai/onboarding.md
   ```

3. **In your editor**

   Every docs page can be copied or opened directly in ChatGPT, Claude, Cursor, or an MCP client from the menu at the top of the page.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.