Connect a coding agent

Working outside Aria, in your own coding tool? Install the Aria CLI, sign in and connect your repository. Your agent then works on your app over MCP, with a key that you control.

Three commands

Install. Sign in. Set up.

  1. 01

    Install the CLI

    curl -fsSL https://api.getaria.cloud/v1/downloads/cli/install.sh | sh

    One command. It needs Node.js 22 or newer, checks its download and installs aria in your home folder.

  2. 02

    Sign in

    aria login

    The terminal shows a code. Confirm it in Aria, on the web or in the app. You never type a password here.

  3. 03

    Set up your repository

    aria init

    Run it in your app’s repository. It links the repository to your app, writes the Aria skill and connects Claude Code. Using another agent? Pick it below.

Your agent

Pick your agent, copy the commands.

You approve each key in Aria with a code, and choose what it may do. aria mcp addreaches every app in your project; add --app wsp_… to keep it to one.

Claude Code

Terminal
aria loginaria init

aria init makes a key that reaches only this app and adds it to Claude Code for this repository. It writes the Aria skill to .claude/skills/aria/SKILL.md and adds an Aria section to AGENTS.md.

Codex

Terminal
aria loginaria init --no-mcparia mcp add --agent codex

Aria adds the server to ~/.codex/config.toml, keeps your other settings and installs the skill for Codex.

Cursor

Terminal
aria loginaria init --no-mcparia mcp add --agent cursor

Aria adds the server to ~/.cursor/mcp.json and keeps the servers you already have. The file stays private to you.

Gemini CLI

Terminal
aria loginaria init --no-mcparia mcp add --agent gemini-cli

Aria adds the server to Gemini CLI for every folder and installs the skill for it.

Antigravity

Terminal
aria loginaria init --no-mcparia mcp add --agent antigravity

Aria adds the server to ~/.gemini/antigravity/mcp_config.json and installs the skill for Antigravity.

Any other client

Terminal
aria loginaria init --no-mcparia mcp add --agent other

Aria writes a private aria-mcp.json in this folder. Copy the server into your client’s settings, then delete the file.

First job

Then tell your agent what to do.

Paste this into your agent. It reads your repository and writes your aria.yaml.

  1. get_stack_promptGets the rules
  2. readReads your repository
  3. aria.yamlWrites your stack
  4. validate_stack_fileChecks it
  5. submit_stack_fileSaves it
Tell your agent
Use the Aria skill. Call get_stack_prompt, read this repository, write aria.yaml, check it with validate_stack_file, then save it with submit_stack_file. Ask me to enter any secret values; never print them.

Who decides

Your agent can look. You decide what changes.

Aria enforces this on its servers, not in a prompt. The same rules apply to Aria AI and every agent.

  1. LookStatus, logs and aria.yaml. Runs straight away and changes nothing.
  2. ChangeSaving aria.yaml, deploying, setting variables. Runs or waits, by the key and the change.
  3. DeleteAnything that removes data. Always waits, and you type the name to confirm.

Questions

Coding agents, answered.

Which coding agents work with Aria?

Claude Code, Codex, Cursor, Gemini CLI and Antigravity have their own setup. Any other MCP client that takes a remote HTTP server and a custom header works too.

What does aria init change in my repository?

It links the repository in .aria/link.json, writes the Aria skill to .claude/skills/aria/SKILL.md and adds an Aria section to AGENTS.md. Running it twice changes nothing.

Can my agent see my secrets?

No. Secret values are masked in everything sent back to an agent, even inside logs. You enter them yourself with aria env add.

How do I stop an agent?

Revoke its key under AI & MCP. A revoked key is refused on its next call.

Your agent is in. Launch your app.

Every command, key option and agent guide is in the full docs.

Account · Terms

We’ve updated our terms.

Please read and accept the current terms of service and privacy policy to keep using Aria.