From 7b8d9d62f02960ae1e736f44ce6fc6a5eb310088 Mon Sep 17 00:00:00 2001 From: claude code agent 227 Date: Sun, 28 Jun 2026 23:52:48 +0300 Subject: [PATCH] docs(changelog): add detached/autonomous agent runs entry (#184) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit F5: document the #184 feature under [Unreleased] -> Added — runs survive a browser disconnect, reconnect-and-live-follow, POST /ai-chat/run + /ai-chat/stop, the settings.ai.autonomousRuns flag, the ai_chat_runs table, and the phase-1 single-instance constraint. Co-Authored-By: Claude Opus 4.8 (1M context) --- CHANGELOG.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 832615d6..56b9b6f8 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -58,6 +58,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0 append/prepend fragments, nor to COMMENT bodies — a comment may legitimately contain a standalone footnote definition, which canonicalization would drop. (#228) +- **Detached, autonomous agent runs that survive a browser disconnect.** When the + new `settings.ai.autonomousRuns` workspace flag is on (off by default), an + AI-chat turn becomes a first-class, server-side RUN tracked in a new + `ai_chat_runs` table instead of a socket-bound stream: closing the tab or + losing the connection no longer aborts the turn — it keeps executing and + persisting server-side, and only an explicit Stop ends it. A client can + reconnect and live-follow (or stop) an in-flight run via `POST /ai-chat/run` + (resolve the latest run + its assistant message for a chat) and + `POST /ai-chat/stop` (stop by `runId` or `chatId`). A partial unique index + enforces one active run per chat, and a startup sweep settles any run left + dangling by a restart. Phase 1 is single-instance-only (cross-instance Stop is + not yet reliable); the server warns at startup on a horizontally-scaled + deployment. (#184) ### Changed