Repository navigation
docs: add ADR 0054 for cross-process background task coordination - #10150
Open
Karthik Thota (karthik-0306) wants to merge 2 commits into
Open
Karthik Thota (karthik-0306) wants to merge 2 commits into
Karthik Thota (karthik-0306) wants to merge 2 commits into
Conversation
Karthik Thota (karthik-0306)
temporarily deployed
to
github-app-auth
November 6, 2026 14:18 — with
GitHub Actions
Inactive
Karthik Thota (karthik-0306)
temporarily deployed
to
github-app-auth
November 6, 2026 14:19 — with
GitHub Actions
Inactive
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
Unresolved coordination identity and lifecycle rules can lose completed results, leave owner state unreclaimed, and cancel work against caller intent.
7 open issues
Define a stable, persisted coordination identity · New Allow owner-side terminal results to supersede Lost · New Retry or retain outcomes after store outages · New Clean up remote tasks and child sessions on the owner · New Honor cancel_running=false and guard against remote work · New Cancel lost tasks with known execution IDs on release · New Preserve published outcomes when releasing local runtime state · New
What changed in this PR
Adds proposed ADR 0054 to define cross-process background task coordination for Python and .NET, following the single-process fixes in #9387 and the design direction from #9040. This is a documentation-only change toward #8760, with no runtime or public API changes.
Changes:
- Compares five approaches and recommends a shared coordination contract with an in-memory default.
- Defines execution identity, ownership, result handoff, cancellation, and remote status handling.
- Outlines conformance tests, implementation sequencing, and seven open design questions.
| File | Description |
|---|---|
docs/decisions/0054-background-task-cross-process-coordination.md |
Proposes the shared coordination contract, trade-offs, and validation plan. |
Review effort: Balanced
Karthik Thota (karthik-0306)
temporarily deployed
to
github-app-auth
November 6, 2026 16:43 — with
GitHub Actions
Inactive
This was referenced Nov 9, 2026
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Motivation & Context
Why is this change required?
BackgroundAgentsProviderkeeps its running-task state in process memory, while the task records travel with thesession. With several replicas, one process marks a healthy task of another process as
Lost, results are orphaned,and a session release cannot cancel remote work (seven scenarios in [Feature]: BackgroundAgentsProvider cannot tell a task that is running on another process from one whose owner died #8760).
What problem does it solve?
It records the cross-process contract that both Python and .NET must implement before any code is written, as
requested by the maintainers.
What scenario does it contribute to?
Multi-replica hosts without session affinity.
Issue Link:
Part of [Feature]: BackgroundAgentsProvider cannot tell a task that is running on another process from one whose owner died #8760. This is a design document only.
Description & Review Guide
docs/decisions/0054-background-task-cross-process-coordination.md(status
proposed). It compares five options and recommends a shared coordination contract with an in-memorydefault, keyed by session, task and execution id.
questions at the end. The deciders listed in the front matter are a proposal.
Related Issue
Part of #8760. It is intentionally not a closing reference: the implementation follows once this ADR is accepted. The
direction came from the maintainer on #9040: "define the cross-process ownership and result-handoff contract in a
shared .NET/Python ADR before implementation". #9040 is closed and informed this ADR. The single-process fixes already
landed in #9387.
Contribution Checklist