Environments

A named set of secrets and configuration that a schedule, launch, or cloud run executes inside. Store API keys and credentials here.

What is an environment?

An environment is a named set of secrets and configuration attached to a workspace. When a schedule fires, when you trigger a launch, or when a cloud run starts, it runs inside an environment. That environment is where API keys, webhook URLs, and other credentials live.

You reference an environment by name when you create a schedule or start a launch. The run picks up whatever secrets are stored there.

What goes in an environment

An environment holds any secrets or API keys your plugin needs at runtime.

Scheduled runs require a GitHub token. A scheduled run cannot mint its own GitHub token. You must include a GITHUB_TOKEN (or GH_TOKEN) in the environment so the run can check out your repo and open pull requests. Without it, the schedule cannot start a run against a repository.

Other common values to include:

• A Linear API key (if the plugin reads or writes Linear issues)
• A Slack webhook URL (if the plugin posts notifications)
• Any other third-party service credential the plugin needs

How to create one

From the CLI

Create the environment and supply its secrets in one step using a .env file:

# Create a .env file with your secrets
cat > production.env << 'EOF'
GITHUB_TOKEN=ghp_your_token_here
LINEAR_API_KEY=your_linear_key_here
EOF

# Create the environment from the file
tessl env create production --env-file production.env

To update an existing environment later, use tessl env update:

tessl env update production --env-file production.env

Note: update replaces the entire environment value. Include all keys you want to keep, not just the changed ones.

From the web app

1. Open your workspace settings.
2. Go to Environments.
3. Click Create environment, enter a name, and save.
4. On the environment's page, click Replace value, enter all key/value pairs, and save.

Note: Replace value replaces the entire environment value. The prior value cannot be recovered after you save, so include all keys in the new value.

Related pages

• Schedules: how to reference an environment when creating a schedule