Question
The panel needs the map, its children, their labels, assignees, and blocking state. Establish where
that data comes from and what it costs.
- Does T3 already have a GitHub data layer to reuse? There is a "Pull request" right-panel tab, so
something already talks to GitHub — find it and judge whether it is reusable or PR-specific.
- Otherwise:
gh CLI shelling out, GitHub REST from the server, or from the client?
- The frontier query needs
sub_issues and issue_dependencies_summary (verified available on
radroid/t3code; commands in docs/t3x/agents/issue-tracker.md). Confirm what a single frontier
refresh costs in API calls, and the rate-limit headroom.
- Polling or on-demand? A map open in a panel while you work a ticket implies refresh.
- Auth: which token, and where does it live for the desktop app?
Produce a recommendation with the call count and rate-limit maths, not just an approach.
Question
The panel needs the map, its children, their labels, assignees, and blocking state. Establish where
that data comes from and what it costs.
something already talks to GitHub — find it and judge whether it is reusable or PR-specific.
ghCLI shelling out, GitHub REST from the server, or from the client?sub_issuesandissue_dependencies_summary(verified available onradroid/t3code; commands indocs/t3x/agents/issue-tracker.md). Confirm what a single frontierrefresh costs in API calls, and the rate-limit headroom.
Produce a recommendation with the call count and rate-limit maths, not just an approach.