Repository navigation
Map native mobile to T3 device tools and list threads across projects - #57
Merged
Merged
Conversation
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.
Adopts the two opportunities from #56, which pins the T3 contract that adds them. Merge #56 first.
Why
devicecapability, Claude and delegated children included (fix(server): agents drive simulators through the device tools instead of ssh pingdotgg/t3code#25661). They say to drive simulators and emulators only through the device tools, and that a brief for device work passes thehostIdand deviceid. Upstream's playbooks still say native mobile uses "whatever simulator-driving skill the repo has", and the adapter had no rule for lanes that share a simulator.t3_thread_listtakesallProjects: trueand each item carries itsprojectId(feat(server): agents list snoozed threads across all projects in one call pingdotgg/t3code#26442). The worktree audit and the pinned-and-active set for a disk cleanup listed one project at a time.Changes in
t3-adapter.mdagent-devicecommand thatdevice_openreturns.device_listand puts itshostId,id, andbootedvalue in the brief. Lanes never share a device, so extra device lanes run in sequence. The lane callsdevice_closebefore it returns, withshutdown: truewhen the device was not booted.t3_thread_listwithallProjects: truecovers every project in one call. The pinned-and-active set issettled: false, withallProjects: truewhen the work spans repositories.Version
0.13.2 to 0.13.3. The adapter changed.
Checks
bun run check: pass (637 plugin files, 13 drift entries)bun test tools: 39 passbun run typecheck: passNo pstack run has exercised a device lane or an all-projects thread list yet. This is a text change to the adapter only.