Tale v0.5.7

0.5.7 is a fix release on the 0.5 line: automation agent runs can now actually use their granted workspace tools — file tasks, write documents and knowledge, and ask their operator a question — and the Convex retirement completes, removing the last legacy runtime packages from the platform.

Highlights

Automation runs get their workspace tools (#3126)

An automation agent's run could not use a single one of its granted workspace tools: ask_human failed with an internal error, and every task and knowledge tool refused with no_access_context — so a run could neither file work nor escalate a question. The 0.5 port had left the workflow_run session lane unfinished, and the automations engine that ships since 0.5.5 mints exactly those sessions.

• Runs act where they are bound. A run pinned to a project acts in that project; one without acts org-wide across its automation's bindings. Writes are attributed to automation:<name>.
• The write tools answer. Task, document, and knowledge write tools reach the same service functions the human and connector lanes already call — task_create lands a card on the run's project board, document_create runs the full upload → link → RAG chain.
• ask_human registers the question against the run instead of erroring, so an automation agent can park on a question and resume when you answer.
• The completion gate matches its own contract. An agent may cancel a card again (abandoning is not certifying — the open-subtasks guard applies), while done stays with the human review gate for every actor: an agent that tries is told to park at in_review. A task node authored with a literal status: done now fails at authoring/deploy-time validation instead of failing on every run; a templated status that resolves to a refused value is named at dispatch.

Runs that failed on these tools before the fix need a rerun after the deploy.

The Convex retirement completes (#3125)

The last pending row of the 0.5 teardown ledger: the legacy convex tree is gone, the ported domain logic lives in the backend tree proper, and the convex packages and dead client remnants are out of the manifests and the image. This is internal restructuring with no user-visible behaviour change — deployed contracts (the convex-data volume name, sandbox-net aliases) are deliberately unchanged, so existing deployments upgrade in place with nothing to rename.

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.6):

  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): serve the automation run's workspace tools by @larryro in #3126
• refactor(platform): retire the convex tree, vocabulary, and packages by @larryro in #3125

Full Changelog: v0.5.6...v0.5.7