fix: deliver nested background reports to their Slack thread - #118
Closed
makeitfutureDev wants to merge 0 commit into
Closed
makeitfutureDev wants to merge 0 commit into
makeitfutureDev wants to merge 0 commit into
Conversation
makeitfutureDev
force-pushed
the
fix/nested-background-thread-delivery
branch
from
September 29, 2026 18:14
4bc4121 to
7d3abfb
Compare
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
1 participant
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.
Cause
Nested background agent session keys append
::agent-<id>to the Slack root timestamp. The unattended result path passed the whole session key asthread_ts, so Slack rejected completed reports withinvalid_thread_ts.Change
Resolve the real Slack timestamp before posting the report, menu, and image files. Synthetic scheduled keys produce channel-level posts. Keep the synthetic key for the agent's engine session.
Checks
node --test test/deliver.test.js test/util.test.js test/durable-delivery.test.js— 63 passednpm run check:static— passedgit diff --check— passedLive acceptance
Claude and Codex nested-agent cases and the scheduled-report case are specified in
TEST-PLAN.md. Private QA registry cases and live runs are pending. After the fix is deployed, a safe gateway restart will retry the preserved completed reports.