Repository navigation
feat(mobile): add the Issues tab and issue screens - #37040
Draft
juliusmarminge wants to merge 1 commit into
Draft
juliusmarminge wants to merge 1 commit into
juliusmarminge wants to merge 1 commit into
Conversation
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Other scenariosNo All 64 scenario measurements
Baseline: unavailable · PR result: 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. |
juliusmarminge
force-pushed
the
issues/6-mobile
branch
from
November 15, 2026 05:14
63c238f to
622836d
Compare
juliusmarminge
force-pushed
the
issues/6-mobile
branch
from
November 15, 2026 05:27
622836d to
34118ef
Compare
Contributor
|
🤖 Android preview
|
Contributor
|
🚀 Expo continuous deployment is ready!
|
Mobile gets a fourth tab that lists issues across environments, and an issue screen with the same reach as the web panel: description, activity, linked pull requests, reactions, comments, state changes, title and description edits, labels, assignees, and new issues with templates. The list grouping, paging and permission rules move from the web page into client-runtime so both clients share them. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
juliusmarminge
force-pushed
the
issues/6-mobile
branch
from
November 15, 2026 06:39
34118ef to
06cb8f6
Compare
This branch has not been deployed
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.
Part of the issue tracking stack, on top of #19274.
Problem
Issues can be browsed and worked on from web and desktop, but the mobile app has no way to see them.
What this adds
How
client-runtime(issue-list,issue-presentation, and a shared cross-environment list atom), so web and mobile run the same logic. Web behaviour is unchanged.workspace-tab-navigation, selection store, detail selection, column navigator) learned a third list + detail section instead of special-casing pull requests.issuesentry. This changes the native fingerprint.ListSearchToolbar).Not in this layer
@/#completions in the comment box (web's issue panel has neither).Testing
vp run check:changedpasses. Run on an iPhone 17 Pro simulator (iOS 27.2) against a dev server with real GitHub data: the Issues tab, filters, the issue screen (state, labels, assignees, description, reactions, linked pull requests, activity, comment box) and the label picker. Not yet run on iPad, a foldable, or Android, and no write was sent from the device.Claude Fable 5.2 via Claude Code
🤖 Generated with Claude Code