You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 888405f
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): thread setting changes no longer end a Claude session's background work
Changing the runtime mode, worktree, or provider instance detached the
Claude session at once, killing background subagents and shells running
in the CLI process. The thread mutation now probes each session it would
detach with the same background-work check message sends use, and
refuses the change with a retryable message while work is still running.
Archive and settle keep stopping idle background work as before.
Fixes#16000
AI-assisted; verified with the tests and tools listed above.
if (command.type !== "thread.archive" && command.type !== "thread.settle") {
4098
+
for (const session of liveSessions) {
4099
+
if (yield* sessionHasBackgroundWork(session, providerContext!.providerThreads)) {
4100
+
return yield* new OrchestratorDispatchError({
4101
+
commandId: command.commandId,
4102
+
commandType: command.type,
4103
+
cause:
4104
+
"The current session is still running background agents or commands, and this change would end them. Wait for them to finish, or press Stop, then try again.",
4105
+
});
4106
+
}
4107
+
}
4108
+
}
4109
+
4074
4110
const now = yield* DateTime.now;
4075
4111
if (command.type === "thread.metadata.update" && command.limitRecovery != null) {
0 commit comments