Skip to content

Tale v0.4.1

Choose a tag to compare

@larryro larryro released this 10 Aug 00:30
670114a

0.4.1 is a feature and fix release on the 0.4 line — an in-place update: tale update, then tale deploy. Four non-destructive data migrations ship with it and apply automatically during deploy; there are no manual steps. Two deliberate behaviour changes are listed below — read them if your organization leans on org-wide knowledge search or a shared inbox pool.

Highlights

Inbox, synced from real mailboxes. Every connected mail credential now syncs into the shared Inbox for triage, each on its own watermark so repeat syncs pick up where they left off, per mailbox (#2915, #2916). Email attachments are stored at ingest and follow the conversation (#2914), and a mailbox's "From" mirrors the IMAP login instead of guessing at an address (#2924, #2925).

Agent runs you can steer and review. Write into a live agent run and it picks your message up mid-flight instead of waiting for the next run (#2921). Agent task work can name a human reviewer: approving settles the task, requesting changes sends it back to the agent with the comment (#2927). Runs whose finishing step died mid-flight now recover instead of stranding the task (#2920), and a running run's badge keeps spinning (#2926).

A provenance layer for regulated processes. Every settled agent run writes one immutable entry to the organization's tamper-evident audit chain: the models actually served, the capability snapshot the run held, spend, produced outputs with checksums, the knowledge it read, approvals raised, and the reviewer linkage (#2947). Project agents and automation nodes accept an autonomy tier (a1 declares posture, a2 parks every outbound write for approval, a3 refuses outbound writes outright), admins can grant competence records, and a review policy can require an independent, competent reviewer. Documents gain opt-in controlled records — draft → in-review (frozen) → approved (immutable), with checksum-addressable approved versions — visible and manageable from the project Files tab (#2954).

Tasks and projects. Tasks get a start date (#2930) and notify assignees when a task starts or comes due (#2943); labels are promoted from freeform strings to a project-scoped catalog with colours (#2929, migrated automatically); your own assignments stand out at a glance (#2944). The projects list shows live open/done task and agent counts (#2939, backfilled), a project with a bound automation gets an Automations tab (#2952), and the list's bulk delete is replaced by reversible bulk archive (#2953).

Plus: conversation privacy is built-in (#2923, see below), skills drop the retired usage-mode and — for new skills — private visibility (#2922), the share-chat dialog is redesigned with neutral feedback buttons (#2946), error toasts say what went wrong (#2935), the dark-mode date picker is readable again (#2945), and row actions are named for screen readers (#2937).

Behaviour changes

  • Knowledge retrieval now enforces document visibility. Team- and project-scoped documents were documented as scoped but remained retrievable org-wide through knowledge search; after the automatic backfill they are returned only to users who can see the document. If someone relied on the org-wide behaviour, share those documents with their team or move them to the org hub. (#2947)
  • Conversation privacy is built-in, not a policy. A thread assigned to a team or person is visible to exactly them (admins and owners see everything); unassigned mail is admin triage, no longer visible to every member. If inbound mail should reach a group on arrival, point conversation routing at a team queue. The old opt-in conversation_access policy is ignored. (#2923)

Migration notes

tale deploy applies four non-destructive migrations automatically; tale migrate status lists them afterwards:

  • 01_automation_pins_to_bindings — automation project pins become explicit binding rows; an automation can now be bound to several projects.
  • 02_task_labels_to_catalog — freeform task labels become the project's label catalog, and tasks reference it.
  • 03_backfill_project_rollup_counts — pre-existing projects get their open/done/agent counters computed.
  • 04_backfill_corpus_document_scope — knowledge-corpus rows inherit their document's team/project scope (the retrieval change above).

Upgrading

tale update    # a 0.4.x CLI stays on the 0.4 line and picks up 0.4.1
tale deploy    # pulls the 0.4.1 images and applies the migrations

On 0.3.x? The 0.3 → 0.4 cutover is a fresh deployment, not an upgrade — read the v0.4.0 release notes and Upgrades → 0.3 → 0.4: breaking cutover before moving.

What's Changed

Full Changelog: v0.4.0...v0.4.1