Tailscale vs Working Copy

Not comparable on these axes

1. ai-native userRun the product headlessly / in CI for automation

   weight 2 · not comparable
   Tailscale~partialprobed5/10

   Docs show Tailscale can run inside Docker containers, be automated via auth keys/IaC/webhooks, and has a documented CLI for scripting—strongly suggesting headless/CI use—but there's no explicit CI pipeline example (e.g., GitHub Actions) in the evidence, and community feedback notes API keys expire every 60 days, complicating long-running automation. missing for 10: explicit CI/CD integration examples, confirmation of long-lived non-expiring credentials for unattended automation, and independent hands-on CI usage reports.

   • [claimed-docs] “Explore how to use Tailscale inside Docker containers.”
   • [claimed-docs] “Automate your tailnet using infrastructure-as-code providers, webhooks, and other integrations.”
   • [probe] “official CLI documented at https://tailscale.com/docs/reference/tailscale-cli”
   • [community] “our pricing ties number of servers to number of users... I don't see how this can ever work within the limits in their pricing plans... thei…”

   proof ↗⚑ flag

   Working Copyn/a

   Working Copy is a GUI-based iOS git client tied to the iPhone/iPad interface; it offers on-device automation via Shortcuts and URL schemes but has no server/CLI mode that could run headlessly in a CI pipeline. Running headlessly/in CI is a category error for this type of mobile app, not a missing feature.

   • [claimed-docs] “Working Copy supports automation through the Shortcuts app where files and other data can flow between actions.”

   proof ↗⚑ flag

2. ai-native userPlug MCP servers into this product so it can use their tools

   weight 3 · not comparable
   Tailscalen/a

   Tailscale is a networking/VPN product, not an AI agent or agentic tool; plugging MCP servers into it to gain tool access is a category error for this product type.

   ⚑ flag

   Working Copy—none0/10

   Working Copy's docs describe a built-in 'Repository Agent' AI assistant but there is no evidence it supports plugging in external MCP servers or consuming third-party tools via MCP; automation is only via Shortcuts app actions, not MCP.

   • [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] “Working Copy supports automation through the Shortcuts app where files and other data can flow between actions.”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · not comparable
   Tailscalen/a

   Tailscale is a networking/VPN infrastructure product, not an AI agent or agent-serving platform; no evidence of an MCP server offering exists, and this axis is a category error for a network connectivity tool.

   ⚑ flag

   Working Copy—none0/10

   Working Copy is a git client with a built-in 'Repository Agent' AI assistant (docs-29), but there is no evidence of an official MCP server that lets external agents connect to Working Copy; probes for llms.txt/openapi endpoints also return 404s.

   • [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…”
   • [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

4. ai-native userUse an official CLI

   weight 2 · not comparable
   Tailscale~partialprobed5/10

   Tailscale documents an official CLI reference (tailscale-probe-3), confirming the capability exists, but the evidence pack lacks detail on CLI features, scripting/automation support for AI-agent workflows, or independent corroboration of its use in agentic contexts. Missing for 10: detailed CLI command documentation, AI-agent-specific automation examples, and independent hands-on validation of CLI robustness.

   • [probe] “official CLI documented at https://tailscale.com/docs/reference/tailscale-cli”

   proof ↗⚑ flag

   Working Copyn/a

   Working Copy is an iOS-only Git client with no terminal/CLI environment; its automation surface is limited to URL schemes, Shortcuts integration, and an in-app AI 'Repository Agent'. A traditional CLI is not a coherent capability for a sandboxed iOS app, making this axis a category mismatch rather than a missing feature.

   • [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

5. ai-native userBuild against official SDKs

   weight 2 · not comparable
   Tailscale—none0/10

   Evidence shows only infra-as-code/webhook integrations and a CLI reference, with no mention of official SDKs; probes explicitly show the OpenAPI spec and llms.txt endpoints returning 404, indicating no discoverable machine-readable API/SDK surface for AI-native builders.

   • [claimed-docs] “Automate your tailnet using infrastructure-as-code providers, webhooks, and other integrations.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://tailscale.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://tailscale.com/openapi.json, https://tailscale.com/swagger.json, https://tailscale.com/api/op…”
   • [probe] “official CLI documented at https://tailscale.com/docs/reference/tailscale-cli”

   proof ↗⚑ flag

   Working Copyn/a

   Working Copy is a Git client app for iOS, not a platform offering an SDK for developers to build against; the story asks about official SDKs which is a category error for this product type.

   ⚑ flag

6. ai-native userSubscribe to events via webhooks

   weight 2 · not comparable
   Tailscale~partialclaimed5/10

   Tailscale docs explicitly mention automating the tailnet via 'infrastructure-as-code providers, webhooks, and other integrations,' indicating webhook support exists, but there's no detail on event types, subscription setup, or payload schema, and no independent/community corroboration of using this feature. Missing for 10: documentation of specific webhook event catalog, setup/config details, and independent confirmation of real-world webhook usage.

   • [claimed-docs] “Automate your tailnet using infrastructure-as-code providers, webhooks, and other integrations.”

   proof ↗⚑ flag

   Working Copyn/a

   Working Copy is a mobile Git client app, not a service with an event-driven API; webhooks (subscribing to repo/CI events) is not a fair capability for this type of product. Evidence shows Shortcuts automation and Files app integration but nothing about webhook subscriptions, which is out of scope for a client app.

   • [claimed-docs] “Working Copy supports automation through the Shortcuts app where files and other data can flow between actions.”

   proof ↗⚑ flag

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

   weight 2 · not comparable
   Tailscalen/a

   Tailscale is a networking/VPN product for connecting devices and infrastructure; it has no data analytics or AI-insights layer over user data, and this axis is a category error for its product type.

   ⚑ flag

   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

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

   weight 3 · not comparable
   Tailscalen/a

   Tailscale is a networking/VPN product; it does not offer or claim any built-in AI assistant feature. Delegating tasks to an AI assistant is outside its product category, making this axis a category error rather than an unmet capability.

   ⚑ flag

   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

9. ai-native userTest against a sandbox environment without touching production data

   weight 1 · not comparable
   Tailscalen/a

   Tailscale is a network connectivity/VPN product, not a testing, data-management, or sandbox-environment tool; the notion of 'sandbox vs production data' for AI testing is a wrong axis for this product category.

   ⚑ flag

   Working Copyn/a

   Working Copy is a git client for iOS; sandbox-vs-production data isolation for AI testing is not a relevant capability for this kind of product — it's a wrong-axis question.

   ⚑ flag

10. ai-native userSchedule recurring jobs or workflows

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product; scheduling recurring jobs or workflows is not a networking capability and falls entirely outside its product category. This is a wrong-axis question, not a missing feature.

    ⚑ flag

    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

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

    weight 1 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product, not an automation/workflow-building tool with versionable automations; versioning, reviewing, and rolling back 'automations' is not a fair axis for its category.

    ⚑ flag

    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

12. power-userAmend the latest commit or undo unpushed commits to fix or split them

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product with no git functionality; amending commits or managing git history is entirely outside its product category.

    ⚑ flag

    Working Copy✓fullclaimed8/10

    Docs explicitly describe amending the latest commit via the commit dialog's Amend toggle and undoing unpushed commits via swipe-left, with changes preserved in the working directory, plus additional editing tools (Edit Message, Squash, Delete Commit) for splitting/fixing history. Missing for 10: independent hands-on verification of these specific commit-editing workflows beyond first-party docs.

    • [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 …”

    proof ↗⚑ flag

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

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product; code search, fuzzy matching, and regex-based navigation of code content are outside its category entirely — this is a wrong-axis question, not a missing feature.

    ⚑ flag

    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

14. developerClone Git repositories over HTTPS, SSH, or the Git protocol

    weight 3 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN tool, not a Git hosting or code-clone tool; cloning repos via HTTPS/SSH/Git protocol is outside its product category, though it could enable network access to a self-hosted Git server as a side effect.

    ⚑ flag

    Working Copy✓fullcommunity9/10

    Working Copy's manual explicitly states support for https, ssh, git, and http protocols, plus SSH key management via Secure Enclave and identity attachment for authentication, and community evidence confirms real-world clone/pull/push usage over GitHub. Missing for 10: independent hands-on verification of the raw git:// protocol specifically and no dedicated troubleshooting/edge-case documentation.

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

15. power-userVisualize the full commit graph across branches

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product; visualizing git commit graphs is entirely outside its category and unrelated to any of its documented features.

    ⚑ flag

    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

16. developerCommit and push changes directly from my device

    weight 3 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product, not a git or source-control tool; committing and pushing code is entirely outside its category (wrong axis).

    ⚑ flag

    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

17. power-userSign my commits with a GPG or SSH key for verification

    weight 1 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product, not a git or code-signing tool; signing commits with GPG/SSH keys is entirely outside its product category.

    ⚑ flag

    Working Copy—none0/10

    Evidence shows Working Copy uses SSH keys (including Secure Enclave-backed keys) for authenticating to remotes, but nothing in the docs describes GPG or SSH commit signing/verification as a feature. Missing for 10: any mention of signed commits, GPG key support, or SSH-signature verification workflow.

    • [claimed-docs] “SSH keys can reside on the Secure Enclave protected by Face ID or Touch ID.”
    • [claimed-docs] “You attach a private key to your Identity which can be imported or generated inside the app.”

    proof ↗⚑ flag

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

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product, not a version control tool; interactive git history rewriting is entirely outside its category.

    ⚑ flag

    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

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

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product; merge conflict resolution is a git/code-editing capability entirely outside its category.

    ⚑ flag

    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

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

    weight 3 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN tool; creating pull requests on Git platforms is a source-control feature entirely outside its category — this is a wrong-axis question, not a missing capability.

    ⚑ flag

    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

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

    weight 3 · not comparable
    Tailscalen/a

    Tailscale is a network connectivity/VPN tool; reviewing pull requests is a git-hosting/code-review workflow entirely outside its product category. It could enable mobile access to a self-hosted git server, but that's a stretch not evidenced, and the axis itself is a wrong-category fit for a networking product.

    ⚑ flag

    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

22. power-userStash and unstash changes to temporarily clear my working directory

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product with no git or version control functionality; git stash/unstash is entirely outside its product category.

    ⚑ flag

    Working Copy✓fullclaimed8/10

    Official docs explicitly confirm stash/unstash via the repository context menu, directly matching the story's core requirement. Missing for 10: independent hands-on corroboration of the stash workflow beyond vendor docs.

    • [claimed-docs] “You Stash and Unstash from the context menu of repositories.”

    proof ↗⚑ flag

23. power-userClone, update, and manage Git submodules within a repository

    weight 1 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN tool, not a Git or version-control product; managing Git submodules is entirely outside its category and not a fair axis for it.

    ⚑ flag

    Working Copy~partialclaimed5/10

    Working Copy's docs explicitly mention Git submodule support, confirming the feature exists, but there is no detail on cloning with submodules, updating them, or managing (add/remove/sync) submodules, nor any community corroboration of real-world submodule workflows. missing for 10: documented submodule clone/update/init workflow, UI for managing submodule paths, independent user confirmation of submodule handling.

    • [claimed-docs] “Git submodules allow you to include other Git repositories within your repository, keeping their histories separate.”

    proof ↗⚑ flag

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

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN tool; live-reload preview of Markdown/HTML files is a code-editor/IDE feature, entirely outside its product category.

    ⚑ flag

    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

25. power-userRoute all my internet traffic through a specific device on my network using an exit node

    weight 2 · not comparable
    Tailscale✓fullcommunity8/10

    First-party docs explicitly document exit nodes for routing all internet traffic through a specific device, and community evidence corroborates real-world use of exit nodes (e.g., using a home exit node to bypass geo-blocking). Missing for 10: independent hands-on walkthrough of exit-node setup/performance and more detail on configuration nuances.

    • [claimed-docs] “Route all internet traffic through a specific device on your network.”
    • [community] “I was once in South Africa and needed to look up my prescriptions in the CVS app... CVS geoblocked me. Luckily I had a TailScale exit node r…”

    proof ↗⚑ flag

    Working Copyn/a

    Working Copy is a Git client for iOS; exit-node/network-routing capability is unrelated to its product category (a Git repository management app), not a Git or VPN networking feature.

    ⚑ flag

26. developerGet secure infrastructure access to resources wherever they live, including Kubernetes clusters

    weight 3 · not comparable
    Tailscale✓fullcommunity8/10

    First-party docs explicitly claim infrastructure access 'wherever your resources live, including Kubernetes clusters,' with auditable SSH/K8s/database access, subnet routers, and infra-as-code integrations, and community testimonials corroborate managing home k8s clusters and SSH access remotely. Missing for 10: independent hands-on validation specifically of Kubernetes access (only a generic homelab testimonial), and no detailed K8s-operator documentation excerpt beyond marketing claims.

    • [claimed-docs] “Infrastructure access to wherever your resources live, including Kubernetes clusters”
    • [claimed-docs] “Auditable access to SSH, K8s, databases, and more.”
    • [claimed-docs] “I now can manage my home NAS and my home k8s cluster…from my phone!”
    • [claimed-docs] “Use subnet routers to give devices outside your local network access to services within specific subnets.”
    • [claimed-docs] “Automate your tailnet using infrastructure-as-code providers, webhooks, and other integrations.”
    • [community] “Tailscale is my favorite (product) discovery of 2022... SSH'ing into a raspberry pi, accessing dev servers from other devices, giving access…”

    proof ↗⚑ flag

    Working Copyn/a

    Working Copy is a Git client for iOS focused on repository management; it has no relevance to infrastructure access or Kubernetes clusters — this is a category mismatch, not a missing feature.

    ⚑ flag

27. developerUse subnet routers to reach devices outside my local network as if I were on it

    weight 2 · not comparable
    Tailscale✓fullcommunity9/10

    Tailscale's docs explicitly describe subnet routers giving devices outside the local network access to services within specific subnets, plus broader infrastructure access (Kubernetes, SSH, cloud/on-prem) and community hands-on confirmation of SSH'ing into remote boxes and managing home NAS/k8s clusters as if local. Missing for 10: independent third-party benchmark or detailed hands-on walkthrough specifically of subnet router setup (rather than general VPN/exit-node use).

    • [claimed-docs] “Use subnet routers to give devices outside your local network access to services within specific subnets.”
    • [claimed-docs] “Auditable access to SSH, K8s, databases, and more.”
    • [claimed-docs] “Across clouds or on-prem, Tailscale’s mesh overlay network connects it all.”
    • [claimed-docs] “just SSH'ed into my boxes, building code and pushing configs around like I'm home”
    • [claimed-docs] “I now can manage my home NAS and my home k8s cluster…from my phone!”
    • [community] “Tailscale is my favorite (product) discovery of 2022... SSH'ing into a raspberry pi, accessing dev servers from other devices, giving access…”

    proof ↗⚑ flag

    Working Copyn/a

    Working Copy is a Git client for iOS; subnet routing/VPN-style network access to reach remote devices is entirely outside its product category (a wrong axis, not a missing feature).

    ⚑ flag

28. developerAccess and work with files and repositories from other apps' sandboxes on my device

    weight 2 · not comparable
    Tailscalen/a

    This story concerns sandboxed app file/repo access (an OS-level app-sandbox interoperability concern), which is unrelated to Tailscale's category as a mesh VPN/networking tool for device and service connectivity — wrong axis for this product type.

    ⚑ flag

    Working Copy✓fullclaimed8/10

    Working Copy explicitly integrates with the iOS Files app and other apps' sandboxes: repositories appear in the Files app/document picker for 3rd party apps, external directories/document packages from other apps can be linked, files can be dragged in from email/other apps, and a built-in WebDAV server plus Shortcuts automation enable cross-app file flow. This directly matches accessing/working with files and repos across app sandboxes on-device. Missing for 10: independent hands-on verification of cross-app sandbox access beyond vendor docs.

    • [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

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

    weight 3 · not comparable
    Tailscalen/a

    Tailscale is a network connectivity/VPN product, not a data-store or content-authoring platform; the notion of 'exporting all my data in open formats and leaving' does not apply to its category — this is a wrong axis rather than a missing feature.

    ⚑ flag

    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

30. ai-native userSelf-host the core product

    weight 3 · not comparable
    Tailscale—none0/10

    No vendor documentation claims a self-hostable control server; multiple independent community comments explicitly note Tailscale's coordination/control server is closed-source and cannot be self-hosted, with users citing this as a trust/lock-in concern.

    • [community] “Am I the only one that has an issue with a VPN that I can't self host? Presumably if Tailscale get's PWN'd or subpoenaed then your network i…”
    • [community] “we're all meant to be happy giving full control of our entire network to a commercial company running a closed source command and control se…”
    • [community] “As soon as Tailscale provides option for Wireguard preshared keys, I will use it. I need Tailscale out of my network... Self hosting Tailsca…”

    proof ↗⚑ flag

    Working Copyn/a

    Working Copy is a proprietary iOS git client app distributed via App Store, not a server/platform that could be self-hosted; self-hosting the 'core product' is a category error for this type of client application.

    ⚑ flag

31. ai-native userChoose where my data is stored (region/residency)

    weight 2 · not comparable
    Tailscale—none0/10

    Tailscale is a mesh VPN/networking product; the evidence pack contains nothing about choosing a data storage region or data residency controls for user data/AI content. This is a plausible axis for privacy-conscious SaaS-style products, but there is no documentation of regional data storage or residency options, so it is 'none' rather than 'na'.

    ⚑ flag

    Working Copyn/a

    Working Copy is a local iOS Git client where users choose their own Git remote/server (GitHub, GitLab, self-hosted, etc.); it does not offer a managed data-residency/region selection feature of its own, making this a category error for a client app rather than a hosted service.

    ⚑ flag

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

    weight 3 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN mesh product, not an AI model provider or data processor that trains AI models; the axis of preventing data use for AI training is a category error for this product type.

    ⚑ flag

    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

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

    weight 3 · not comparable
    Tailscalen/a

    Tailscale is a network connectivity/VPN product, not an AI agent or code-analysis tool; analyzing PRs and suggesting code improvements is entirely outside its category. It could at most provide network access to reach such an agent, but that's a different axis from the story itself.

    ⚑ flag

    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

34. ai-native userGet AI-generated commit message suggestions based on my staged changes

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product, not a coding tool or git assistant; AI-generated commit message suggestions are entirely outside its product category and wrong axis for this type of product.

    ⚑ flag

    Working Copy✓fullclaimed8/10

    Working Copy's docs explicitly state it can suggest commit messages using AI based on staged diffs, sent to OpenAI, directly matching the story. Missing for 10: independent/hands-on corroboration of this specific AI commit-message feature and details on accuracy/configuration options.

    • [claimed-docs] “includes the ability to suggest messages using artificial intelligence. These AI suggestions require sending staged differences to OpenAI”

    proof ↗⚑ flag

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

    weight 3 · not comparable
    Tailscalen/a

    Tailscale is a network connectivity/VPN product, not a coding agent or repository tool; browsing/editing/committing/pushing code is entirely outside its product category — this is a wrong-axis question, not a gap in its networking feature set.

    ⚑ flag

    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

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

    weight 3 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product; assigning issues to AI coding agents and receiving pull requests is entirely outside its category — this is a wrong-axis question, not a capability gap.

    ⚑ flag

    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

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

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product; conversing with an AI agent about repository/PR insights is entirely outside its category (wrong axis), not something Tailscale's evidence pack even attempts to address.

    ⚑ flag

    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

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

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a network connectivity/VPN mesh product, not a coding-agent task management or tracking tool; nothing in the evidence relates to managing or tracking cloud-based coding agent tasks, only network access from devices including phones.

    ⚑ flag

    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

39. ai-native userDescribe what I want in plain language and have the tool generate the corresponding shell command

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product, not a natural-language-to-command generation tool; this axis is a category error for its product type.

    ⚑ flag

    Working Copyn/a

    Working Copy is a mobile Git GUI client with no shell/command-line interface; the natural-language-to-shell-command axis is a category error for this product. Its Repository Agent performs actions directly via conversation rather than generating shell commands.

    ⚑ flag

40. developerStore credentials once in a secure vault and reference them from multiple hosts

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN mesh product, not a secrets/credentials vault; the evidence pack shows it provides secure network access (SSH, Kubernetes, subnet routing) but no capability for storing or referencing credentials/secrets. This story is a category error for this product type.

    ⚑ flag

    Working Copy~partialclaimed5/10

    Working Copy supports secure credential storage via Identities (SSH keys stored in the Secure Enclave, protected by Face ID/Touch ID, and can be imported/generated) and supports connecting to many host types (GitHub Enterprise, GitLab, Gitea, BitBucket, etc.), implying credentials could be reused. However, there is no explicit documentation confirming one Identity/credential can be attached to and reused across multiple different repositories or hosts simultaneously, nor any independent verification of this workflow. Missing for 10: explicit multi-host credential reuse documentation, independent/hands-on confirmation of cross-host credential sharing.

    • [claimed-docs] “SSH keys can reside on the Secure Enclave protected by Face ID or Touch ID.”
    • [claimed-docs] “You attach a private key to your Identity which can be imported or generated inside the app.”
    • [claimed-docs] “Working Copy supports private instances of GitHub Enterprise, GitLab and Gitea.”

    proof ↗⚑ flag

41. power-userStore my SSH keys in a hardware-backed secure enclave protected by biometrics

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a mesh networking/VPN product; hardware-backed secure enclave storage for SSH keys protected by biometrics is a credential-management/OS-security feature outside its product category, not something a networking tool ships.

    ⚑ flag

    Working Copy✓fullclaimed8/10

    Working Copy's documentation explicitly states SSH keys can reside on the Secure Enclave protected by Face ID or Touch ID, directly matching the story's hardware-backed, biometric-protected key storage requirement. Missing for 10: independent/hands-on corroboration of this specific feature beyond first-party docs.

    • [claimed-docs] “SSH keys can reside on the Secure Enclave protected by Face ID or Touch ID.”
    • [claimed-docs] “You attach a private key to your Identity which can be imported or generated inside the app.”

    proof ↗⚑ flag

42. developerEdit files with a terminal-based editor and run syntax/lint checkers inside the app

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product providing connectivity (SSH, subnet routing, mesh network); it is not an editor, IDE, or code-quality tool and does not provide in-app terminal editing or lint/syntax checking. This is a wrong-axis story for the product category.

    ⚑ flag

    Working Copy—none0/10

    Working Copy is a Git client for iOS with syntax-highlighted file viewing and editing, but there is no evidence of a terminal-based editor or any integrated syntax/lint checker execution inside the app — no shell, no linting tools, no build/check runner mentioned anywhere in the docs.

    ⚑ flag

43. developerInstall additional pure-Python packages using pip directly on my device

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product; installing pip packages is a local development environment concern unrelated to network connectivity, which is entirely outside its category.

    ⚑ flag

    Working Copyn/a

    Working Copy is a Git client for iOS with no terminal, shell, or Python runtime — installing pip packages is entirely outside its product category (a git/file-management app, not a code execution or package management environment).

    ⚑ flag

44. power-userGroup multiple terminal sessions together and broadcast the same command to all of them

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN product providing connectivity between devices; it has no terminal multiplexing or broadcast-command-to-multiple-sessions feature, and grouping terminal sessions is a wrong axis for a mesh-networking tool, not a networking capability gap.

    ⚑ flag

    Working Copyn/a

    Working Copy is a Git client for iOS, not a terminal/SSH multiplexer; grouping terminal sessions and broadcasting commands is outside its product category entirely.

    ⚑ flag

45. developerTransfer files to and from remote hosts via scp and sftp using my configured keys

    weight 2 · not comparable
    Tailscale~partialcommunity5/10

    Tailscale provides standard IP connectivity between devices so any TCP-based tool including scp/sftp over SSH should work using normal SSH keys, and evidence confirms SSH access to boxes (tailscale-docs-6, tailscale-docs-7, tailscale-comm-1). However, there is no explicit mention of scp/sftp usage, and community reports specifically flag file-transfer performance overhead as a real drawback (tailscale-comm-7), which is directly relevant to this story's file-transfer use case. Missing for 10: explicit scp/sftp documentation or examples, confirmation that key-based auth flows unchanged, and resolution of the noted file-transfer performance complaints.

    • [claimed-docs] “Auditable access to SSH, K8s, databases, and more.”
    • [claimed-docs] “just SSH'ed into my boxes, building code and pushing configs around like I'm home”
    • [community] “Tailscale is my favorite (product) discovery of 2022... SSH'ing into a raspberry pi, accessing dev servers from other devices, giving access…”
    • [community] “I love tailscale, but the performance overhead on file transfer (my primary use case for it) is very real. Samba transfers take a 15 megabyt…”

    proof ↗⚑ flag

    Working Copyn/a

    Working Copy is a Git client for iOS that supports git-over-ssh and SSH keys for authentication, but there is no evidence it offers general scp/sftp file transfer to arbitrary remote hosts — this is a Git-specific tool, not a general SSH file-transfer utility, making the scp/sftp axis a category mismatch.

    ⚑ flag

46. developerRun local UNIX commands like ls, grep, cat, tar, and curl directly in the app

    weight 3 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN mesh product, not a terminal/agent app with a built-in shell; running local UNIX commands like ls/grep/tar/curl inside 'the app' is a category error for this product type — it enables SSH connectivity to remote machines but does not itself execute local shell commands.

    ⚑ flag

    Working Copy—none0/10

    Working Copy is a git client for iOS with file browsing, syntax highlighting, and Shortcuts automation, but there is no evidence of a terminal or shell environment allowing execution of UNIX commands like ls, grep, cat, tar, or curl.

    ⚑ flag

47. power-userOpen multiple terminal sessions, each with its own context, appearance, and history

    weight 3 · not comparable
    Tailscalen/a

    Tailscale is a networking/VPN mesh product, not a terminal emulator or SSH client with session/appearance/history management — multi-session terminal UX is a wrong-axis question for this category of product.

    ⚑ flag

    Working Copyn/a

    Working Copy is a git client for iOS with no terminal/SSH-session feature; the story's axis of multiple terminal sessions with distinct context/appearance/history is a category error for this product type, which manages git repos rather than shell sessions.

    ⚑ flag

48. power-userKeep my terminal session alive across network changes and device sleep

    weight 3 · not comparable
    Tailscale~partialcommunity3/10

    Evidence shows Tailscale is commonly used to SSH into always-reachable devices (docs-7, comm-1) via a stable mesh network, which implies some resilience, but there is no explicit evidence that an active terminal session survives network changes or device sleep (e.g., no mosh-like session persistence claim). Community reports also note connectivity breakage from ISPs/guest wifi blocking Tailscale ports and NAT traversal failures (comm-11, comm-10), casting doubt on seamless roaming. missing for 10: explicit documentation or hands-on test of session persistence across network/device changes, confirmation of roaming behavior during sleep/wake cycles.

    • [claimed-docs] “just SSH'ed into my boxes, building code and pushing configs around like I'm home”
    • [community] “Tailscale is my favorite (product) discovery of 2022... SSH'ing into a raspberry pi, accessing dev servers from other devices, giving access…”
    • [community] “Tailscale is becoming less useful as network providers become hostile to it. Last week I noticed McDonalds guest wifi is blocking new connec…”
    • [community] “If you have more complex cases, the IPTables/Netfilter rules make it vastly more difficult to manage... They've also broken features I relie…”

    proof ↗⚑ flag

    Working Copyn/a

    Working Copy is a Git client for iOS; it has no interactive terminal/SSH session feature to keep alive across network changes or sleep — this is a category error for this product type.

    ⚑ flag

49. power-userCustomize the font, colors, and cursor appearance of my terminal and persist the settings

    weight 2 · not comparable
    Tailscalen/a

    Tailscale is a VPN/networking product, not a terminal or CLI application with UI customization features; terminal appearance settings are entirely outside its product category.

    ⚑ flag

    Working Copyn/a

    Working Copy is a mobile Git client with a file/diff viewer, not a terminal emulator; there is no terminal interface to customize font, colors, or cursor appearance. This axis is a category error for this product type.

    ⚑ flag