Skip to main content
Before you start
  • Python 3.10 or newer
  • Docker running, for local runs and builds
  • A Cycls API key for deploying
  • A model key, for example ANTHROPIC_API_KEY or OPENAI_API_KEY

What the five minutes below look like: one file, one command, a live URL.

1

Install the SDK

Check it:
2

Set your keys

Cycls reads a .env file from the working directory automatically.
.env
Keep two files. .env holds keys that stay on your machine, such as CYCLS_API_KEY. .providers.env holds keys the container needs, such as ANTHROPIC_API_KEY. Ship only the second one with cycls.Image().copy(".providers.env", ".env").
3

Scaffold an agent

This writes my_agent.py:
my_agent.py
Four declarations and one function body. The image describes the container, the volume holds chat state, web configures the interface, and llm configures the model. The body receives a context and yields events.
4

Run it locally

Cycls builds the image, starts the container and serves on http://localhost:8080. Every save rebuilds and reloads. The first build takes a minute or two, later ones are cached.
5

Deploy it

The build happens in the cloud, not on your laptop. The deployment name comes from the function name, and redeploying the same name updates it in place.

Give it tools

The managed loop ships with built-in tools. Enabling one is a single call, and each tool brings its own prompt guidance.
Now the agent can search the web, write files into the user’s workspace, run shell commands in a sandbox, and open results on the canvas. See Tools for the full set.

Talk to it over HTTP

Every agent serves an OpenAI-compatible endpoint, so existing clients work without changes.

Next steps

Core concepts

Run, remote and deploy, and when to use each layer.

Build an agent

The loop, the context object, and what the body yields.

Local and remote builds

What happens on your machine and what happens in the cloud.

Guides

End-to-end examples you can copy.