Skip to content

docs: daily update 2026-08-03 — release v4.163.1 - #5593

Open
deco-cms[bot] wants to merge 14 commits into
mainfrom
docs/auto-update-2026-08-03-release-4.163.1
Open

docs: daily update 2026-08-03 — release v4.163.1#5593
deco-cms[bot] wants to merge 14 commits into
mainfrom
docs/auto-update-2026-08-03-release-4.163.1

Conversation

@deco-cms

@deco-cms deco-cms Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Release v4.163.1 (previous: v4.163.0)

Range evaluated: v4.163.0...v4.163.1 (compare: v4.163.0...v4.163.1)

Depends on: #5580 (docs/auto-update-2026-08-03-release-4.160.7) — this PR branches from its HEAD and should be merged after it (which in turn depends on #5574).

Commits covered

  • 747c9d988 — fix(decopilot): drop the ?-in-text heuristic from thread status resolution (fix(decopilot): drop the ?-in-text heuristic from thread status resolution #5585) — 747c9d9warranted a docs update. Previously, a finished (stop) turn was classified as requires_action whenever its final text contained a ? (e.g. a rhetorical question, or a schemeless URL query string like fonts.googleapis.com/css2?...). This caused task-board cards to get permanently stuck in "In Progress" instead of moving to "In Review". The fix makes requires_action come only from structural signals (a pending user_ask or approval-requested tool part) — a clean stop always maps to completed. The docs described the Requires action task state as triggered when the agent "asked you a question," which read as if any question-like text could trigger it — now clarified to be explicit about the structural trigger, matching the fixed behavior and heading off future confusion of this kind.

Commits skipped

  • ebb522db6[release]: bump changed workspace versions — bot release commit, version bump only (package.json changes across apps/api, apps/native, packages/e2e).

Changed doc files (English)

  • studio/decopilot/context-and-tasks.mdx — reworded the Requires action task-state bullet under "What is a task?" to state plainly that it fires only for a pending tool-approval request or user_ask, never merely because reply text contains a question mark.

pt-br counterpart (context-and-tasks.mdx) was auto-translated and updated in the same commit set (technical terms, code, and UI labels kept in English per convention).

Consistency notes

  • Checked quickstart.mdx, overview.mdx, concepts.mdx, and decopilot/overview.mdx for other mentions of task/thread status semantics — no other references to the old text-heuristic or to task states found; no changes needed there.
  • No other doc file references the removed ?-heuristic or the affected source files (status.ts, thread-status.ts, project-chunks.ts).

Summary by cubic

Updates docs for v4.163.1: clarifies Decopilot “Requires action” as a structural trigger only, adds Task Board docs with automated reviewers/auto‑merge, and removes desktop runtime references. Self‑hosting now uses AUTH_* env vars (no auth-config.json), and Kubernetes docs cover the studio-sandbox-go image and optional sandbox OTLP metrics.

  • New Features

    • Task Board: reviewers (QA Agent, Code Reviewer), optional auto‑merge, and “Ship to production”.
    • Sandbox repo picker now shows forks with a Fork badge and explains permission requirements.
    • Kubernetes: opt‑in OTLP metrics export from the sandbox daemon to a collector (ClusterIP required).
  • Migration

    • Auth is env‑var only: set AUTH_* (providers, magic link/OTP); remove auth-config.json. Compose and self‑hosting guides updated.
    • Sandbox is Go‑daemon only: use studio-sandbox-go; no TypeScript/desktop daemon or local runtime/linking. Agents run in a managed cloud sandbox by default.

Written for commit dd7a222. Summary will update on new commits.

Review in cubic

@deco-cms deco-cms Bot added the documentation Improvements or additions to documentation label Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants