Set up with an AI assistant

An AI coding assistant, such as Claude Code, Cursor or Codex, can set up a Suta project for you. It installs the CLI, writes suta.yaml for your app, and plans and deploys it, asking you before anything changes on a device.

Copy the prompt

Open your assistant in the repository for your app. Copy this prompt, add what your devices should run at the end, and send it.

Prompt

Help me deploy software to my devices with Suta, from this repository.

Before you start, read the Suta documentation at
https://docs.suta.dev/llms-full.txt. Use only the commands, options and
suta.yaml settings it describes; don't guess. The suta.yaml schema is at
https://suta.dev/schema/suta.json.

1. Check that the Suta CLI is installed with `suta --version`. If it isn't,
   install it with `curl -fsSL https://suta.dev/install.sh | bash -s -- --cli`.
2. Run `suta auth status`. If I'm not signed in, ask me to run
   `suta auth login`, which opens my browser.
3. Run `suta project list` and ask me which project to deploy to.
4. Write suta.yaml for what I describe below. Use images that include
   linux/arm64, give every app a probe, and keep data that must survive
   updates in volumes. If an app needs a secret, ask me to create it with
   `suta secret set NAME`; never ask for or print its value.
5. Run `suta plan --device DEVICE` for one device I choose. Show me the
   output and explain what will change.
6. Only after I confirm, deploy that plan with `suta deploy PLAN_ID --wait`.
   If the device rolls the change back, run `suta device generations DEVICE`,
   tell me why, and fix suta.yaml.
7. Once it works on one device, ask me before rolling it out to the rest of
   the project.

When we're done, commit suta.yaml and suta.lock.

What my devices should run:

You still sign in and create secrets yourself; the assistant asks you when it needs you to.

Give an assistant the docs

These docs are also published as plain text for AI assistants. Point an assistant at one of these files, or add it to its context, when you ask it about Suta.

File	What’s in it
llms.txt	Where to start: what Suta is, and links to the other files.
llms-full.txt	The complete documentation in one file.
llms-small.txt	The same, with tips and notes removed, for assistants with less room.
_llms-txt/reference.txt	One section of the docs, such as the reference. llms.txt lists a file for each section, for an assistant that only needs part of them.

For suta.yaml, editors and assistants can also use the JSON Schema.

Let an agent work on your devices

To let an assistant read logs, check metrics or follow a rollout for you, connect it to Suta’s MCP server. It gets only the access you approve. See Connect an AI agent.