Connections and environments

Know which Synth service your commands target, without confusing it with the environment where an agent works.

Two different things are often called an environment:

Term	Meaning
Synth connection	The service endpoint and identity that own your tasks, runs and checkpoints.
Task environment	The files, software and resources provided to an agent during one trial.

Changing the first does not update the second.

Check your connection

synth status --json

Inspect the reported API base URL, its source, credential source and any authentication issue. Status describes local configuration; a successful authorized read is a separate check of remote access:

synth task list --json

Use the CLI’s shipped default unless your organization has supplied a different Synth connection. The public customer API base is https://sprites-gateway.api.synthlabs.ai.

An administrator-provided override uses SYNTH_API_BASE_URL. Credentials may be bound to a particular service. Changing the URL does not make an existing credential valid there; authenticate for the intended service instead.

Never send a credential to an untrusted host. Do not change a working connection just to make a troubleshooting example pass. Task names and run IDs from one connection need not exist in another.

Configure the task environment

The task package defines its image, working files, timeouts and resource requirements. A run may supply explicit overrides. Read the resolved request before submission; do not assume an override rewrote the immutable task.

See task authoring and resources and limits.