Configure Temporal

How Cori connects to Temporal — auto-spawned dev server for local use, existing cluster for production.

Default: auto-spawned dev server

For solo local use, you don't need to configure anything. If no Temporal endpoint is configured and nothing is serving 127.0.0.1:7233, cori run automatically shells out to temporal server start-dev as a supervised child process.

TODO: Confirm whether the temporal binary is bundled with the Cori CLI installer, or must be installed separately by the operator. If it must be installed separately, add temporal (the Temporal CLI) to the prerequisites on the install page.

For now: if cori run fails with a Temporal connectivity error and you haven't configured an endpoint, check that the temporal binary is available (which temporal). If not, install it from temporal.io/cli.

Point at an existing Temporal cluster

For production, CI, or shared team setups, point Cori at an existing Temporal cluster:

Via config file:

# ~/.cori/config.toml
[temporal]
host = "temporal.mycompany.com:7233"

Via environment variable:

CORI_TEMPORAL_TARGET=temporal.mycompany.com:7233 cori run ./my_workflow

The environment variable takes precedence over the config file.

To set the config value permanently:

cori config set temporal.host temporal.mycompany.com:7233

Verifying the connection

cori status

cori status shows the current Temporal endpoint and whether Cori can reach it.

Not supported in v1

There is no Temporal Cloud support and no multi-region setup. Cori connects to a single Temporal endpoint. Configure that endpoint to point at whatever Temporal instance you have.

Running a Temporal dev server manually

If you want to manage the Temporal dev server yourself (rather than let Cori auto-spawn it):

temporal server start-dev

Then run cori commands as normal. Cori will detect that 127.0.0.1:7233 is already serving and skip the auto-spawn.