Skip to content

fix(team-plan): name each report file after its sender - #331

Merged
chuycepeda merged 2 commits into
mainfrom
fix/team-report-filename
Nov 17, 2026
Merged

chuycepeda merged 2 commits into
mainfrom
fix/team-report-filename

Conversation

@chuycepeda

Copy link
Copy Markdown
Member

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.sh asserts 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

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
@chuycepeda chuycepeda added this to the v0.8.20 milestone Nov 17, 2026
@chuycepeda
chuycepeda merged commit 1b136cb into main Nov 17, 2026
15 checks passed
@chuycepeda
chuycepeda deleted the fix/team-report-filename branch November 17, 2026 21:28
@chuycepeda chuycepeda modified the milestones: v0.8.20, v0.8.19 Nov 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant