Repository navigation
test(droid): count a Responses developer-role title request as a title - #1066
Merged
Merged
Conversation
Droid's stable runtime promotion failed on macOS because the native-switch live test counted Droid's session-title request as unexpected traffic. Over the Responses protocol Droid puts its system prompt and the title prompt in a "developer" message, and the fixture classifier only read "system" messages. The classifier now reads both roles; the captured request is a unit case that fails on the old classifier. Seen in promotion runs 44859843209 and 44974982481 (macos-26). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
yaacovcorcos
enabled auto-merge
November 22, 2026 06:03
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosAll 64 scenario measurements match All 64 scenario measurements
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
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 Droid runtime promotion has failed on macOS since 11-12. One of its two causes is fixed here.
DroidRuntime.live.test.ts › real Droid confirms switches and automatic default requests for every BYOK protocolcounted Droid's own session-title request as unexpected traffic on macos-26 (promotion runs 44859843209 and 44974982481). Over the OpenAI Responses protocol, Droid puts its system prompt and the title prompt together in adevelopermessage. The fixture classifier read onlysystemmessages, so it never saw the title prompt.The classifier now reads
developermessages too. It still requires the exact title-helper sentence, and any request with tools still counts as agent traffic.Proof
expected 'unexpected' to be 'title') and passes on the new one.developermessage without the title prompt, and the title prompt in anassistantmessage, both still count as unexpected.Not fixed here
The other macOS cause is still open: ENOTEMPTY when the fixture removes the temp HOME while Droid's detached helpers are still writing to
.factory. Until that is fixed, Droid promotion stays red on macOS.Checks
provider/droidpasses, all under pinned Node 26.13.1 with no live-profile variables.Platforms: this only changes how a test sorts captured requests. It runs the same on macOS, Windows and Linux; the failure appeared only on macOS because that is where Droid's title request reached the fixture in time.
🤖 Generated with Claude Code