Working Copy vs GitHub Mobile

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to GitHub Mobile
   Working Copy—none0/10

   Probes explicitly show no llms.txt, no markdown-accessible docs, and no OpenAPI spec exist for Working Copy; no evidence of any agent-oriented documentation format being provided.

   • [probe] “PROBE llms.txt: HTTP 404 at https://workingcopyapp.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://workingcopyapp.com/manual/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://workingcopyapp.com/openapi.json, https://workingcopyapp.com/swagger.json, https://workingcop…”

   proof ↗⚑ flag

   GitHub Mobile~partialprobed5/10

   A probe confirms docs.github.com serves a valid llms.txt (HTTP 200) that an agent could be pointed at, but this is generic GitHub documentation rather than anything specific to GitHub Mobile, and no GitHub Mobile-specific agent-oriented docs are shown. missing for 10: GitHub Mobile-specific agent-facing documentation, confirmation the llms.txt content covers mobile app usage, independent corroboration of agents actually using it.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.github.com/llms.txt # GitHub Docs > GitHub is a developer platform for building, shipping, and mai…”

   proof ↗⚑ flag

2. ai-native userDrive the product through a documented public API

   weight 3 · round to Working Copy
   Working Copy~partialprobed3/10

   Working Copy documents automation via the Shortcuts app (docs-28) and a WebDAV server for file transfer (docs-27), which allow some programmatic/agentic control, but there is no documented REST/OpenAPI or general-purpose public API — probes confirm no openapi.json, no llms.txt, and no machine-readable docs endpoint. missing for 10: a documented REST/OpenAPI-style API, API reference/docs, and independent confirmation that AI agents can drive it beyond Shortcuts.

   • [claimed-docs] “Working Copy supports automation through the Shortcuts app where files and other data can flow between actions.”
   • [claimed-docs] “a good way to get files into and out of Working Copy is the built-in WebDAV server.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://workingcopyapp.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://workingcopyapp.com/manual/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://workingcopyapp.com/openapi.json, https://workingcopyapp.com/swagger.json, https://workingcop…”

   proof ↗⚑ flag

   GitHub Mobile—none0/10

   GitHub Mobile is a client app with no evidence of exposing its own documented public API; the probe for an OpenAPI/Swagger spec at docs.github.com returned 404s, and the docs pack only markets Copilot features, not programmatic API access to the mobile app itself. missing for 10: any documented REST/GraphQL/OpenAPI spec for driving GitHub Mobile, SDKs, or automation endpoints tied to this product.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.github.com/openapi.json, https://docs.github.com/swagger.json, https://docs.github.com/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.github.com/llms.txt # GitHub Docs > GitHub is a developer platform for building, shipping, and mai…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Working Copy~partialclaimed6/10

   Working Copy documents two AI features: AI-suggested commit messages based on staged diffs (docs-5) and a conversational 'Repository Agent' that can browse, search, read/modify files, commit, pull and push (docs-29) — both surface AI-generated insight/suggestions from the user's repository data. However, evidence is entirely first-party docs with no independent/hands-on validation of quality or reliability, and no detail on depth of 'insights' beyond commit messages and agentic file actions. Missing for 10: independent/hands-on corroboration of the Repository Agent's real-world usefulness, and richer detail on what kinds of data insights (beyond commit suggestions) are generated.

   • [claimed-docs] “includes the ability to suggest messages using artificial intelligence. These AI suggestions require sending staged differences to OpenAI”
   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”

   proof ↗⚑ flag

   GitHub Mobile~partialclaimed6/10

   GitHub Mobile ships Copilot-powered features that generate insights/suggestions from repo data — code review suggestions, natural-language Q&A over public/private repos, and agent task management — per docs-3 through docs-6. However, these are vendor-only claims with no independent/hands-on corroboration of AI-insight quality in the community evidence, which instead focuses on unrelated UX complaints. Missing for 10: independent verification of AI suggestion accuracy/usefulness, detail on what 'insights' are surfaced proactively (vs. on-demand chat), and community confirmation of these AI features working well in practice.

   • [claimed-docs] “Agent Tasks are now on GitHub Mobile, giving developers a centralized way to manage Copilot cloud agent tasks wherever they are. Easily star…”
   • [claimed-docs] “Let Copilot code review analyze your pull requests and suggest improvements right from your phone. Catch bugs, ensure best practices, and bo…”
   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”
   • [claimed-docs] “Ask Copilot to break down complex coding concepts, guide you through unfamiliar codebases, provide insights into both public and your privat…”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to GitHub Mobile
   Working Copy~partialclaimed4/10

   Working Copy integrates with Apple's Shortcuts app for automation (docs-28) and has a conversational Repository Agent that can browse, edit, commit, pull and push (docs-29), but neither is documented as running autonomously in the background without user-triggered interaction — Shortcuts automations in this context appear action-chaining rather than scheduled/autonomous, and the Repository Agent is described as conversational (user-driven), not a background daemon. missing for 10: explicit documentation of scheduled/triggered background automations, evidence of autonomous unattended execution, and independent confirmation of background automation working.

   • [claimed-docs] “Working Copy supports automation through the Shortcuts app where files and other data can flow between actions.”
   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”

   proof ↗⚑ flag

   GitHub Mobile~partialclaimed6/10

   GitHub Mobile lets users assign issues to Copilot and manage/track Copilot cloud agent tasks that run autonomously in the background, and start new agent tasks from the app (docs-3, docs-5, docs-6). However, this is essentially a mobile front-end to trigger/monitor agent runs rather than a full automation-builder (e.g., no scheduling, workflow-authoring, or webhook-trigger setup evidenced), and there is no independent/hands-on corroboration of this specific feature's reliability. Missing for 10: evidence of configuring/scheduling automations (not just assigning single tasks), and independent hands-on validation of the Agent Tasks feature.

   • [claimed-docs] “Agent Tasks are now on GitHub Mobile, giving developers a centralized way to manage Copilot cloud agent tasks wherever they are. Easily star…”
   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”
   • [claimed-docs] “Ask Copilot to break down complex coding concepts, guide you through unfamiliar codebases, provide insights into both public and your privat…”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Working Copy✓fullclaimed7/10

   Working Copy documents a built-in 'Repository Agent' AI assistant that users interact with conversationally to browse files, search content, read/modify files, commit, pull and push — directly matching the delegation story, alongside a separate AI commit-message suggestion feature. missing for 10: no independent/hands-on user reports confirming the Repository Agent's real-world reliability, and no detail on scope limits or setup requirements.

   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”
   • [claimed-docs] “includes the ability to suggest messages using artificial intelligence. These AI suggestions require sending staged differences to OpenAI”

   proof ↗⚑ flag

   GitHub Mobile✓fullclaimed7/10

   GitHub Mobile ships built-in Copilot features letting users delegate work: assigning issues to Copilot for a ready-to-review PR, launching/tracking Copilot cloud 'Agent Tasks', Copilot code review, and natural-language Copilot chat for code Q&A and PR creation, all within the app. Missing for 10: independent/hands-on verification of these AI features (community evidence only covers pre-Copilot app issues) and detail on reliability/limits of the agent delegation flow.

   • [claimed-docs] “Agent Tasks are now on GitHub Mobile, giving developers a centralized way to manage Copilot cloud agent tasks wherever they are. Easily star…”
   • [claimed-docs] “Let Copilot code review analyze your pull requests and suggest improvements right from your phone. Catch bugs, ensure best practices, and bo…”
   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”
   • [claimed-docs] “Ask Copilot to break down complex coding concepts, guide you through unfamiliar codebases, provide insights into both public and your privat…”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Working Copy
   Working Copy✓fullclaimed7/10

   The docs describe a 'Repository Agent' AI assistant that users interact with via conversation to browse files, search content, read/modify files, commit, pull, and push — directly matching natural-language operation. However, this is first-party documentation only, with no independent/hands-on corroboration of how well the natural-language interface actually performs. Missing for 10: independent user reports validating the Repository Agent's reliability, and detail on the scope/limits of supported natural-language commands.

   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”

   proof ↗⚑ flag

   GitHub Mobile~partialclaimed6/10

   GitHub Mobile documents natural-language interaction via Copilot chat (asking Copilot to explain code, navigate repos, open PRs) and Copilot code review/agent task assignment, which are genuine NL-driven agentic capabilities within the app. However this covers only a subset of the app's functionality (core browsing, notifications, merging still require standard UI), and there's no independent/hands-on corroboration of the natural-language features specifically — community evidence only discusses non-AI aspects of the app. Missing for 10: independent corroboration of the Copilot NL features actually working, broader coverage of NL commands beyond code Q&A/PR creation, evidence of reliability in real use.

   • [claimed-docs] “Ask Copilot to break down complex coding concepts, guide you through unfamiliar codebases, provide insights into both public and your privat…”
   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”
   • [claimed-docs] “Agent Tasks are now on GitHub Mobile, giving developers a centralized way to manage Copilot cloud agent tasks wherever they are. Easily star…”
   • [claimed-docs] “Let Copilot code review analyze your pull requests and suggest improvements right from your phone. Catch bugs, ensure best practices, and bo…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Working Copy
   Working Copy~partialclaimed4/10

   The docs show some bulk-like features — the Resolve tool for handling merge conflicts across many files at once, Shortcuts app automation for scripting flows across files, and a Repository Agent AI assistant that can browse/search/modify/commit across a repo — but there is no evidence of true bulk operations across many items (e.g., batch commits across multiple repos, mass file edits, bulk push/pull) as an AI-native automation feature. Missing for 10: explicit multi-repo or multi-file batch APIs, scripted bulk edit/commit workflows, and independent verification that Shortcuts or the Repository Agent can perform such bulk tasks reliably.

   • [claimed-docs] “A faster solution is to use the Resolve tool that lets you resolve conflicts for many files at once.”
   • [claimed-docs] “Working Copy supports automation through the Shortcuts app where files and other data can flow between actions.”
   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”

   proof ↗⚑ flag

   GitHub Mobile—none0/10

   GitHub Mobile evidence focuses on individual item actions (single PR review, single issue assignment, single search) with no mention of bulk/multi-item operations; community feedback even highlights missing features and friction for single-item workflows, with nothing about batch actions across many items.

   ⚑ flag

2. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Working Copy—none0/10

   No evidence of scheduling or recurring job/workflow capability; Shortcuts automation and Repository Agent support ad-hoc triggers, not scheduled recurring jobs. Missing for 10: any scheduling mechanism, cron-like triggers, or recurring workflow automation documentation.

   ⚑ flag

   GitHub Mobile—none0/10

   GitHub Mobile evidence covers reviewing PRs, Copilot agent tasks, code search, and notifications on the go, but nothing describes scheduling recurring jobs or workflows (e.g., cron-like automation or scheduled actions) from the app.

   ⚑ flag

3. ai-native userVersion, review, and roll back my automations

   weight 1 · round to Working Copy
   Working Copy~partialclaimed6/10

   Working Copy provides strong git version-control primitives (commit, undo, amend, delete/squash commits, checkout old versions, commit graph) that could version and roll back automation scripts stored in a repo, and its Repository Agent AI assistant can commit/pull/push conversationally, plus Shortcuts automation integration. However, the story frames automation-workflow versioning specifically, and there's no evidence of automation-run history, diffing of automation configs, or rollback tied to Shortcuts/agent-run outputs rather than generic file commits. missing for 10: evidence of versioning/reviewing/rolling back actual automation runs or agent actions (not just generic git files), independent hands-on confirmation of Repository Agent's commit/rollback behavior.

   • [claimed-docs] “Swipe left on any commit in the repository's commit list to Checkout an old version.”
   • [claimed-docs] “For commits not yet pushed to a remote, swipe left to Undo them. The commit's changes remain in your working directory as modified files”
   • [claimed-docs] “To make changes to the latest commit enable Amend at the top of the commit dialog.”
   • [claimed-docs] “Long tapping commits you can Delete Commit to rewrite the branch without the work contributed by this single commit, Edit Message to change …”
   • [claimed-docs] “To explore repository changes across branches use the Commit Graph available from the Repository screen.”
   • [claimed-docs] “Working Copy supports automation through the Shortcuts app where files and other data can flow between actions.”
   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”

   proof ↗⚑ flag

   GitHub Mobile~partialclaimed4/10

   GitHub Mobile lets users track Copilot cloud agent tasks and review/approve/merge PRs generated by automations, which touches 'review' but nothing in the evidence describes versioning automation configs or explicitly rolling back an automation's changes. missing for 10: explicit workflow/version history for automations, rollback/revert mechanism, and independent confirmation of these capabilities beyond first-party docs.

   • [claimed-docs] “Agent Tasks are now on GitHub Mobile, giving developers a centralized way to manage Copilot cloud agent tasks wherever they are. Easily star…”
   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”

   proof ↗⚑ flag

Repo management

1. developerSearch and navigate code content using fuzzy matching, filters, and regular expressions

   weight 2 · round to Working Copy
   Working Copy~partialclaimed4/10

   Working Copy's docs confirm regular-expression search within file scope (wrapping pattern in slashes), and syntax-highlighted file browsing supports basic navigation, but there is no evidence of fuzzy matching or advanced filter options for code search. missing for 10: fuzzy matching support, filter options (by file type/path/date), evidence of broader project-wide search UI beyond regex.

   • [claimed-docs] “Regular expression search is supported for the file scope by wrapping your pattern in slashes such as /[0-9]+/”
   • [claimed-docs] “File content is shown with syntax highlighting for sourcecode and a preview of html and document files.”

   proof ↗⚑ flag

   GitHub Mobile~partialcommunity3/10

   Docs mention 'global code search' allowing locating snippets and navigating repositories, but there is no evidence of fuzzy matching, filters, or regex support in the mobile search experience. Community feedback also highlights broken navigation to files/links, suggesting code navigation is limited. Missing for 10: documentation or evidence of regex/filter syntax support, fuzzy matching, and independent confirmation of code search functionality working well.

   • [claimed-docs] “Effortlessly locate code snippets, navigate repositories, and access content directly from your home screen with global code search.”
   • [community] “Trying to follow a link on a readme or something to another file within the github repo always results in 'something went wrong' (iOS).”

   proof ↗⚑ flag

2. power-userVisualize the full commit graph across branches

   weight 2 · round to Working Copy
   Working Copy✓fullclaimed8/10

   Working Copy has a dedicated Commit Graph feature accessible from the Repository screen explicitly for exploring repository changes across branches, plus supporting features like swipe-to-checkout old commits and branch-aware history operations. Missing for 10: independent hands-on review or screenshots corroborating the graph's usability/completeness across many branches.

   • [claimed-docs] “To explore repository changes across branches use the Commit Graph available from the Repository screen.”
   • [claimed-docs] “Swipe left on any commit in the repository's commit list to Checkout an old version.”

   proof ↗⚑ flag

   GitHub Mobile—none0/10

   No evidence GitHub Mobile offers any commit-graph visualization across branches; docs cover PR review, Copilot features, notifications, and search but nothing about a graph/branch visualization tool, and community feedback focuses on diffs, notifications, and navigation issues instead.

   ⚑ flag

3. developerCommit and push changes directly from my device

   weight 3 · round to Working Copy
   Working Copy✓fullcommunity8/10

   Working Copy's docs clearly describe the core commit-and-push workflow (staging/committing via the Changes/Status tab, pushing over https/ssh/git protocols, amend/squash, and a real user account of pulling, editing, and pushing on the go). Missing for 10: independent hands-on verification of push reliability/conflict scenarios beyond a single anecdote, and no first-party benchmark or detailed push-error handling documentation.

   • [claimed-docs] “Working Copy supports https, ssh, git, and http protocols”
   • [claimed-docs] “When you have file modifications the Changes tab lights up... you can commit them to the repository with a button on the Status tab.”
   • [claimed-docs] “Working Copy supports private instances of GitHub Enterprise, GitLab and Gitea.”
   • [community] “I have been using this iOS git tool to write a book - the text is on GitHub, and I just wanted to pull, edit and push while on a commute.”

   proof ↗⚑ flag

   GitHub Mobile—none0/10

   GitHub Mobile's evidence covers PR review, merging, Copilot agent tasks, code search, and notifications, but nowhere mentions committing or pushing local file changes/code edits from the device; one community comment even notes a competing third-party app (Working Copy) is used specifically for shipping small changes from a phone, implying GitHub's own app lacks this.

   • [claimed-docs] “Whether you're reviewing a bug fix or merging code, we've got you covered. From your daily commute to grabbing a coffee, unblock your team o…”
   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”
   • [community] “I do a surprising amount of development on my phone these days. I was using GitHub's mobile website for this but I've recently started using…”

   proof ↗⚑ flag

4. power-userInteractively rewrite history by deleting, editing, squashing, or reordering commits

   weight 2 · round to Working Copy
   Working Copy✓fullclaimed8/10

   Working Copy explicitly documents interactive history rewriting: delete commit, edit commit message, squash a commit with its child (docs-17), amend the latest commit (docs-16), and undo unpushed commits (docs-15). This directly covers deleting, editing, squashing commits as described in the story. Missing for 10: no explicit reordering/rebase-onto-arbitrary-commit UI mentioned and no independent hands-on corroboration of this specific feature beyond docs.

   • [claimed-docs] “Long tapping commits you can Delete Commit to rewrite the branch without the work contributed by this single commit, Edit Message to change …”
   • [claimed-docs] “To make changes to the latest commit enable Amend at the top of the commit dialog.”
   • [claimed-docs] “For commits not yet pushed to a remote, swipe left to Undo them. The commit's changes remain in your working directory as modified files”
   • [claimed-docs] “You can configure repositories to Rebase instead of Merge commits from the Configuration page inside Repository status.”

   proof ↗⚑ flag

   GitHub Mobile—none0/10

   GitHub Mobile's evidence covers PR review, Copilot features, notifications, and code search, but there is no mention of interactive rebase, commit editing, squashing, or reordering—capabilities not supported by mobile git clients generally. No documentation or community evidence indicates this exists.

   ⚑ flag

5. developerResolve merge conflicts across many files at once with a dedicated tool

   weight 2 · round to Working Copy
   Working Copy✓fullclaimed8/10

   Working Copy's docs explicitly describe a dedicated 'Resolve tool' for handling merge conflicts across many files at once, directly matching the story. Missing for 10: independent/hands-on corroboration of the multi-file resolve workflow beyond vendor docs.

   • [claimed-docs] “A faster solution is to use the Resolve tool that lets you resolve conflicts for many files at once.”

   proof ↗⚑ flag

   GitHub Mobile—none0/10

   No evidence of any merge conflict resolution tool in GitHub Mobile; the app focuses on PR review, notifications, Copilot tasks, and code search, with no mention of conflict resolution across files. Community feedback even highlights diff-view limitations rather than conflict tools.

   ⚑ flag

6. developerCreate pull requests on hosted Git platforms directly from my device

   weight 3 · round to Working Copy
   Working Copy✓fullclaimed8/10

   Working Copy's docs explicitly state it supports creating pull requests for BitBucket, GitHub and GitLab, directly from the mobile app, and also supports self-hosted GitHub Enterprise/GitLab/Gitea instances. This directly matches the story of creating PRs on hosted Git platforms from a device. Missing for 10: independent hands-on confirmation of the PR-creation flow itself (community evidence covers general git usage but not PR creation specifically).

   • [claimed-docs] “Working Copy supports creating these for BitBucket, GitHub and GitLab.”
   • [claimed-docs] “Working Copy supports private instances of GitHub Enterprise, GitLab and Gitea.”

   proof ↗⚑ flag

   GitHub Mobile~partialcommunity6/10

   GitHub Mobile docs confirm PR-related workflows: assigning issues to Copilot yields a 'ready-to-review pull request' and Copilot chat can 'open a new pull request' directly from the app, with review/approve/merge available in-app. However, evidence centers on Copilot-driven PR creation rather than a straightforward manual 'New Pull Request' flow, and community feedback highlights broader gaps in mobile code-review UX (diff wrapping, missing notifications) though nothing directly disputes PR creation itself. Missing for 10: explicit confirmation of manual (non-Copilot) PR creation from arbitrary branches, and independent hands-on validation of the PR-creation flow.

   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”
   • [claimed-docs] “Ask Copilot to break down complex coding concepts, guide you through unfamiliar codebases, provide insights into both public and your privat…”
   • [claimed-docs] “Let Copilot code review analyze your pull requests and suggest improvements right from your phone. Catch bugs, ensure best practices, and bo…”
   • [community] “I do quite a few code reviews on my Pixel 2, but what drives me crazy is that the lines in the diffs wrap! On top of that, the code font it …”

   proof ↗⚑ flag

7. developerReview pull requests from my phone while on the go

   weight 3 · round to GitHub Mobile
   Working Copy~partialcommunity4/10

   Working Copy documents diff viewing, commit graphs, and syntax-highlighted file review, and notes it can create pull/merge requests for GitHub, GitLab, and BitBucket, which implies some PR-related workflow on mobile. However there is no explicit documentation of viewing PR discussion threads, inline review comments, or approving/merging PRs from the app. Missing for 10: dedicated PR review UI (comments, approve/request-changes, merge button), and independent hands-on evidence of reviewing PRs on the go.

   • [claimed-docs] “To explore repository changes across branches use the Commit Graph available from the Repository screen.”
   • [claimed-docs] “Working Copy supports creating these for BitBucket, GitHub and GitLab.”
   • [claimed-docs] “File content is shown with syntax highlighting for sourcecode and a preview of html and document files.”
   • [community] “I have been using this iOS git tool to write a book - the text is on GitHub, and I just wanted to pull, edit and push while on a commute.”

   proof ↗⚑ flag

   GitHub Mobile~partialcommunity6/10

   GitHub Mobile's official docs explicitly support reviewing, commenting, approving and merging PRs from the phone, plus Copilot-assisted code review, which directly matches the story. However, multiple hands-on community reports describe genuine friction in the review experience itself (diff line-wrapping, large font making diffs hard to read, diff view called 'unusable') and missing PR-review notifications, undercutting a purely full delivery. Missing for 10: independent confirmation that diff readability issues have been fixed, and consistent positive reviews of the core review UX rather than mixed reports.

   • [claimed-docs] “Whether you're reviewing a bug fix or merging code, we've got you covered. From your daily commute to grabbing a coffee, unblock your team o…”
   • [claimed-docs] “Let Copilot code review analyze your pull requests and suggest improvements right from your phone. Catch bugs, ensure best practices, and bo…”
   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”
   • [community] “I do quite a few code reviews on my Pixel 2, but what drives me crazy is that the lines in the diffs wrap! On top of that, the code font it …”
   • [community] “Make the mobile website work well instead. Diff view is unusable, as are many other views. I'd much rather have a working web version than a…”
   • [community] “Really great, has push notifications all that. I just wish I got a push notification...for when I'm assigned to review a PR. Really annoying…”
   • [community] “I tried out the beta version of GitHub's iOS app. I didn't find a single bug in it, and I really enjoyed using it for casually browsing code…”

   proof ↗⚑ flag

8. developerPreview Markdown, HTML, and other rendered files with live reload

   weight 2 · round to Working Copy
   Working Copy✓fullclaimed8/10

   Docs confirm preview of html/document files with syntax highlighting, plus explicit live-reload behavior that auto-reloads on file/asset changes while preserving scroll and zoom. Missing for 10: no independent/hands-on corroboration of live reload in practice and no explicit mention of Markdown-specific preview beyond 'html and document files'.

   • [claimed-docs] “File content is shown with syntax highlighting for sourcecode and a preview of html and document files.”
   • [claimed-docs] “The preview reloads automatically when the file or any local asset it depends on changes, restoring scroll and zoom”

   proof ↗⚑ flag

   GitHub Mobile—none0/10

   No evidence GitHub Mobile offers any Markdown/HTML file preview with live reload; docs focus on PR review, Copilot agent tasks, code search, and notifications, and community comments describe browsing/reviewing code, not rendered file preview with reload.

   ⚑ flag

1. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Working Copy
   Working Copy✓fullclaimed7/10

   Working Copy stores all repository data as standard Git repositories (open format) and provides multiple export paths: Files app/document-picker access, drag-and-drop, a built-in WebDAV server, and Shortcuts automation, meaning a user can pull all data out in a non-proprietary format at any time (docs-24, docs-25, docs-27, docs-28). This directly satisfies 'export in open formats and leave' since Git itself is portable across any host. Missing for 10: no explicit single bulk-export/account-deletion feature described, and no independent hands-on account of a full data migration out of the app.

   • [claimed-docs] “All repositories in Working Copy can be accessed in the Files app and 3rd party applications using the document picker or file browser compo…”
   • [claimed-docs] “Drag files from your emails, the Files app or any other supporting app to add to your repositories.”
   • [claimed-docs] “When adding repositories you tap Link external directory and pick a folder or Document Package in the Files app.”
   • [claimed-docs] “a good way to get files into and out of Working Copy is the built-in WebDAV server.”
   • [claimed-docs] “Working Copy supports automation through the Shortcuts app where files and other data can flow between actions.”

   proof ↗⚑ flag

   GitHub Mobile—none0/10

   No evidence in the pack addresses data export, open formats, or account portability from GitHub Mobile; the app's documentation focuses on code review, Copilot, and browsing features only.

   ⚑ flag

1. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Working Copy—none0/10

   Working Copy's docs mention AI features that send staged diffs to OpenAI (working-copy-docs-5) and an AI Repository Agent (working-copy-docs-29), but there is no mention of any opt-out, data-retention policy, or control preventing that data from being used to train AI models. Since the product actively integrates third-party AI processing, this axis applies, but no evidence shows a training-data opt-out or privacy guarantee exists.

   • [claimed-docs] “includes the ability to suggest messages using artificial intelligence. These AI suggestions require sending staged differences to OpenAI”
   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”

   proof ↗⚑ flag

   GitHub Mobile—none0/10

   No evidence in the pack addresses AI-training data opt-out or privacy controls for GitHub Mobile; all citations concern app features, bugs, and UX complaints. Missing for 10: any mention of data-training opt-out settings, Copilot data usage policy, or privacy controls specific to GitHub Mobile.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Working Copy—none0/10

   Working Copy's docs mention AI features (commit-message suggestions, Repository Agent) that send data to OpenAI, but there is no evidence of any user-facing control over how long that data is retained by the AI provider, nor any deletion/export mechanism for AI-related data. The axis applies because the product ships AI features that transmit user data externally, but no retention/deletion controls are documented. Missing for 10: any documented retention policy, opt-out/delete mechanism for data sent to OpenAI, or user-facing controls over AI data lifecycle.

   • [claimed-docs] “includes the ability to suggest messages using artificial intelligence. These AI suggestions require sending staged differences to OpenAI”
   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”

   proof ↗⚑ flag

   GitHub Mobile—none0/10

   No evidence in the pack addresses data retention or deletion controls related to AI/Copilot features within GitHub Mobile; all citations concern app features, UX complaints, or unrelated docs probes.

   ⚑ flag

3. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Working Copy—none0/10

   No evidence in the pack addresses telemetry, usage tracking, analytics, or an opt-out setting for Working Copy; only AI commit-message and Repository Agent features mention sending data to OpenAI, with no privacy toggle documented. Missing for 10: any privacy policy or settings documentation on telemetry/analytics collection, and any opt-out mechanism.

   ⚑ flag

   GitHub Mobile—none0/10

   No evidence in the pack addresses telemetry opt-out or usage tracking controls for GitHub Mobile; all docs focus on features (Copilot, code search, reviews) and community items discuss UX bugs, not privacy settings.

   ⚑ flag

Ai coding agents

1. ai-native userHave an AI agent analyze my pull requests and suggest code improvements from my phone

   weight 3 · round to GitHub Mobile
   Working Copy~partialclaimed4/10

   Working Copy ships a 'Repository Agent' AI assistant that can browse, search, read/modify files, commit, pull and push from the phone, which is a general agentic capability, but the docs never mention it analyzing pull requests specifically or suggesting code improvements (only AI-generated commit messages are separately documented). missing for 10: explicit PR review/analysis feature, code-improvement suggestions, independent hands-on evidence of the Repository Agent doing this task.

   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”
   • [claimed-docs] “includes the ability to suggest messages using artificial intelligence. These AI suggestions require sending staged differences to OpenAI”

   proof ↗⚑ flag

   GitHub Mobile✓fullclaimed7/10

   First-party docs directly state Copilot code review can analyze PRs and suggest improvements from the phone, matching the story closely (github-mobile-docs-4), supported by related Copilot agent task management on mobile (github-mobile-docs-3, docs-5, docs-6). Missing for 10: independent/hands-on verification of this specific Copilot code review feature (community evidence predates Copilot integration and only covers general app usability issues, not AI review functionality).

   • [claimed-docs] “Let Copilot code review analyze your pull requests and suggest improvements right from your phone. Catch bugs, ensure best practices, and bo…”
   • [claimed-docs] “Agent Tasks are now on GitHub Mobile, giving developers a centralized way to manage Copilot cloud agent tasks wherever they are. Easily star…”
   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”
   • [claimed-docs] “Ask Copilot to break down complex coding concepts, guide you through unfamiliar codebases, provide insights into both public and your privat…”

   proof ↗⚑ flag

2. ai-native userDirect an AI agent to browse, search, edit, commit, pull, and push in a repository via conversation

   weight 3 · round to Working Copy
   Working Copy✓fullclaimed7/10

   Working Copy documents a first-party "Repository Agent" that is explicitly described as an AI assistant interacted with via conversation, capable of browsing files, searching content, reading/modifying files, committing, pulling and pushing — directly matching the story. However, there is no independent/community corroboration of this specific agent feature working hands-on, and details on setup, model/provider, and reliability are thin. Missing for 10: independent or hands-on validation of the Repository Agent, more detail on configuration/limitations, and confirmation of conversational browsing/search fidelity beyond the doc line.

   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”
   • [claimed-docs] “When you have file modifications the Changes tab lights up... you can commit them to the repository with a button on the Status tab.”
   • [claimed-docs] “includes the ability to suggest messages using artificial intelligence. These AI suggestions require sending staged differences to OpenAI”

   proof ↗⚑ flag

   GitHub Mobile~partialclaimed6/10

   GitHub Mobile lets users converse with Copilot to search code, ask questions about repos, assign issues to Copilot for automated PR creation, and manage Copilot cloud agent tasks—covering browse, search, and a form of edit/commit/PR creation via natural language. However, there's no evidence of a full conversational agent loop that also handles pull/push git operations or arbitrary file edits directly through chat; PR creation is Copilot's autonomous action rather than user-directed commit/pull/push. Missing for 10: explicit pull/push-via-conversation capability, hands-on confirmation of the full browse-to-push agent workflow, and independent corroboration beyond vendor docs.

   • [claimed-docs] “Agent Tasks are now on GitHub Mobile, giving developers a centralized way to manage Copilot cloud agent tasks wherever they are. Easily star…”
   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”
   • [claimed-docs] “Ask Copilot to break down complex coding concepts, guide you through unfamiliar codebases, provide insights into both public and your privat…”
   • [claimed-docs] “Effortlessly locate code snippets, navigate repositories, and access content directly from your home screen with global code search.”

   proof ↗⚑ flag

3. ai-native userAssign an issue to an AI coding agent and receive a ready-to-review pull request

   weight 3 · round to GitHub Mobile
   Working Copy—none0/10

   Working Copy's 'Repository Agent' is a conversational AI assistant for browsing/editing/committing within the app, but there is no evidence of assigning an external issue to an autonomous agent that then produces a ready-to-review pull request. missing for 10: issue-to-PR automation workflow, autonomous agent triggering from issue assignment, PR creation/readiness evidence.

   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”

   proof ↗⚑ flag

   GitHub Mobile✓fullclaimed7/10

   First-party docs explicitly state the exact capability: 'Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitHub Mobile,' plus supporting docs on Copilot cloud Agent Tasks management from mobile. Missing for 10: independent/hands-on corroboration specifically of this AI-agent assignment flow (all community evidence predates this feature and concerns unrelated app UX issues).

   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”
   • [claimed-docs] “Agent Tasks are now on GitHub Mobile, giving developers a centralized way to manage Copilot cloud agent tasks wherever they are. Easily star…”
   • [claimed-docs] “Ask Copilot to break down complex coding concepts, guide you through unfamiliar codebases, provide insights into both public and your privat…”

   proof ↗⚑ flag

4. ai-native userConverse with an AI agent in natural language to get insights into repositories and open pull requests

   weight 2 · round to GitHub Mobile
   Working Copy~partialclaimed6/10

   Working Copy's docs describe a 'Repository Agent' AI assistant you converse with to browse files, search content, read/modify files, commit, pull and push — directly matching the ai-native conversational insight story for repositories. However, there is no explicit mention of pull-request insights/management via this agent, and no independent/hands-on corroboration of the feature's real-world behavior. missing for 10: explicit pull-request conversational insight capability, independent/hands-on verification of the Repository Agent's conversational quality.

   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”

   proof ↗⚑ flag

   GitHub Mobile✓fullclaimed7/10

   First-party docs explicitly describe conversing with Copilot in natural language on GitHub Mobile to get insights into public/private repositories, explain codebases, and open pull requests, directly matching the story. Missing for 10: independent hands-on corroboration of the AI chat/insights feature specifically (community evidence is mostly about general app usability, not the AI conversational feature) and detail on PR-specific insight depth.

   • [claimed-docs] “Ask Copilot to break down complex coding concepts, guide you through unfamiliar codebases, provide insights into both public and your privat…”
   • [claimed-docs] “Agent Tasks are now on GitHub Mobile, giving developers a centralized way to manage Copilot cloud agent tasks wherever they are. Easily star…”
   • [claimed-docs] “Let Copilot code review analyze your pull requests and suggest improvements right from your phone. Catch bugs, ensure best practices, and bo…”
   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”

   proof ↗⚑ flag

5. developerManage and track cloud-based coding agent tasks from my phone

   weight 2 · round to GitHub Mobile
   Working Copy—none0/10

   Working Copy is a mobile git client with its own in-app AI 'Repository Agent' for local file/commit operations (working-copy-docs-29), but there is no evidence it can view, manage, or track tasks from cloud-based coding agents (e.g., a task queue, agent run status, or PR tracking from services like Codex/Copilot workspace). The story's specific axis of monitoring cloud agent task state is unaddressed.

   • [claimed-docs] “Repository Agent is an AI assistant that you interact with through conversation. Ask it to browse files, search content, read and modify fil…”

   proof ↗⚑ flag

   GitHub Mobile✓fullclaimed8/10

   First-party docs explicitly state Agent Tasks are on GitHub Mobile giving a centralized way to manage Copilot cloud agent tasks, start new tasks, and track progress, directly matching the story. Missing for 10: independent/hands-on corroboration of this specific agent-task feature (community evidence predates this feature and covers general app issues only).

   • [claimed-docs] “Agent Tasks are now on GitHub Mobile, giving developers a centralized way to manage Copilot cloud agent tasks wherever they are. Easily star…”
   • [claimed-docs] “Assign issues to Copilot and get a ready-to-review pull request. Use comments to refine, iterate, approve and merge—all directly within GitH…”

   proof ↗⚑ flag

Credential protection

1. developerProtect my remote connections with biometric authentication like Face ID or fingerprint

   weight 2 · round to Working Copy
   Working Copy~partialclaimed6/10

   Working Copy documents that SSH keys can be stored in the Secure Enclave protected by Face ID or Touch ID, directly enabling biometric protection of remote (SSH) connections. However, this is limited to SSH key access specifically, with no evidence of biometric gating for HTTPS credentials or app-wide lock, and no independent/hands-on corroboration beyond the vendor docs. Missing for 10: evidence of biometric protection for HTTPS remotes, independent confirmation of the Face ID/Touch ID flow in practice, and details on fallback/security scope.

   • [claimed-docs] “SSH keys can reside on the Secure Enclave protected by Face ID or Touch ID.”
   • [claimed-docs] “Working Copy supports https, ssh, git, and http protocols”
   • [claimed-docs] “You attach a private key to your Identity which can be imported or generated inside the app.”

   proof ↗⚑ flag

   GitHub Mobile—none0/10

   No evidence in the pack mentions biometric authentication, Face ID, fingerprint unlock, or any app-level security lock for GitHub Mobile; only general feature descriptions and unrelated community complaints are present.

   ⚑ flag