Skip to content
ProductArena

Blink Shell vs Working Copy

open-source · freemium · subscription-flat · credits

·

freemium · one-time-license

Working Copy wins · 5–7 (10 drawn)

Blink ShellAGENT-READY0/100BUILT-IN AI n/a
Agenticness
AGENT-READY4/100BUILT-IN AI52/100Working Copy

Agenticness — how well agents can access and operate the productAgenticness

How well agents can access and operate the product

Agent access

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

    weight 2 · round drawn
    Blink Shellnone0/10

    Probe confirms no llms.txt exists (404) and no agent-oriented API docs are found; Blink Shell is a terminal/SSH client with no evidence of agent-friendly documentation.

    • [probe] “PROBE llms.txt: HTTP 404 at https://docs.blink.sh/llms.txt”
    • [probe] “PROBE openapi: all candidate paths 404 (https://docs.blink.sh/openapi.json, https://docs.blink.sh/swagger.json, https://docs.blink.sh/api/op…”
    proof ↗⚑ flag
    Working Copynone0/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

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

    weight 3 · round to Working Copy
    Blink Shellnone0/10

    No public API or SDK is documented; probes for llms.txt and OpenAPI/Swagger specs all returned 404, and no evidence pack item describes a programmatic/API interface for driving Blink Shell.

    • [probe] “PROBE llms.txt: HTTP 404 at https://docs.blink.sh/llms.txt”
    • [probe] “PROBE openapi: all candidate paths 404 (https://docs.blink.sh/openapi.json, https://docs.blink.sh/swagger.json, https://docs.blink.sh/api/op…”
    proof ↗⚑ flag
    Working Copypartialprobed3/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

Api quality

  1. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

    weight 2 · round drawn
    Blink Shellnone0/10

    Blink Shell is a terminal/SSH client, not an API-providing service, but the axis was probed and no machine-readable API spec exists — probes show 404 for llms.txt and all OpenAPI/swagger candidate paths, and no docs mention any API spec.

    • [probe] “PROBE llms.txt: HTTP 404 at https://docs.blink.sh/llms.txt”
    • [probe] “PROBE openapi: all candidate paths 404 (https://docs.blink.sh/openapi.json, https://docs.blink.sh/swagger.json, https://docs.blink.sh/api/op…”
    proof ↗⚑ flag
    Working Copynone0/10

    Probes explicitly show no OpenAPI/swagger spec exists at any candidate path and no llms.txt or machine-readable docs are available; Working Copy exposes Shortcuts automation and an x-callback-url scheme but no documented downloadable API spec.

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

Automation depth — how much of the product can run unattendedAutomation depth

How much of the product can run unattended

  1. ai-native userDefine rules that trigger actions automatically on events

    weight 3 · round to Working Copy
    Blink Shellnone0/10

    No evidence Blink Shell supports defining rules or triggers for automated actions on events; it is a terminal/SSH/Mosh client with no automation-rule engine documented.

      ⚑ flag
      Working Copypartialclaimed4/10

      Working Copy supports Shortcuts app automation where files/data flow between actions, which allows building event-triggered workflows via iOS Shortcuts automations (e.g., time/location/app triggers), but there's no first-party rule engine or documented event-trigger system within Working Copy itself. missing for 10: native event/rule triggers inside the app, documented automation-on-git-events (e.g. auto-commit/push on file change), examples of Shortcuts automations actually wired to Working Copy triggers.

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

    • ai-native userSchedule recurring jobs or workflows

      weight 2 · round drawn
      Blink Shellnone0/10

      Blink Shell is a terminal/SSH/Mosh client; there is no evidence of any scheduling, cron-like, or recurring workflow/job automation capability in the docs or community discussion.

        ⚑ flag
        Working Copynone0/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

        Git code — core git and code operations — cloning, branching, pushing, code browsingGit code

        Core git and code operations — cloning, branching, pushing, code browsing

        Repo management

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

          weight 3 · round to Working Copy
          Blink Shellnone0/10

          Blink Shell's documented built-in commands (cat, grep, wc, cd, ls, etc.) do not include git, and no evidence pack item shows native git clone support over HTTPS, SSH, or git protocol; it only documents scp/sftp for file transfer and ssh/mosh for remote sessions, implying git operations would need to happen on a remote server, not natively in Blink.

          • [claimed-docs] “cat, grep, wc, cd, setenv, ls, touch, cp, rm, ln, mv, mkdir, rmdir, df, du”
          • [github] “scp user@host.name.edu:filename . sftp localFilename user@host.name.edu:~/”
          proof ↗⚑ flag
          Working Copyfullcommunity9/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

        2. developerCommit and push changes directly from my device

          weight 3 · round to Working Copy
          Blink Shellpartialclaimed5/10

          Blink is an SSH/Mosh terminal client that connects to remote hosts (including VS Code servers, GitHub Codespaces, GitPod) where a developer could run git commands, but the evidence never mentions git itself, a git client, or any explicit commit/push workflow — it's an indirect capability via a generic shell rather than a documented feature. missing for 10: explicit mention of git support, any documented git commit/push workflow, hands-on confirmation of using git from within Blink.

          • [claimed-docs] “A coding experience fitted to your device, that connects to Microsoft Visual Studio Code for web, GitHub Codespaces, GitPod or your own VS C…”
          • [claimed-docs] “Work on local projects, or seamlessly on remote machines thanks to Blink Files.”
          • [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
          • [claimed-docs] “cat, grep, wc, cd, setenv, ls, touch, cp, rm, ln, mv, mkdir, rmdir, df, du”
          proof ↗⚑ flag
          Working Copyfullcommunity8/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

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

          weight 1 · round drawn
          Blink Shellnone0/10

          Blink Shell is an SSH/Mosh terminal client; evidence covers SSH key pair generation for server login, but there is no mention of GPG or SSH commit signing for git operations anywhere in the docs or community discussion.

            ⚑ flag
            Working Copynone0/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

          • developerReview pull requests from my phone while on the go

            weight 3 · round drawn
            Blink Shellpartialclaimed4/10

            Blink Shell is a mobile terminal/SSH client that lets developers connect to remote dev environments (SSH, Mosh, VS Code for web, GitHub Codespaces, GitPod) where command-line git tools or web-based review could be used, but the evidence pack never mentions git, GitHub, gh CLI, or any PR-review-specific feature. This is a generic terminal capability stretched to cover the story rather than a documented PR-review workflow. Missing for 10: explicit git/GitHub CLI support, PR/diff viewing UI or workflow, mobile-optimized review tooling, and any user/community confirmation of doing PR reviews via Blink.

            • [claimed-docs] “A coding experience fitted to your device, that connects to Microsoft Visual Studio Code for web, GitHub Codespaces, GitPod or your own VS C…”
            • [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
            • [claimed-docs] “Work on local projects, or seamlessly on remote machines thanks to Blink Files.”
            proof ↗⚑ flag
            Working Copypartialcommunity4/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

          Networking access — stories about networking access in this arenaNetworking access

          Stories about networking access in this arena

          Mesh network

          1. power-userConnect directly to my servers without relying on a cloud relay, proxy, or VPN

            weight 2 · round drawn
            Blink Shellfullcommunity8/10

            Blink Shell is a direct SSH/Mosh client built on libssh, connecting straight to hosts via hostname/user with no cloud relay or VPN required, and this is corroborated by community reviews praising its solid direct connectivity and open-source transparency. Missing for 10: independent technical audit confirming no telemetry/relay involvement, and no explicit statement ruling out any proxy usage.

            • [claimed-docs] “In Blink type mosh [user@]hostname. For example : mosh irwin@irwinvb.”
            • [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
            • [claimed-docs] “Hosts: create hosts that can be accessed with only the hostname.”
            • [claimed-docs] “Supports Ed25519, ECDSA and RSA keys. It is built on top of libssh and libssh2.”
            • [community] “Been using it (beta testing on iPhone and paid version on iPad so I can compare) for a while. Improving steadily, solid connectivity. So far…”
            • [community] “Bought it even though it apparently has no agent forwarding... Pretty good, refresh seems faster than Prompt, especially when using htop and…”
            proof ↗⚑ flag
            Working Copyfullcommunity8/10

            Working Copy documents direct git/ssh/https protocol support, including private self-hosted GitHub Enterprise, GitLab, and Gitea instances, with SSH keys stored in Secure Enclave — all indicating direct, non-relay connections to user-controlled servers. Community evidence shows users pairing it with self-hosted VPS git servers, corroborating real-world direct-connection use. missing for 10: independent technical verification that no intermediary/relay is used during sync, and explicit confirmation of raw SSH/git protocol (not tunneled) from a third party.

            • [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] “Working Copy supports private instances of GitHub Enterprise, GitLab and Gitea.”
            • [claimed-docs] “You attach a private key to your Identity which can be imported or generated inside the app.”
            • [community] “I ended up not wanting to put my years of thinking, planning and researching up on a public service, so I spun up a $5/month VPS instance fr…”
            proof ↗⚑ flag

          Offline sync — stories about offline sync in this arenaOffline sync

          Stories about offline sync in this arena

          Cross device sync

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

            weight 2 · round to Working Copy
            Blink Shellpartialclaimed4/10

            Blink Files (docs-8) enables working with local and remote projects, and drag-and-drop selection lets users move content to/from other apps (docs-16), suggesting some file interoperability with other apps' sandboxes, but there's no explicit documentation of Files-app document-provider integration or direct access to another app's sandboxed storage/repos. missing for 10: explicit Files app/document-provider integration details, concrete examples of accessing another app's sandbox, independent corroboration of this capability.

            • [claimed-docs] “Work on local projects, or seamlessly on remote machines thanks to Blink Files.”
            • [claimed-docs] “To start selection mode, Tap and drag. You can drag selections to other apps, or from other apps into Blink.”
            proof ↗⚑ flag
            Working Copyfullclaimed8/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

          2. power-userSync my saved hosts and connection settings across all my devices

            weight 2 · round drawn
            Blink Shellnone0/10

            There is no evidence of cross-device sync for hosts/settings; in fact a community comment explicitly requests this feature ('Could you consider adding config sync via iCloud/Dropbox? It's quite a pain to sync host lists across several iOS devices'), indicating it was not available.

            • [community] “Could you consider adding config sync via iCloud/Dropbox? It's quite a pain to sync host lists across several iOS devices.”
            proof ↗⚑ flag
            Working Copynone0/10

            Working Copy is a single-device iOS git client; the evidence pack contains no mention of any cross-device sync feature (e.g. iCloud sync of hosts/identities/keys) for saved hosts or connection settings across devices, only per-repository git operations, SSH key storage in Secure Enclave, and file access mechanisms.

              ⚑ flag

            Openness — open source, data portability, and self-hosting storiesOpenness

            Open source, data portability, and self-hosting stories

            1. ai-native userRead the product's source under an open license

              weight 2 · round to Blink Shell
              Blink Shellpartialcommunity5/10

              GitHub repo (blinksh/blink) is publicly available and community notes describe it as an open-source development process on GitHub, but the license itself is disputed—one commenter questions GPL compatibility with the App Store, and no evidence pack item explicitly names or confirms an OSI-approved open license for the source. missing for 10: explicit license file/name confirmation, resolution of the GPL/App Store tension, first-party statement of licensing terms.

              • [github] “If you would like to participate on its development, we would love to have you on board! There are two ways to collaborate with the project:…”
              • [community] “The way in which Blink really blows the competition (e.g. Prompt) out of the water is its open source development process... Carlos [is] hig…”
              • [community] “I thought GPL was incompatible with the App Store? Wasn't VLC famously pulled from the App Store over a complaint about this?”
              proof ↗⚑ flag
              Working Copynone0/10

              Working Copy is a closed-source commercial iOS app; no evidence indicates its source code is available under any open license, and no repository or license file is mentioned anywhere in the evidence pack.

                ⚑ flag

              Privacy posture — data-handling and privacy storiesPrivacy posture

              Data-handling and privacy stories

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

                weight 2 · round drawn
                Blink Shellnone0/10

                No evidence in the pack mentions telemetry, analytics, usage tracking, or any opt-out/privacy settings for Blink Shell; the evidence is entirely about SSH/Mosh features, UI, and community feedback unrelated to data collection.

                  ⚑ flag
                  Working Copynone0/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

                  Security — security posture and hardening storiesSecurity

                  Security posture and hardening stories

                  Credential protection

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

                    weight 2 · round to Working Copy
                    Blink Shellnone0/10

                    No evidence anywhere in the pack mentions Face ID, Touch ID, biometric authentication, or fingerprint-based unlock/authentication for Blink Shell; the security features documented are SSH key types and password-less key auth only.

                    • [claimed-docs] “Supports Ed25519, ECDSA and RSA keys. It is built on top of libssh and libssh2.”
                    • [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
                    proof ↗⚑ flag
                    Working Copypartialclaimed6/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

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

                    weight 2 · round drawn
                    Blink Shellpartialclaimed5/10

                    Blink documents separate 'Keys' and 'Hosts' management features, implying SSH keys can be created once and associated with host entries for password-less access, which aligns with a credential-vault-and-reuse pattern. However, there is no explicit documentation confirming a single stored key can be referenced across multiple distinct hosts, no mention of encryption-at-rest or vault security guarantees, and no independent/community confirmation of this specific reuse workflow. Missing for 10: explicit multi-host key reuse documentation, vault security/encryption details, and independent corroboration of the workflow.

                    • [claimed-docs] “Hosts: create hosts that can be accessed with only the hostname.”
                    • [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
                    • [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
                    proof ↗⚑ flag
                    Working Copypartialclaimed5/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

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

                    weight 2 · round to Working Copy
                    Blink Shellnone0/10

                    Evidence shows Blink Shell supports creating SSH key pairs (docs-12) but there is no mention of hardware-backed secure enclave storage or biometric protection for keys anywhere in the docs, GitHub, or community discussion.

                    • [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
                    proof ↗⚑ flag
                    Working Copyfullclaimed8/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

                  Terminal ssh — terminal and SSH workflows — shells, sessions, remote accessTerminal ssh

                  Terminal and SSH workflows — shells, sessions, remote access

                  Local dev environment

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

                    weight 2 · round drawn
                    Blink Shellnone0/10

                    Blink Shell is documented as an SSH/mosh terminal with a small set of built-in local commands (cat, grep, wc, cd, ls, etc.) and its 'coding experience' feature explicitly delegates editing to external VS Code servers/Codespaces/Gitpod rather than a built-in terminal editor. No evidence describes a bundled terminal-based text editor (e.g., vim/nano) or any built-in syntax/lint checking capability inside the app itself.

                    • [claimed-docs] “cat, grep, wc, cd, setenv, ls, touch, cp, rm, ln, mv, mkdir, rmdir, df, du”
                    • [claimed-docs] “A coding experience fitted to your device, that connects to Microsoft Visual Studio Code for web, GitHub Codespaces, GitPod or your own VS C…”
                    • [claimed-docs] “Work on local projects, or seamlessly on remote machines thanks to Blink Files.”
                    proof ↗⚑ flag
                    Working Copynone0/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

                    Ssh connections

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

                      weight 3 · round to Blink Shell
                      Blink Shellpartialclaimed6/10

                      Docs explicitly list built-in commands including ls, grep, cat, cd, touch, cp, rm, mv, mkdir, df, du (blink-shell-docs-4) and file transfer via scp/sftp (blink-shell-gh-1), covering much of the 'run local UNIX commands' story. However, tar and curl are never mentioned anywhere in the evidence pack, so support for those specific commands is unconfirmed. missing for 10: explicit documentation or confirmation that tar and curl are supported as local commands, independent hands-on verification of command behavior.

                      • [claimed-docs] “cat, grep, wc, cd, setenv, ls, touch, cp, rm, ln, mv, mkdir, rmdir, df, du”
                      • [github] “scp user@host.name.edu:filename . sftp localFilename user@host.name.edu:~/”
                      proof ↗⚑ flag
                      Working Copynone0/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

                      • developerConnect to remote servers using SSH with Ed25519, ECDSA, or RSA keys

                        weight 3 · round to Blink Shell
                        Blink Shellfullcommunity9/10

                        Docs explicitly confirm support for Ed25519, ECDSA, and RSA keys via libssh/libssh2, with key pair creation and hostname-based ssh usage documented, and community discussion corroborates Ed25519 support as a differentiator from competitors. Missing for 10: independent hands-on verification of ECDSA/RSA specifically (community focus is mostly on Ed25519).

                        • [claimed-docs] “Supports Ed25519, ECDSA and RSA keys. It is built on top of libssh and libssh2.”
                        • [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
                        • [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
                        • [community] “Does it support Ed25519 keys? This is one of the things that Panic's Prompt still lack support of, and I really miss it.”
                        proof ↗⚑ flag
                        Working Copypartialclaimed5/10

                        Docs confirm SSH remote support and private-key based Identities (importable or generated, storable in Secure Enclave), but no evidence specifies which key algorithms (Ed25519, ECDSA, RSA) are supported. Missing for 10: explicit documentation of supported key types/algorithms, independent confirmation of SSH auth working with each key type.

                        • [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.”
                        • [claimed-docs] “SSH keys can reside on the Secure Enclave protected by Face ID or Touch ID.”
                        proof ↗⚑ flag

                      • power-userGenerate SSH key pairs for password-less access to my servers

                        weight 2 · round to Blink Shell
                        Blink Shellfullcommunity9/10

                        Official docs explicitly describe the 'Keys' feature for creating SSH key pairs for password-less server access, supporting Ed25519, ECDSA, and RSA, corroborated by community discussion confirming Ed25519 support (a differentiator vs competitors). Missing for 10: independent hands-on verification of the key-generation UX itself beyond docs description.

                        • [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
                        • [claimed-docs] “Supports Ed25519, ECDSA and RSA keys. It is built on top of libssh and libssh2.”
                        • [community] “Does it support Ed25519 keys? This is one of the things that Panic's Prompt still lack support of, and I really miss it.”
                        proof ↗⚑ flag
                        Working Copyfullclaimed7/10

                        Working Copy's docs state you attach a private key to an Identity which can be 'imported or generated inside the app,' and that SSH keys can be stored in the Secure Enclave protected by Face ID/Touch ID, directly enabling password-less SSH access to git servers. Missing for 10: independent/hands-on confirmation of the keygen flow and details on supported key types/algorithms.

                        • [claimed-docs] “You attach a private key to your Identity which can be imported or generated inside the app.”
                        • [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”
                        proof ↗⚑ flag

                      • power-userConnect to a saved host with one tap without re-entering credentials

                        weight 2 · round to Blink Shell
                        Blink Shellfullclaimed7/10

                        Docs confirm saved 'Hosts' allow access via just hostname, SSH key pairs enable password-less login, and connections persist through sleep/network changes via Mosh — together supporting one-tap reconnection to saved hosts without re-entering credentials. missing for 10: no explicit demonstration of a literal one-tap UI flow, and no independent hands-on account specifically validating passwordless saved-host connection.

                        • [claimed-docs] “Hosts: create hosts that can be accessed with only the hostname.”
                        • [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
                        • [claimed-docs] “don't be afraid to put your device to sleep, when you wake it up later, your connections will be intact.”
                        • [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
                        proof ↗⚑ flag
                        Working Copypartialclaimed5/10

                        Working Copy stores SSH identities/keys (optionally in Secure Enclave protected by Face ID/Touch ID) attached to a repository, which implies reconnecting to a saved remote doesn't require re-entering credentials, but this is git-remote SSH, not an interactive terminal session, and there's no explicit documentation of a one-tap 'connect to saved host' action or session reuse UI. Missing for 10: explicit one-tap host connection flow, interactive terminal/shell access evidence, and independent confirmation of credential-free reconnect behavior.

                        • [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 https, ssh, git, and http protocols”
                        proof ↗⚑ flag

                      Not comparable on these axes

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

                        weight 2 · not comparable
                        Blink Shelln/a

                        Blink Shell is an iOS/iPadOS terminal/SSH client app designed for interactive mobile use; running it headlessly or in a CI pipeline is a category mismatch as it has no server/daemon mode or CI-oriented interface.

                          ⚑ 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

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

                          weight 3 · not comparable
                          Blink Shelln/a

                          Blink Shell is a terminal/SSH/mosh client for iOS, not an AI agent or MCP-capable platform; MCP server integration is outside its product category.

                            ⚑ flag
                            Working Copynone0/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

                          • ai-native userConnect an agent via an official MCP server

                            weight 3 · not comparable
                            Blink Shelln/a

                            Blink Shell is a terminal/SSH/Mosh client for iOS, not an AI agent or coding assistant; there is no indication it plays the agent role nor offers an MCP server role. Connecting to AI-coding tools like VS Code Server/Codespaces is client-side usage, not an official MCP server axis, so this story is a category error for this product type.

                              ⚑ flag
                              Working Copynone0/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

                            • ai-native userUse an official CLI

                              weight 2 · not comparable
                              Blink Shelln/a

                              Blink Shell is a terminal/SSH client app, not an AI agent or developer platform for which an 'official CLI for AI-native workflows' would be a meaningful axis; it is itself a shell/CLI tool, not something with a separate AI-oriented CLI product to evaluate.

                                ⚑ 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

                              • ai-native userIssue scoped/least-privilege API credentials for an agent

                                weight 2 · not comparable
                                Blink Shelln/a

                                Blink Shell is a terminal/SSH client for iOS, not an agent-management or API-credential-issuing platform; there is no concept of scoped API credentials for agents in its feature set. This axis is a category error for this product type.

                                  ⚑ flag
                                  Working Copynone0/10

                                  No evidence of any API credential/token scoping mechanism for agents; Working Copy uses SSH keys/Identities for git auth and has a Repository Agent AI assistant, but nothing about issuing scoped or least-privilege API credentials for external agents.

                                  • [claimed-docs] “You attach a private key to your Identity which can be imported or generated inside the app.”
                                  • [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 openapi: all candidate paths 404 (https://workingcopyapp.com/openapi.json, https://workingcopyapp.com/swagger.json, https://workingcop…”
                                  proof ↗⚑ flag

                                • ai-native userBuild against official SDKs

                                  weight 2 · not comparable
                                  Blink Shelln/a

                                  Blink Shell is a terminal/SSH/Mosh client app, not a platform or service with an SDK/API surface for developers to build against; the story of building against official SDKs is a category error for this product type.

                                    ⚑ 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

                                    • ai-native userSubscribe to events via webhooks

                                      weight 2 · not comparable
                                      Blink Shelln/a

                                      Blink Shell is a terminal/SSH/Mosh client app, not a service or platform with an event system; webhooks are not a fair capability for this kind of product.

                                        ⚑ 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

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

                                        weight 2 · not comparable
                                        Blink Shelln/a

                                        Blink Shell is a terminal/SSH/Mosh client; AI-generated insights from data is a wrong-axis capability for this product category, not something a terminal emulator would plausibly ship.

                                          ⚑ flag
                                          Working Copypartialclaimed6/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

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

                                          weight 2 · not comparable
                                          Blink Shelln/a

                                          Blink Shell is a mobile SSH/Mosh terminal client, not an automation/agent platform; there's no concept of background autonomous automations in its feature set. This axis is a category error for a terminal client rather than a missing feature.

                                            ⚑ flag
                                            Working Copypartialclaimed4/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

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

                                            weight 3 · not comparable
                                            Blink Shelln/a

                                            Blink Shell is a terminal/SSH/Mosh client for iOS; nothing in the evidence indicates a built-in AI assistant feature. This story is a category error for this product type — a terminal emulator does not deliver AI-agent delegation itself.

                                              ⚑ flag
                                              Working Copyfullclaimed7/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

                                            • ai-native userOperate the product with natural-language commands

                                              weight 2 · not comparable
                                              Blink Shelln/a

                                              Blink Shell is a terminal/SSH client for iOS; the evidence shows only standard shell commands, key management, and terminal UI features, with no natural-language or AI command interface of any kind. This axis (operating via natural-language commands, agenticness) is a category mismatch for a traditional terminal emulator, not a missing feature it could plausibly ship as part of its product identity.

                                                ⚑ flag
                                                Working Copyfullclaimed7/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

                                              • ai-native userExplore an interactive API reference with runnable examples

                                                weight 2 · not comparable
                                                Blink Shelln/a

                                                Blink Shell is a terminal/SSH client app, not an API-driven platform or SDK; an interactive API reference with runnable examples is not a relevant capability for this product category.

                                                  ⚑ flag
                                                  Working Copynone0/10

                                                  Working Copy is a mobile git client with no evidence of any API reference, interactive docs, or runnable examples; probes for llms.txt, markdown docs, and OpenAPI specs all returned 404.

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

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

                                                  weight 1 · not comparable
                                                  Blink Shelln/a

                                                  Blink Shell is a terminal/SSH client for connecting to remote hosts; it has no concept of sandbox environments or production/test data separation - that's an axis for testing/dev platforms, not a terminal emulator app.

                                                    ⚑ 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

                                                    • ai-native userRely on versioned APIs with a documented deprecation policy

                                                      weight 2 · not comparable
                                                      Blink Shelln/a

                                                      Blink Shell is a terminal/SSH client app, not a platform offering a programmatic API for third-party/agent integration; the story of versioned APIs with a deprecation policy is a category error for this product type.

                                                        ⚑ flag
                                                        Working Copynone0/10

                                                        No evidence of any public API, versioning scheme, or deprecation policy; probes for OpenAPI/llms.txt all return 404s, and Working Copy's docs only cover in-app Git features, not an API for programmatic/agentic access.

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

                                                      • ai-native userPerform bulk operations across many items at once

                                                        weight 2 · not comparable
                                                        Blink Shelln/a

                                                        Blink Shell is a terminal/SSH client for iOS; bulk operations across many items is not a fair capability for this kind of product—it's a terminal emulator, not a batch-processing or automation platform.

                                                          ⚑ flag
                                                          Working Copypartialclaimed4/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

                                                        • ai-native userVersion, review, and roll back my automations

                                                          weight 1 · not comparable
                                                          Blink Shelln/a

                                                          Blink Shell is a terminal/SSH client for iOS, not an automation platform with workflows or agent scripts that could be versioned, reviewed, or rolled back; this axis is a category error for this product type.

                                                            ⚑ flag
                                                            Working Copypartialclaimed6/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

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

                                                            weight 2 · not comparable
                                                            Blink Shelln/a

                                                            Blink Shell is a terminal/SSH/Mosh client for iOS, not a git tool; git commit editing is a wrong-axis capability for a terminal emulator itself (any git operations would occur via a remote shell's own git binary, not Blink Shell functionality).

                                                              ⚑ flag
                                                              Working Copyfullclaimed8/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

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

                                                              weight 2 · not comparable
                                                              Blink Shelln/a

                                                              Blink Shell is a terminal/SSH/Mosh client for iOS, not a code search or navigation tool; it provides basic Unix utilities like grep but no fuzzy matching, code-aware filters, or regex-based code navigation features. This axis is a category error for a terminal emulator app.

                                                                ⚑ flag
                                                                Working Copypartialclaimed4/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

                                                              • power-userVisualize the full commit graph across branches

                                                                weight 2 · not comparable
                                                                Blink Shelln/a

                                                                Blink Shell is a terminal/SSH/Mosh client for mobile devices, not a git tool or GUI for visualizing commit history; git graph visualization is outside its product category.

                                                                  ⚑ flag
                                                                  Working Copyfullclaimed8/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

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

                                                                  weight 2 · not comparable
                                                                  Blink Shelln/a

                                                                  Blink Shell is a terminal/SSH/Mosh client for iOS, not a git tool or version control interface; interactive rebase/history rewriting is a git-code capability entirely outside its product category (though a user could run git commands via a remote shell, that's not a feature of Blink itself).

                                                                    ⚑ flag
                                                                    Working Copyfullclaimed8/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

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

                                                                    weight 2 · not comparable
                                                                    Blink Shelln/a

                                                                    Blink Shell is a terminal/SSH/Mosh client for iOS; it provides shell access to remote machines but has no built-in merge-conflict resolution tooling. Resolving merge conflicts is a git-tooling/IDE feature, not something a terminal emulator would plausibly ship, so this axis is a category error for this product.

                                                                      ⚑ flag
                                                                      Working Copyfullclaimed8/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

                                                                    • developerCreate pull requests on hosted Git platforms directly from my device

                                                                      weight 3 · not comparable
                                                                      Blink Shelln/a

                                                                      Blink Shell is a terminal/SSH/mosh client for iOS; it provides shell access and code-editor integrations but has no Git platform integration for creating pull requests. This is a category error—PR creation is a GitHub/GitLab web-workflow feature, not something a terminal emulator app would surface directly (users could only do it via git CLI/gh CLI inside a remote shell, which is the remote host's tooling, not Blink's).

                                                                        ⚑ flag
                                                                        Working Copyfullclaimed8/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

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

                                                                        weight 2 · not comparable
                                                                        Blink Shelln/a

                                                                        Blink Shell is a terminal/SSH/Mosh client for iOS; git stash/unstash is a git version-control operation, not a function of a terminal emulator itself. This is a category error — the axis belongs to a git tool or IDE, not a shell/SSH client.

                                                                          ⚑ flag
                                                                          Working Copyfullclaimed8/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

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

                                                                          weight 1 · not comparable
                                                                          Blink Shelln/a

                                                                          Blink Shell is an SSH/Mosh terminal client; any git operations would rely entirely on the remote host's own git binary, not a Blink-native capability. Git submodule management is not a feature category this type of product ships, so the axis does not apply.

                                                                            ⚑ flag
                                                                            Working Copypartialclaimed5/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

                                                                          • developerPreview Markdown, HTML, and other rendered files with live reload

                                                                            weight 2 · not comparable
                                                                            Blink Shelln/a

                                                                            Blink Shell is a terminal/SSH/Mosh client, not a file preview or rendering tool; live-reload preview of Markdown/HTML is outside its category.

                                                                              ⚑ flag
                                                                              Working Copyfullclaimed8/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

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

                                                                              weight 2 · not comparable
                                                                              Blink Shelln/a

                                                                              Blink Shell is a terminal/SSH/Mosh client for iOS/iPadOS, not a VPN or network-routing tool; 'exit node' traffic routing (e.g., VPN mesh networking) is a completely different product category and wrong axis for this kind of tool.

                                                                                ⚑ 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

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

                                                                                  weight 3 · not comparable
                                                                                  Blink Shellnone0/10

                                                                                  Blink Shell provides SSH/Mosh terminal access to hosts, but there is no evidence of any Kubernetes-specific integration (kubectl exec, kubeconfig management, cluster access) or broader infrastructure-access features beyond generic SSH to named hosts.

                                                                                    ⚑ 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

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

                                                                                      weight 2 · not comparable
                                                                                      Blink Shelln/a

                                                                                      Blink Shell is a terminal/SSH/Mosh client for iOS, not a VPN or network-mesh product; subnet routing to reach devices as if on the local network is a VPN-style capability entirely outside its category (wrong axis).

                                                                                        ⚑ 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

                                                                                        • ai-native userDo everything through the API that I can do in the UI

                                                                                          weight 2 · not comparable
                                                                                          Blink Shelln/a

                                                                                          Blink Shell is a terminal/SSH client app, not a service with a programmatic API surface distinct from its UI; the notion of an API replicating UI functionality is a category mismatch for this product type.

                                                                                            ⚑ flag
                                                                                            Working Copypartialprobed3/10

                                                                                            Working Copy exposes automation via the Shortcuts app and a conversational 'Repository Agent' that can browse, search, read/modify files, commit, pull and push, giving some non-UI access to core git actions, but there is no documented REST/OpenAPI surface (probe shows no openapi.json, llms.txt, or machine-readable docs) proving full UI-parity for an AI-native/API consumer. missing for 10: a formal API/SDK spec covering all UI actions, evidence that Shortcuts actions cover every UI feature (branches, tags, submodules, resolve tool, etc.), and independent confirmation of Repository Agent's coverage.

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

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

                                                                                            weight 3 · not comparable
                                                                                            Blink Shelln/a

                                                                                            Blink Shell is a terminal/SSH client app, not a data-storage or SaaS platform that accumulates user data subject to export; there is no 'user data' corpus (documents, records, etc.) to export in the sense this story implies. Data export/lock-in is a category mismatch for a shell/terminal emulator.

                                                                                              ⚑ flag
                                                                                              Working Copyfullclaimed7/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

                                                                                            • ai-native userSelf-host the core product

                                                                                              weight 3 · not comparable
                                                                                              Blink Shelln/a

                                                                                              Blink Shell is a client-side terminal/SSH app that runs locally on the user's device and connects to servers the user already controls; there is no hosted backend or SaaS component for an 'ai-native' user to self-host. The self-hosting axis applies to server/platform products, not to a local iOS client app, so this is a category mismatch rather than a missing capability.

                                                                                                ⚑ 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

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

                                                                                                  weight 2 · not comparable
                                                                                                  Blink Shelln/a

                                                                                                  Blink Shell is a local terminal/SSH client app, not a data-storage or cloud service; data residency/region selection is not a meaningful axis for this product category.

                                                                                                    ⚑ 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

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

                                                                                                      weight 3 · not comparable
                                                                                                      Blink Shelln/a

                                                                                                      Blink Shell is a terminal/SSH client, not an AI model or AI service that trains on user data; the question of preventing data being used for AI training is a category error for this product type.

                                                                                                        ⚑ flag
                                                                                                        Working Copynone0/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

                                                                                                      • ai-native userControl data retention and deletion

                                                                                                        weight 2 · not comparable
                                                                                                        Blink Shelln/a

                                                                                                        Blink Shell is a terminal/SSH/Mosh client for iOS; it does not process or store user data on behalf of an AI service, so data retention/deletion controls are a category error for this kind of product.

                                                                                                          ⚑ flag
                                                                                                          Working Copynone0/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

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

                                                                                                          weight 3 · not comparable
                                                                                                          Blink Shelln/a

                                                                                                          Blink Shell is a mobile SSH/mosh terminal client; it provides connectivity and file transfer to remote hosts but has no AI agent, PR analysis, or code-review capability of its own. This is a category error for a terminal client, not a missing feature.

                                                                                                            ⚑ flag
                                                                                                            Working Copypartialclaimed4/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

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

                                                                                                            weight 2 · not comparable
                                                                                                            Blink Shelln/a

                                                                                                            Blink Shell is a terminal/SSH client for iOS, not a git or AI tool; there is no evidence of git integration or AI features at all, and generating commit messages is outside its product category (terminal emulator/SSH client).

                                                                                                              ⚑ flag
                                                                                                              Working Copyfullclaimed8/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

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

                                                                                                              weight 3 · not comparable
                                                                                                              Blink Shelln/a

                                                                                                              Blink Shell is a terminal/SSH client for iOS, not an AI agent or agentic coding tool; there is no evidence of any AI agent integration for directing conversational browse/search/edit/commit/pull/push workflows. This story presumes an AI-native agent product, which is the wrong axis for a terminal emulator.

                                                                                                                ⚑ flag
                                                                                                                Working Copyfullclaimed7/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

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

                                                                                                                weight 3 · not comparable
                                                                                                                Blink Shelln/a

                                                                                                                Blink Shell is a terminal/SSH/Mosh client for iOS; it has no agent-assignment or autonomous coding-agent workflow that produces pull requests. This capability is entirely outside its product category (terminal emulator/remote shell), not a failed axis.

                                                                                                                  ⚑ flag
                                                                                                                  Working Copynone0/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

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

                                                                                                                  weight 2 · not comparable
                                                                                                                  Blink Shelln/a

                                                                                                                  Blink Shell is an SSH/Mosh terminal client for iOS; it has no AI agent, chat interface, or repository/PR insight capability. This story concerns AI-native conversational agent features, which is entirely outside Blink Shell's product category as a terminal emulator.

                                                                                                                    ⚑ flag
                                                                                                                    Working Copypartialclaimed6/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

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

                                                                                                                    weight 2 · not comparable
                                                                                                                    Blink Shelln/a

                                                                                                                    Blink Shell is a terminal/SSH/Mosh client for connecting to remote shells; it has no concept of cloud-based coding agent task management or tracking. This story is a category error for a terminal emulator, not a missing feature.

                                                                                                                      ⚑ flag
                                                                                                                      Working Copynone0/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

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

                                                                                                                      weight 2 · not comparable
                                                                                                                      Blink Shelln/a

                                                                                                                      Blink Shell is an SSH/Mosh terminal client for iOS; it has no natural-language-to-shell-command generation feature. This is a wrong axis for a terminal emulator/SSH client—no evidence suggests it offers any AI/NLP command generation capability.

                                                                                                                        ⚑ 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

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

                                                                                                                          weight 2 · not comparable
                                                                                                                          Blink Shellnone0/10

                                                                                                                          Blink Shell's evidence describes it as an SSH/Mosh terminal client with a small set of built-in local commands (cat, grep, wc, ls, etc.) and remote connectivity features; there is no mention of a bundled Python runtime or pip package management on-device. No evidence supports installing pure-Python packages locally.

                                                                                                                          • [claimed-docs] “cat, grep, wc, cd, setenv, ls, touch, cp, rm, ln, mv, mkdir, rmdir, df, du”
                                                                                                                          proof ↗⚑ 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

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

                                                                                                                            weight 2 · not comparable
                                                                                                                            Blink Shellnone0/10

                                                                                                                            Evidence shows Blink supports multiple shells, split view, and switching between sessions, but there is no mention of grouping sessions or broadcasting a single command to multiple sessions simultaneously.

                                                                                                                              ⚑ 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

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

                                                                                                                                weight 2 · not comparable
                                                                                                                                Blink Shellfullclaimed8/10

                                                                                                                                GitHub docs explicitly show scp and sftp usage examples with remote hosts, and Blink supports configured SSH keys (Ed25519, ECDSA, RSA) for authentication per docs, confirming key-based scp/sftp transfers work. Missing for 10: independent hands-on verification of scp/sftp specifically (community discussion focuses mostly on ssh/mosh) and no detail on edge cases like large file transfer performance.

                                                                                                                                • [github] “scp user@host.name.edu:filename . sftp localFilename user@host.name.edu:~/”
                                                                                                                                • [claimed-docs] “Supports Ed25519, ECDSA and RSA keys. It is built on top of libssh and libssh2.”
                                                                                                                                • [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
                                                                                                                                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

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

                                                                                                                                  weight 3 · not comparable
                                                                                                                                  Blink Shellpartialclaimed6/10

                                                                                                                                  Docs confirm multiple shells can be opened (two-finger tap to create, swipe to switch) and each session can persist via Mosh even after sleep, plus per-shell customization via themes/fonts and hosts. However, there's no explicit evidence that each session maintains fully independent appearance/history configuration simultaneously (e.g., per-tab theme or scrollback isolation) beyond global settings. Missing for 10: documented per-session independent history/appearance settings, and independent corroboration of multi-session workflows beyond basic split-view/switching.

                                                                                                                                  • [claimed-docs] “To create a new shell, tap the screen with two fingers. To switch between active shells, swipe side to side.”
                                                                                                                                  • [claimed-docs] “don't be afraid to put your device to sleep, when you wake it up later, your connections will be intact.”
                                                                                                                                  • [claimed-docs] “You can flawlessly jump from home, to the train, and then to the office thanks to Mosh. Blink is rock-solid connected all the way.”
                                                                                                                                  • [claimed-docs] “You can rock your terminal and roll your own themes and fonts beyond our included ones. And yes, we include Pragmata Pro by default!”
                                                                                                                                  • [github] “We've incorporated SplitView, for those necessary Google searches and chats with coworkers.”
                                                                                                                                  • [claimed-docs] “Hosts: create hosts that can be accessed with only the hostname.”
                                                                                                                                  proof ↗⚑ 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

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

                                                                                                                                    weight 3 · not comparable
                                                                                                                                    Blink Shellfullcommunity9/10

                                                                                                                                    Blink Shell is built around Mosh, explicitly marketed for surviving network changes (train, home, office) and device sleep with connections remaining intact, backed by docs and community praise of solid connectivity. Missing for 10: independent hands-on verification specifically testing sleep/network-switch persistence rather than general connectivity praise.

                                                                                                                                    • [claimed-docs] “You can flawlessly jump from home, to the train, and then to the office thanks to Mosh. Blink is rock-solid connected all the way.”
                                                                                                                                    • [claimed-docs] “don't be afraid to put your device to sleep, when you wake it up later, your connections will be intact.”
                                                                                                                                    • [claimed-docs] “In Blink type mosh [user@]hostname. For example : mosh irwin@irwinvb.”
                                                                                                                                    • [community] “Been using it (beta testing on iPhone and paid version on iPad so I can compare) for a while. Improving steadily, solid connectivity. So far…”
                                                                                                                                    • [community] “Bought it even though it apparently has no agent forwarding... Pretty good, refresh seems faster than Prompt, especially when using htop and…”
                                                                                                                                    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

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

                                                                                                                                      weight 2 · not comparable
                                                                                                                                      Blink Shellpartialclaimed6/10

                                                                                                                                      Docs confirm custom fonts/themes support with Pragmata Pro included by default and that users can 'roll your own' fonts/themes, but there's no explicit mention of persisted settings, cursor appearance customization, or color-scheme granularity beyond fonts/themes. missing for 10: dedicated docs on color scheme/cursor customization, explicit confirmation settings persist across sessions/devices, independent hands-on corroboration of theming.

                                                                                                                                      • [claimed-docs] “You can rock your terminal and roll your own themes and fonts beyond our included ones. And yes, we include Pragmata Pro by default!”
                                                                                                                                      proof ↗⚑ 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