Skip to content

Tale v0.5.5

Choose a tag to compare

View all tags
@larryro larryro released this 31 Aug 12:30
v0.5.5
586927f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

0.5.5 is a fix and feature release on the 0.5 line: task-agent runs work end-to-end again — the card moves, the transcript streams, and turns keep running — and organizations that sign in with Microsoft Entra ID can reuse that app registration for Microsoft 365 import.

Highlights

Task-agent runs move the card, stream, and self-chain (#3117)

Assigning a task to a project agent and starting a run was broken in several stacked ways on 0.5 deployments: the task never moved to In progress, the run panel sat forever on "The agent produced no log for this run.", every turn died after its first drive window, @-mentioning an idle agent did nothing, and any task carrying attachments or prior deliverables failed at input staging. All of it is repaired:

  • The board moves again. Starting a run flips the task to In progress in the same transaction as the kick, with the full status choreography; a second start while a run is live answers "already running" instead of doing anything. This also re-arms auto-retry, which requires the in-progress status.
  • The run is visible live. The run card and the live transcript now refresh while the run is active, so you watch the agent work instead of a frozen spinner.
  • Turns keep running. The run host's self-chaining and steer-retry scheduling were never wired to the 0.5 job queue, so every run ended after its first drive window and settled as "could not start". Runs now continue to completion.
  • @-mentions put an idle agent to work again. Commenting with an @-mention of a project agent steers its running run, or (re)assigns the task and kicks a run that treats your comment as feedback — moving the card with it. A queued or otherwise live run is left alone, and agents' own comments never dispatch.
  • Task attachments and prior deliverables stage again. The blob-staging door the sandbox fetches inputs through was never served by the 0.5 backend, so every org-bucket staging failed the run. It is back, with token verification, per-organization namespace checks, and a concrete per-file reason whenever a file is skipped.
  • Non-Claude models run reliably. Claude-specific reasoning-effort settings were forced onto every model and could collapse some models (e.g. DeepSeek variants) into one-token responses that silently ended turns mid-work; they now apply to Claude models only. A turn that ends with no final report no longer parks the task half-done at In review — it fails as retryable and the retry resumes the same conversation. And when a provider permanently rejects a conversation (e.g. a text-only model that was shown an image), retrying starts a fresh conversation instead of resuming into the same rejection.

Reuse the Entra SSO app for Microsoft 365 import (#3116)

An organization that signs in through Enterprise SSO with Microsoft Entra ID has already registered a vendor app — but enabling Knowledge's From Microsoft 365 import still demanded configuring a second OAuth app by hand. The same registration can now serve both:

  • Settings → Connectors → OAuth apps: the OneDrive / SharePoint row offers Use Entra ID SSO app whenever the organization's active SSO is a usable Entra registration. The confirm dialog previews the client ID and tenant, and lists exactly what the registration still needs in Entra: the cloud-import redirect URI and the delegated Graph permissions (Files.Read, Sites.Read.All, User.Read, offline_access).
  • The copy is derived server-side — the client secret never passes through the browser, and the audit chain records the reuse.
  • Copy semantics, not a live link: sign-in and import consents stay separate (sign-in never gains file scopes), and rotating the SSO secret means clicking copy again.

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

    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

  • feat(platform): reuse the Entra SSO app for Microsoft 365 import by @larryro in #3116
  • fix(platform): task-agent runs move the card, stream, and self-chain by @larryro in #3117

Full Changelog: v0.5.4...v0.5.5

Contributors

larryro
Assets 8
Loading