Skip to main content
Cycls loads a .env file from the working directory at import. Variables fall into three groups by where they belong.

On your machine

These are for deploying. Keep them out of the container image.

Inside the container

These belong in the image, usually through .copy(".providers.env", ".env"). Any other key your handlers use, such as a service token for your own API, goes here too.
Do not put CYCLS_API_KEY in the image. It is a deploy credential. Splitting .env for your machine and .providers.env for the container keeps it out:

Optional services

Set these when the matching feature should be available. With any of them unset, the feature is not offered and nothing else breaks.

Connector relay

Set on deployments that share one registered OAuth redirect across agents.

Injected by the platform

Read these, do not set them.

Checking what a container sees

Next

Limits and quotas

Sizes, timeouts and caps in one table.