---
title: Appaloft for AI Agents
description: Agent-door index for AI coding agents arriving at appaloft.com — appaloft setup agent, then appaloft deploy ., ask first, and return a live URL.
---

# Appaloft for AI Agents

You are an AI agent reading appaloft.com. **Appaloft deploys applications onto user-controlled infrastructure** (bring your own server) or machines the user manages from the Cloud console. The product destination is a live URL for this app.

This document is the Agent-door default index. Configure yourself first with `appaloft setup agent`, then deploy.

Human visitors should use https://www.appaloft.com (two doors: `/deploy` and `/agents`). Coding agents should start at `/llms.txt` (this briefing is the same index).

---

## Setup agent, then deploy

Ask the user before modifying the machine, then run:

```bash
appaloft setup agent
```

This writes skill files and MCP into the Cursor or OpenCode already on this machine. It does not deploy.

- Codex still needs `appaloft auth mcp login` and `appaloft auth mcp codex install`.
- OpenCode may need `--agent opencode`.
- Do **not** print `--agent cursor`.

Before every deploy, ask the human. Then:

```bash
appaloft deploy .
```

On success, **return a live URL for this app**. Failure must exit non-zero. If you are not signed in, you will be asked. A usable Server is part of the path.

`appaloft login` defaults to Cloud. Optional flags, in prose: `--url`, `--mode cloud|self-hosted`, `--no-browser`. Do not tell the user to run `appaloft login --help` or `appaloft login -h`.

If the user declines setup, continue with public docs only and avoid actions that require an Appaloft account.

---

## Do not invent commands

The primary commands are `appaloft setup agent` and `appaloft deploy .`. Optional documented deploy variants exist (`--config appaloft.yml`, `./dist --as static-site`). For login, project, or Server setup, use the first-deployment guide — do not stack those next to the hero command.

There is **no** `appaloft agent`, **no** `appaloft up`, **no** `appaloft projects create`, and **no** `curl agents.appaloft.com | sh`. Do not invent those. Do not print `agent-adapter install` as “make Cursor deploy”. Do not print `appaloft mcp --help` as usage.

`curl -fsSL https://appaloft.com/install.sh | sudo sh` is the **self-host control-plane installer**. Never present it as the developer CLI or agent setup.

Developer CLI install (docs): `npm i -g @appaloft/cli` or `brew install appaloft/tap/appaloft`.

---

## Before destructive actions

Confirm with the user before deleting a project, server, resource, or deployment; overwriting production variables; or any action that loses data or a user-visible URL.

Default posture: describe the change, name the affected resource, and wait for explicit approval.

Never export tokens. Never ask the user to paste cookies, bearer tokens, deploy tokens, private keys, provider credentials, database URLs, or raw secret values into chat.

---

## Reference

- Humans: https://www.appaloft.com
- Agent index: https://www.appaloft.com/llms.txt
- Deploy door: https://www.appaloft.com/deploy
- Agents door: https://www.appaloft.com/agents
- This briefing: https://www.appaloft.com/index.md
- Same briefing: https://www.appaloft.com/start.md
- First deployment: https://docs.appaloft.com/en/start/first-deployment
- Skill: https://docs.appaloft.com/en/agents/skill
- MCP: https://docs.appaloft.com/en/agents/mcp
- CLI: https://docs.appaloft.com/en/reference/cli
- Entrypoints: https://docs.appaloft.com/en/start/entrypoints
- Deploy skill: https://docs.appaloft.com/en/agents/deploy-skill
- GitHub: https://github.com/appaloft/appaloft
- Console: https://app.appaloft.com