Skip to content

Tale v0.5.4

Choose a tag to compare

@larryro larryro released this 31 Aug 07:22
320a9a9

0.5.4 is a fix release on the 0.5 line: containerized deployments can start agent runs again — the backend containers now reach the sandbox spawner out of the box.

Highlights

Agent runs start again on containerized deployments (#3115)

On every containerized 0.5 deployment, starting a task assigned to an agent failed within milliseconds with "the agent run could not start: fetch failed". The same defect broke every feature that opens a sandbox session — task-agent runs, coding-harness chat sessions, and automation agent turns.

The root cause was a missing environment default: the backend-api and backend-worker containers were never given SANDBOX_URL, so the platform's sandbox client fell back to its host-development default (http://localhost:8003) — an address nothing serves inside a container. Development setups (bun dev) were never affected, which is how the gap survived: on the host, localhost:8003 happens to be the spawner's published port.

The default is now set at every layer, so any one of them alone fixes a deployment:

  • compose.yml passes SANDBOX_URL=http://sandbox:8003 to both backend containers.
  • The platform image's entrypoint exports the same default for the api/worker roles, so an older compose file with a new image also works.
  • Compose files and .env files generated by tale deploy carry the value explicitly, locked by tests.

An explicitly configured SANDBOX_URL keeps winning everywhere — set it only to point the backend at a spawner running somewhere else.

Migration notes

No database migrations in this release. No operator action is needed beyond the upgrade itself.

Upgrading

  • On the 0.5 line (0.5.0 – 0.5.3):

    tale update
    tale deploy
  • New install:

    curl -fsSL https://raw.githubusercontent.com/tale-project/tale/main/scripts/install-cli.sh | bash
    mkdir tale-05 && cd tale-05
    tale init
    tale deploy
  • Coming from 0.4.x: 0.5 remains a breaking minor with no in-place upgrade in either direction — read the v0.5.0 release notes and Upgrades → 0.4 → 0.5: breaking cutover before touching anything.

What's Changed

  • fix(platform): default SANDBOX_URL so container workers reach the spawner by @larryro in #3115

Full Changelog: v0.5.3...v0.5.4