Repository navigation
fix(team-plan): name each report file after its sender - #331
Merged
Merged
Conversation
Crews reporting to one lead named their spawn-inbox request after the lead, so two reports landing together overwrote each other and one was lost with nothing reporting it (seen in the v0.8.19 live team probe). The launcher's report-back line now names the file after the sender. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ri8aqK7pwGNSj7zCjcvetU
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ri8aqK7pwGNSj7zCjcvetU
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.
What
The team launcher adds a report-back line to every crew task. That line now names the spawn-inbox file after the sender (
~/.aios/spawn-inbox/<session>-report.json), not after the lead.Why
In the v0.8.19 live team probe, two crews reported to the same lead within the same second. Both named their request after the lead, so the second overwrote the first before the surface picked it up. One report was lost, and nothing (no dead letter, no error) said so. The inbox README already asks for distinct file names, but a worker never reads it; the line the launcher writes is the only instruction it is sure to follow.
Test
tests/team-plan.test.shasserts the sender-named file in the launched task. It fails on the old code (16/17) and passes on the fix (17/17).🤖 Generated with Claude Code
https://claude.ai/code/session_01Ri8aqK7pwGNSj7zCjcvetU