# Let your AI do it

If you work with a coding agent, it can do the setup for you. Create an agent in the app (**Developer → New agent**), copy the key, and paste this prompt into Claude Code, Codex, Cursor or any agent that can read the web:

```text
Connect this project to Cestra so you can message me. Read https://docs.cestra.ai/llms.txt. Use this API key: cs_live_YOUR_KEY. When it works, send me 'Hello from Cestra'.
```

Replace `cs_live_YOUR_KEY` with your key. When "Hello from Cestra" appears in your thread, you're connected.

## What the agent will do

[llms.txt](/llms.txt) is a condensed, machine-readable version of these docs. From it the agent learns the API and picks a path:

- **Inside Claude Code or Codex**, it usually installs the [MCP server](/mcp), so it can use tools like `ask` and `send_message` in later sessions.
- **In a Python or Node project**, it installs the [Python](/python) or [JavaScript](/javascript) SDK and writes a small client.
- **Anywhere else**, it calls the [REST API](/rest-api) directly.

## Keep the key safe

The prompt puts your key in the chat. That's fine for a key you just created, but:

- Ask the agent to store it in an environment variable or an ignored `.env` file, never in committed code.
- If a key ends up somewhere it shouldn't, revoke it under **Developer → API keys** and create a new one. Revocation takes effect immediately. See [Limits & security](/limits).

## Good follow-up prompts

```text
From now on, when you finish a long task, send me a summary on Cestra.
```

```text
Before you run anything destructive (deleting files, force-pushing, migrations), ask me on Cestra with Approve / Cancel buttons and wait for my answer.
```

```text
While you work on this, keep a Cestra job updated with one step per phase.
```