Termius vs Working Copy
free-tier · subscription-per-seat · enterprise-custom
·freemium · one-time-license
Working Copy wins · 8–10 (10 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to TermiusA probe confirms docs.termius.com/llms.txt returns HTTP 200 with structured documentation links, meaning an agent can be pointed directly at an llms.txt file. Missing for 10: no first-party announcement or documentation explicitly describing/promoting the llms.txt file as an agent-facing feature, and no independent corroboration of its completeness or maintenance.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.termius.com/llms.txt # termius.docs ## Documentation - [What is Termius](https://docs.termius.com…”
Working Copynone0/10Probes 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.
ai-native userDrive the product through a documented public API
weight 3 · round to Working CopyTermiusnone0/10No evidence of a documented public API for driving Termius programmatically; OpenAPI probes all returned 404, and docs focus on UI/CLI features like snippets, AI command generation, and sync rather than an API for external agent control.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.termius.com/openapi.json, https://docs.termius.com/swagger.json, https://docs.termius.c…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.termius.com/llms.txt # termius.docs ## Documentation - [What is Termius](https://docs.termius.com…”
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…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to Working CopyTermius docs mention AI-generated shell commands from plain-language descriptions (docs-6), which is a form of AI suggestion, but there's no evidence of AI-generated insights derived from the user's own data (e.g., analyzing session logs, host activity, or infrastructure patterns) — autocomplete (docs-11, docs-24) is rule/history-based, not AI-driven. missing for 10: AI analysis/insights over session logs or infrastructure data, dashboards or summaries generated from user data, independent/hands-on corroboration of the AI command feature.
- [claimed-docs] “Termius can convert a plain-language description into a shell command... Termius generates the command using AI.”
- [claimed-docs] “Autocomplete in Termius uses data from many sources to suggest snippets, shell history commands, paths, and built-in commands with arguments…”
- [claimed-docs] “Session logs are a record of your terminal activity. They help you review past work, troubleshoot issues, and collaborate with teammates.”
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…”
ai-native userSet up automations that run autonomously in the background
weight 2 · round to Working CopyTermiusnone0/10Termius offers snippets, broadcast commands, and workspace templates that are user-triggered, but there is no evidence of scheduling, triggers, or autonomous background execution without a user actively running them.
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…”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round to Working CopyTermius docs mention AI-assisted command generation from natural language (termius-docs-6), which is a narrow AI helper feature rather than a full agentic assistant capable of being delegated multi-step tasks. Missing for 10: evidence of autonomous task execution, multi-step delegation, or a persistent AI assistant beyond single-command translation, and no independent/hands-on corroboration of this AI feature's real-world use.
- [claimed-docs] “Termius can convert a plain-language description into a shell command... Termius generates the command using AI.”
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”
ai-native userOperate the product with natural-language commands
weight 2 · round to Working CopyTermius docs explicitly describe an AI feature that converts plain-language descriptions into shell commands (termius-docs-6), directly supporting natural-language command operation. However, this appears limited to command generation within the terminal rather than broader natural-language control of the app (e.g., navigating hosts, managing vaults, or automating workflows via NL), and there's no independent/community corroboration of this AI feature's real-world reliability. Missing for 10: broader NL control beyond command generation, hands-on/community validation of the AI feature, and details on accuracy/limitations.
- [claimed-docs] “Termius can convert a plain-language description into a shell command... Termius generates the command using AI.”
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…”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnTermiusnone0/10Termius is an SSH client, not an API product; no evidence of an interactive API reference or runnable examples exists, and the OpenAPI probe explicitly returned 404s at all candidate paths. There is no documented API playground or reference in the evidence pack.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.termius.com/openapi.json, https://docs.termius.com/swagger.json, https://docs.termius.c…”
Working Copynone0/10Working 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.
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnTermiusnone0/10A probe explicitly checked for OpenAPI/Swagger spec files at common paths and all returned 404, and no other evidence mentions a machine-readable API spec being available for download.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.termius.com/openapi.json, https://docs.termius.com/swagger.json, https://docs.termius.c…”
Working Copynone0/10Probes 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.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnTermiusnone0/10Termius is an SSH client focused on terminal/session management; there is no evidence of a public versioned API or documented deprecation policy. The openapi probe returned 404 for all candidate paths, confirming absence of API documentation.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.termius.com/openapi.json, https://docs.termius.com/swagger.json, https://docs.termius.c…”
Working Copynone0/10No 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.
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to TermiusTermius provides multiple documented bulk-operation mechanisms: broadcasting commands to all sessions simultaneously and saving as reusable workspace templates, executing snippets on multiple hosts at once, and CSV bulk-import of hosts/groups/credentials. These directly satisfy 'bulk operations across many items.' Missing for 10: independent/hands-on corroboration specifically validating broadcast-to-many-hosts at scale (community evidence only touches snippet scripting, not the broadcast/bulk-import features) and evidence of bulk operations on other item types like credentials or vault entries.
- [claimed-docs] “You can broadcast a command to all sessions simultaneously and save the entire setup as a reusable template.”
- [claimed-docs] “execute them on multiple hosts at once from the Snippets screen”
- [claimed-docs] “Termius can import hosts from a CSV file, including labels, IP addresses, protocols, ports, groups, subgroups, tags, and credentials.”
- [claimed-docs] “Workspaces group multiple terminal sessions into one focused environment... Broadcast the same input to multiple sessions”
- [claimed-docs] “Workspace templates capture: Included connections, Tab names, Layout configuration, Working directories, Running commands at the time of sav…”
- [community] “Combination of Termius's saved snippets and short shell scripts let me do monitoring without running a separate web-server behind auth. Easi…”
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…”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round to Working CopyTermiusnone0/10Termius evidence covers saved connections, jump-host auto-routing, snippets/broadcast commands, and AI command generation, but none of this describes user-defined rules that trigger actions automatically on events (e.g., on-connect/on-disconnect triggers, webhooks, conditional automations). Jump-host auto-connect is a static config, not an event-rule engine, and no evidence pack item describes any such automation system.
- [claimed-docs] “if you configure a jump host for a Group, every Host within it will automatically connect through that jump host”
- [claimed-docs] “You can broadcast a command to all sessions simultaneously and save the entire setup as a reusable template.”
- [claimed-docs] “execute them on multiple hosts at once from the Snippets screen”
- [claimed-docs] “Termius can convert a plain-language description into a shell command... Termius generates the command using AI.”
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.”
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnTermiusnone0/10Termius offers snippets, broadcast commands, and templates, but no evidence of scheduling recurring jobs or workflows (e.g., cron-like triggers or timed automation) exists in the pack.
ai-native userVersion, review, and roll back my automations
weight 1 · round to Working CopyTermiusnone0/10Termius offers snippets, templates, and logs, but there is no evidence of version control, review workflows, or rollback capability for automations/snippets—no changelog, history, or revert feature is documented.
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…”
Networking access — stories about networking access in this arenaNetworking access
Stories about networking access in this arena
Mesh network
power-userConnect directly to my servers without relying on a cloud relay, proxy, or VPN
weight 2 · round drawnTermius explicitly documents local-first, direct SSH connections without cloud dependency: "Termius doesn't depend on the cloud to manage your access... Connect directly to your servers without the internet, a proxy, or VPN," backed by locally encrypted infrastructure storage. Community evidence corroborates real direct SSH usage in the field (debugging via SSH from mobile), though no independent technical audit verifies the no-relay claim. Missing for 10: independent/hands-on verification of the no-relay architecture claim, and details on how sync (which does use Termius cloud) is kept separate from the direct connection path.
- [claimed-docs] “Termius doesn't depend on the cloud to manage your access. Your infrastructure is stored and encrypted locally. Connect directly to your ser…”
- [claimed-docs] “Every account includes a Personal vault, accessible only to you and synced across all your devices.”
- [community] “Saved my butt once when my docker containers were bouncing while on vacation—debugged and deployed a fix from my iPhone while my wife drove.…”
- [community] “Wow, this app saved my butt over a year ago when I ran out of laptop battery in the field.”
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…”
Offline sync — stories about offline sync in this arenaOffline sync
Stories about offline sync in this arena
Cross device sync
power-userSync my saved hosts and connection settings across all my devices
weight 2 · round to TermiusTermius documents a Personal vault synced across all devices, automatic sync of vaults/hosts/configurations on login, and cross-device access to hosts, keys, groups, snippets, and port-forwarding rules; community evidence corroborates cross-device usage (e.g., debugging from iPhone). Missing for 10: independent verification of sync reliability/conflict handling and no detailed technical explanation of sync mechanism/security internals.
- [claimed-docs] “Every account includes a Personal vault, accessible only to you and synced across all your devices.”
- [claimed-docs] “Log in to your account — your Vaults, hosts, and configurations will be synced automatically.”
- [claimed-docs] “Termius transforms this process with team vaults. Vaults serve as a single source of truth for Hosts, Groups, Snippets, Port Forwarding rule…”
- [claimed-docs] “Items in the Keychain can be referenced by multiple Hosts and Groups without duplicating them.”
- [community] “Saved my butt once when my docker containers were bouncing while on vacation—debugged and deployed a fix from my iPhone while my wife drove.…”
- [community] “I love using Termius on my 12.9” iPad Pro with keyboard—full screen terminal with extra features that pop up right when needed.”
Working Copynone0/10Working 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.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to Working CopyTermiusnone0/10No evidence of a public API exposing Termius's core UI capabilities (hosts, snippets, vaults, workspaces) programmatically; probes for an OpenAPI spec all returned 404, and no documentation describes an API at all.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.termius.com/openapi.json, https://docs.termius.com/swagger.json, https://docs.termius.c…”
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…”
ai-native userExport all of my data in open formats and leave
weight 3 · round to Working CopyTermiusnone0/10Evidence shows Termius supports importing hosts/keys from SSH config and CSV files, but nowhere does the pack mention any export function for hosts, keychains, snippets, or vaults in open formats, and community comments raise concern about SSH keys being stored on Termius' servers with no mention of an exit path.
- [claimed-docs] “Termius supports importing the contents of the `~/.ssh` folder, including `ssh_config`, `known_hosts`, and key files”
- [claimed-docs] “Termius can import hosts from a CSV file, including labels, IP addresses, protocols, ports, groups, subgroups, tags, and credentials.”
- [community] “The only benefit of Termius seems to be a few nice colours, with the downside of being able to store your SSH keys on Termius' servers.”
- [community] “I'm usually wary of using closed-source programs for sensitive tasks like SSH. I haven't found details on the crypto libraries used or secur…”
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.”
ai-native userRead the product's source under an open license
weight 2 · round drawnTermiusnone0/10Termius is closed-source; there's no evidence of an open license or public source repository, and community feedback (termius-comm-4) explicitly notes concerns about it being closed-source with no visibility into crypto implementation.
- [community] “I'm usually wary of using closed-source programs for sensitive tasks like SSH. I haven't found details on the crypto libraries used or secur…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnTermiusnone0/10No evidence pack item mentions AI training data opt-out, data usage policy for model training, or any privacy control specific to AI training; only unrelated AI-command-generation feature (termius-docs-6) is mentioned, which does not address data usage/training consent.
Working Copynone0/10Working 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…”
ai-native userControl data retention and deletion
weight 2 · round drawnTermiusnone0/10Termius documents where data lives (Personal/Team vaults, local encrypted storage, synced session logs) but provides no evidence of user-facing controls for setting retention periods, purging logs, or deleting synced/vault data on demand.
- [claimed-docs] “Termius automatically collects terminal session logs for every host. Logs are synced across devices and shared with your team. You can searc…”
- [claimed-docs] “Every account includes a Personal vault, accessible only to you and synced across all your devices.”
- [claimed-docs] “When you add team members, a Team vault is created automatically. This vault is shared with all team members, allowing your team to manage i…”
- [claimed-docs] “Termius doesn't depend on the cloud to manage your access. Your infrastructure is stored and encrypted locally. Connect directly to your ser…”
- [claimed-docs] “Session logs are a record of your terminal activity. They help you review past work, troubleshoot issues, and collaborate with teammates.”
Working Copynone0/10Working 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…”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round drawnTermiusnone0/10No evidence pack item mentions telemetry, usage tracking, analytics opt-out, or any privacy/data-collection settings controllable by the user; documentation focuses on features (sync, keychain, SSH keys) not telemetry controls.
Working Copynone0/10No 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.
Security — security posture and hardening storiesSecurity
Security posture and hardening stories
Credential protection
developerProtect my remote connections with biometric authentication like Face ID or fingerprint
weight 2 · round to TermiusTermius docs explicitly claim biometric protection via Windows Hello, Touch ID/Face ID, and Android biometrics tied to device-bound keys, directly matching the story. Missing for 10: independent/hands-on corroboration of biometric unlock in practice and details on implementation robustness across platforms.
- [claimed-docs] “Secure connections with device-bound keys and biometric protection with Windows Hello, Touch ID/Face ID, or Android biometrics.”
- [claimed-docs] “Secure SSH authentication with FIDO2 security keys and MFA.”
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.”
developerStore credentials once in a secure vault and reference them from multiple hosts
weight 2 · round to TermiusTermius provides a Keychain vault where credentials (SSH keys, passwords) are stored once and referenced by multiple Hosts and Groups without duplication, backed by Personal and Team vaults synced across devices with encryption. This directly matches the story's core need of centralized credential storage referenced across hosts. Missing for 10: independent/hands-on verification of the vault-reference mechanism specifically (community evidence covers general SSH client experience but not this exact vault-reuse workflow), and no detail on encryption specifics beyond marketing claims.
- [claimed-docs] “Items in the Keychain can be referenced by multiple Hosts and Groups without duplicating them.”
- [claimed-docs] “Every account includes a Personal vault, accessible only to you and synced across all your devices.”
- [claimed-docs] “When you add team members, a Team vault is created automatically. This vault is shared with all team members, allowing your team to manage i…”
- [claimed-docs] “Termius transforms this process with team vaults. Vaults serve as a single source of truth for Hosts, Groups, Snippets, Port Forwarding rule…”
- [claimed-docs] “Create and manage your SSH keys with passphrase protection. Everything is encrypted and easily accessible from any device.”
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.”
power-userStore my SSH keys in a hardware-backed secure enclave protected by biometrics
weight 2 · round to Working CopyTermius docs explicitly claim 'device-bound keys and biometric protection with Windows Hello, Touch ID/Face ID, or Android biometrics' plus FIDO2 security key support, matching the hardware-backed/biometric claim reasonably well. However, there's no explicit mention of a 'secure enclave' term or independent verification of how keys are hardware-isolated, and community comments express skepticism about SSH keys being stored on Termius' servers and about closed-source crypto practices, which tempers confidence without concretely disproving the biometric/device-bound claim. Missing for 10: independent/hands-on verification of the secure-enclave implementation, explicit documentation of enclave/TPM/Keystore usage, and resolution of community concerns about key storage location.
- [claimed-docs] “Secure connections with device-bound keys and biometric protection with Windows Hello, Touch ID/Face ID, or Android biometrics.”
- [claimed-docs] “Secure SSH authentication with FIDO2 security keys and MFA.”
- [claimed-docs] “Create and manage your SSH keys with passphrase protection. Everything is encrypted and easily accessible from any device.”
- [community] “The only benefit of Termius seems to be a few nice colours, with the downside of being able to store your SSH keys on Termius' servers.”
- [community] “I'm usually wary of using closed-source programs for sensitive tasks like SSH. I haven't found details on the crypto libraries used or secur…”
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.”
Terminal ssh — terminal and SSH workflows — shells, sessions, remote accessTerminal ssh
Terminal and SSH workflows — shells, sessions, remote access
Ssh connections
developerRun local UNIX commands like ls, grep, cat, tar, and curl directly in the app
weight 3 · round drawnTermiusnone0/10All evidence describes Termius as an SSH/SFTP client for connecting to and managing remote hosts (snippets run on hosts, port forwarding, session logs, SFTP), with no mention of a local shell/terminal mode for running commands like ls, grep, cat, tar, curl directly against the local machine. Missing for 10: any documentation or community confirmation of a local terminal tab/local command execution feature.
- [claimed-docs] “execute them on multiple hosts at once from the Snippets screen”
- [claimed-docs] “In Termius, a snippet is a labeled shell script that you can save and run on different hosts without retyping it.”
- [claimed-docs] “Dual-pane interface on the desktop: manage local or remote files side-by-side”
- [claimed-docs] “Integrated workflow: switch between a terminal session and an SFTP session for the same host with a single click”
developerConnect to remote servers using SSH with Ed25519, ECDSA, or RSA keys
weight 3 · round to TermiusTermius docs explicitly confirm it can generate Ed25519, ECDSA, RSA (and ML-DSA) keys with passphrase protection, and supports importing existing ~/.ssh keys and configs for connecting to remote servers via SSH. Community evidence corroborates real-world SSH usage as a core client function. Missing for 10: independent hands-on verification specifically testing each key type's SSH connection success.
- [claimed-docs] “Termius can generate Ed25519, ECDSA, RSA, and ML-DSA keys.”
- [claimed-docs] “Create and manage your SSH keys with passphrase protection. Everything is encrypted and easily accessible from any device.”
- [claimed-docs] “Termius supports importing the contents of the `~/.ssh` folder, including `ssh_config`, `known_hosts`, and key files”
- [community] “Combination of Termius's saved snippets and short shell scripts let me do monitoring without running a separate web-server behind auth. Easi…”
- [community] “Saved my butt once when my docker containers were bouncing while on vacation—debugged and deployed a fix from my iPhone while my wife drove.…”
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.”
power-userGenerate SSH key pairs for password-less access to my servers
weight 2 · round to TermiusTermius docs explicitly confirm SSH key pair generation (Ed25519, ECDSA, RSA, ML-DSA) with passphrase protection, encrypted storage, and cross-device sync/keychain reuse across hosts for password-less auth. Missing for 10: independent hands-on verification of the key-generation workflow itself (community evidence covers other features but not this specific one).
- [claimed-docs] “Create and manage your SSH keys with passphrase protection. Everything is encrypted and easily accessible from any device.”
- [claimed-docs] “Termius can generate Ed25519, ECDSA, RSA, and ML-DSA keys.”
- [claimed-docs] “Items in the Keychain can be referenced by multiple Hosts and Groups without duplicating them.”
- [claimed-docs] “Every account includes a Personal vault, accessible only to you and synced across all your devices.”
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”
power-userConnect to a saved host with one tap without re-entering credentials
weight 2 · round to TermiusDocs confirm saved hosts with credentials stored in Keychain/vault so users connect instantly without re-entering IPs/ports/passwords, with sync across devices enabling one-tap access from any client. Community evidence corroborates real-world quick reconnection (e.g., fixing servers from a phone). Missing for 10: independent hands-on verification specifically of the one-tap flow (vs. broader feature set) and no mention of biometric/one-tap unlock friction trade-offs.
- [claimed-docs] “No more re-entering IPs, ports, or password. Everything is saved, so you connect instantly.”
- [claimed-docs] “Items in the Keychain can be referenced by multiple Hosts and Groups without duplicating them.”
- [claimed-docs] “Every account includes a Personal vault, accessible only to you and synced across all your devices.”
- [claimed-docs] “Log in to your account — your Vaults, hosts, and configurations will be synced automatically.”
- [community] “Saved my butt once when my docker containers were bouncing while on vacation—debugged and deployed a fix from my iPhone while my wife drove.…”
- [community] “Wow, this app saved my butt over a year ago when I ran out of laptop battery in the field.”
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”
Not comparable on these axes
ai-native userRun the product headlessly / in CI for automation
weight 2 · not comparableTermiusn/aTermius is a GUI-based SSH/terminal client designed for interactive, human-driven sessions across desktop and mobile; running headlessly or in CI automation pipelines is outside its product category (no CLI, headless mode, or automation API is evidenced or implied by its design).
Working Copyn/aWorking 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.”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableTermiusn/aTermius is an SSH/terminal client focused on connectivity, key management, and collaboration; there is no evidence of any MCP server integration or plugin mechanism for AI tools, and this axis is not a natural fit for a terminal/SSH client product category.
Working Copynone0/10Working 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.”
ai-native userConnect an agent via an official MCP server
weight 3 · not comparableTermiusn/aTermius is an SSH/terminal client (an agent-adjacent tool for humans), not an ecosystem/platform expected to expose an official MCP server for other AI agents to connect to; no evidence suggests it plays that server role. This is a category mismatch rather than a missing feature.
Working Copynone0/10Working 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…”
ai-native userUse an official CLI
weight 2 · not comparableTermiusnone0/10The evidence pack covers Termius's GUI features (snippets, workspaces, port forwarding, AI command generation) but contains no mention of an official standalone CLI tool for scripting/automation outside the app; the probe for OpenAPI/API surface also returned 404s, suggesting no documented CLI/API surface.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.termius.com/openapi.json, https://docs.termius.com/swagger.json, https://docs.termius.c…”
Working Copyn/aWorking 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…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client for human users, not an agent platform or identity provider; issuing scoped API credentials for an AI agent is outside its product category and not something a buyer comparing terminal clients would expect.
Working Copynone0/10No 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…”
ai-native userBuild against official SDKs
weight 2 · not comparableTermiusnone0/10No evidence of any official SDK for developers to build against; Termius is an SSH client with AI-generated command features, not a platform offering SDKs, and the openapi probe returned 404s with no SDK docs found.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.termius.com/openapi.json, https://docs.termius.com/swagger.json, https://docs.termius.c…”
- [claimed-docs] “Termius can convert a plain-language description into a shell command... Termius generates the command using AI.”
ai-native userSubscribe to events via webhooks
weight 2 · not comparableTermiusn/aTermius is an SSH client/terminal app, not an event-driven platform; webhook subscriptions are outside its product category (wrong axis) rather than a missing feature.
Working Copyn/aWorking 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.”
ai-native userTest against a sandbox environment without touching production data
weight 1 · not comparableTermiusn/aTermius is an SSH/terminal client for connecting to and managing real servers, not a testing or sandboxing tool; there is no concept of a 'sandbox vs production' testing environment in its feature set. This axis is a category error for a terminal/SSH client.
power-userAmend the latest commit or undo unpushed commits to fix or split them
weight 2 · not comparableTermiusn/aTermius is an SSH client/terminal tool, not a git client or version control tool; amending or undoing commits is entirely outside its product category (wrong axis).
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 …”
developerSearch and navigate code content using fuzzy matching, filters, and regular expressions
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client, not a code editor or repository tool; searching/navigating code content with fuzzy matching, filters, and regex is a wrong-axis capability for this product category. It only offers log searching, not code content search/navigation.
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.”
developerClone Git repositories over HTTPS, SSH, or the Git protocol
weight 3 · not comparableTermiusn/aTermius is an SSH/terminal client focused on server connections, file transfer, and session management, not a Git client or version control tool; cloning Git repositories over HTTPS/SSH/Git protocol is outside its product category.
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.”
power-userVisualize the full commit graph across branches
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client, not a source-control or git tool; visualizing a commit graph across branches is entirely outside its product category.
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.”
developerCommit and push changes directly from my device
weight 3 · not comparableTermiusn/aTermius is an SSH/terminal client for connecting to remote hosts, snippets, and file transfer—it has no git integration or version control features for committing/pushing code. This story is a category error for this product type.
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.”
power-userSign my commits with a GPG or SSH key for verification
weight 1 · not comparableTermiusn/aTermius is an SSH/terminal client focused on connection management, not a git/version-control tool; commit signing with GPG/SSH keys is a git workflow feature outside its product category. Evidence covers SSH key generation/management for authentication, not git commit signing.
Working Copynone0/10Evidence 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.”
power-userInteractively rewrite history by deleting, editing, squashing, or reordering commits
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client, not a git tool; interactive rebase/history rewriting is entirely outside its product category.
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.”
developerResolve merge conflicts across many files at once with a dedicated tool
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client, not a source-control or code-diff tool; merge conflict resolution is entirely outside its product category.
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.”
developerCreate pull requests on hosted Git platforms directly from my device
weight 3 · not comparableTermiusn/aTermius is an SSH/terminal client focused on connecting to hosts, managing keys, and terminal collaboration; it is not a Git hosting or Git workflow tool and has no evidence of Git/PR integration, so creating pull requests is outside its product category.
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.”
developerReview pull requests from my phone while on the go
weight 3 · not comparableTermiusn/aTermius is an SSH/terminal client, not a git/code review tool; it has no mention of pull requests, git hosting integration, or code review workflows. Reviewing PRs is outside its product category (wrong axis), even though it supports mobile terminal SSH sessions.
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.”
power-userStash and unstash changes to temporarily clear my working directory
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client, not a version control tool; git stash/unstash is a wrong axis for this product category.
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.”
power-userClone, update, and manage Git submodules within a repository
weight 1 · not comparableTermiusn/aTermius is an SSH/terminal client focused on host management, file transfer, and session tools; Git submodule management is a source-control operation entirely outside its product category, not something a terminal client would ship as a feature.
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.”
developerPreview Markdown, HTML, and other rendered files with live reload
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client focused on remote connections, file transfer, and terminal collaboration; it has no evidence of rendering Markdown/HTML preview with live reload, which is a file/document-editing feature outside its category as a terminal tool.
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”
power-userRoute all my internet traffic through a specific device on my network using an exit node
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client with port forwarding and tunneling (local/remote/dynamic), not a VPN or mesh-networking tool that can route all device traffic through an exit node. This capability is outside the product's category (SSH/SFTP session management), so the axis does not apply.
- [claimed-docs] “Termius supports all three main types of port forwarding (local, remote, and dynamic) and lets users manage their port-forwarding rules thro…”
- [claimed-docs] “Termius doesn't depend on the cloud to manage your access. Your infrastructure is stored and encrypted locally. Connect directly to your ser…”
developerGet secure infrastructure access to resources wherever they live, including Kubernetes clusters
weight 3 · not comparableTermiusnone0/10Termius's evidence pack covers SSH/host management, port forwarding, vaults, snippets, and file transfer, but there is no mention anywhere of Kubernetes clusters, kubectl integration, or container-orchestration access—this is a specific capability that is entirely unevidenced.
developerUse subnet routers to reach devices outside my local network as if I were on it
weight 2 · not comparableTermiusn/aSubnet routing (reaching an entire remote subnet via a single gateway node, à la Tailscale subnet routers) is a mesh-VPN networking feature, not something an SSH/terminal client like Termius provides. Termius offers per-host jump hosts, port forwarding, and tunneling, but these require configuring access per host/service, not exposing a whole subnet transparently — this capability class is outside Termius's product category.
developerAccess and work with files and repositories from other apps' sandboxes on my device
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client focused on remote server management, not a file-system/document interop tool with iOS/Android app-sandbox file access (like Files app document providers). Accessing other apps' sandboxed files/repos is outside its product category.
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.”
ai-native userSelf-host the core product
weight 3 · not comparableTermiusnone0/10Termius is presented as a cloud-synced SSH client with Personal/Team vaults and sync services (termius-docs-8, termius-docs-9, termius-docs-29); there is no mention of any self-hosted server/backend option or on-prem deployment for the core product. termius-docs-15 only notes local caching of credentials for offline connect, not a self-hosted core service. Missing for 10: any documented self-hosted/on-prem deployment option, self-hosting instructions, or enterprise self-managed sync server.
- [claimed-docs] “Every account includes a Personal vault, accessible only to you and synced across all your devices.”
- [claimed-docs] “When you add team members, a Team vault is created automatically. This vault is shared with all team members, allowing your team to manage i…”
- [claimed-docs] “Termius doesn't depend on the cloud to manage your access. Your infrastructure is stored and encrypted locally. Connect directly to your ser…”
- [claimed-docs] “Log in to your account — your Vaults, hosts, and configurations will be synced automatically.”
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableTermiusnone0/10No evidence Termius offers any data residency or region-selection controls for where vault/host data is stored; docs only describe local encryption and sync to Termius' cloud without regional choice options.
ai-native userHave an AI agent analyze my pull requests and suggest code improvements from my phone
weight 3 · not comparableTermiusn/aTermius is a mobile-capable SSH/terminal client; PR analysis and code-suggestion agents are a code-review/CI-integration capability outside its category, which focuses on terminal sessions, host management, and shell command AI assistance. Nothing in the evidence shows PR/code review integration, so this is a wrong-axis question rather than a missing feature.
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”
ai-native userGet AI-generated commit message suggestions based on my staged changes
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client, not a version control or git tool; commit message generation is unrelated to its product category (its AI feature is for generating shell commands, not git commits).
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”
ai-native userDirect an AI agent to browse, search, edit, commit, pull, and push in a repository via conversation
weight 3 · not comparableTermiusn/aTermius is an SSH/terminal client, not an AI coding agent or repo-management tool; the story asks for an AI agent to browse/search/edit/commit/pull/push in a repository via conversation, which is a category error for this product type. Its AI feature is limited to generating shell commands from plain language, not agentic repo operations.
- [claimed-docs] “Termius can convert a plain-language description into a shell command... Termius generates the command using AI.”
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”
ai-native userAssign an issue to an AI coding agent and receive a ready-to-review pull request
weight 3 · not comparableTermiusn/aTermius is an SSH/terminal client for managing server connections, not an AI coding agent or issue-tracking/PR workflow tool; assigning issues to agents and receiving PRs is outside its product category.
Working Copynone0/10Working 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…”
ai-native userConverse with an AI agent in natural language to get insights into repositories and open pull requests
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client for managing servers; it has no repository or pull-request awareness, and this story's subject (AI conversational insight into repos/PRs) is a wrong-axis category error for this product type. Its only AI feature is natural-language-to-shell-command generation, unrelated to repos/PRs.
- [claimed-docs] “Termius can convert a plain-language description into a shell command... Termius generates the command using AI.”
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…”
developerManage and track cloud-based coding agent tasks from my phone
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client for managing servers, not a platform for orchestrating or tracking cloud-based AI coding agent tasks; nothing in the evidence relates to coding agent task management.
Working Copynone0/10Working 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…”
ai-native userDescribe what I want in plain language and have the tool generate the corresponding shell command
weight 2 · not comparableTermius docs explicitly state it can convert a plain-language description into a shell command via AI generation, directly matching the story. However, this is a single first-party doc claim with no independent/hands-on corroboration, no detail on scope/accuracy, and no community evidence discussing this AI feature. missing for 10: independent or hands-on verification of the AI command-generation feature, detail on its reliability/limitations, and broader documentation beyond one line.
- [claimed-docs] “Termius can convert a plain-language description into a shell command... Termius generates the command using AI.”
developerEdit files with a terminal-based editor and run syntax/lint checkers inside the app
weight 2 · not comparableTermiusn/aTermius is an SSH client/terminal app for connecting to remote hosts, not a text editor or IDE with built-in linting/syntax-checking capability; editing and running lint checkers is outside its product category (users would rely on remote shell tools like vim/nano and remote linters via SSH, not a Termius-native feature).
Working Copynone0/10Working 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.
developerInstall additional pure-Python packages using pip directly on my device
weight 2 · not comparableTermiusn/aTermius is an SSH/terminal client, not a Python runtime or package manager; installing pip packages would occur on the remote host's OS itself, not as a Termius feature. This axis is a category error for this product type.
power-userGroup multiple terminal sessions together and broadcast the same command to all of them
weight 2 · not comparableTermius Workspaces feature explicitly groups multiple terminal sessions and broadcasts the same input to all of them, with templates capturing layout, tabs, and running commands (termius-docs-18, termius-docs-19, termius-docs-4). Missing for 10: independent hands-on corroboration of broadcast reliability across many hosts and any documented limits/edge cases from community sources.
- [claimed-docs] “Workspaces group multiple terminal sessions into one focused environment... Broadcast the same input to multiple sessions”
- [claimed-docs] “Workspace templates capture: Included connections, Tab names, Layout configuration, Working directories, Running commands at the time of sav…”
- [claimed-docs] “You can broadcast a command to all sessions simultaneously and save the entire setup as a reusable template.”
developerTransfer files to and from remote hosts via scp and sftp using my configured keys
weight 2 · not comparableTermius documents SFTP file transfer with a dual-pane interface and one-click switching between terminal and SFTP sessions on the same host, using the same configured Hosts/Keychain credentials, plus a keychain for SSH key management with passphrase protection referenced across connections. This directly covers scp/sftp-style file transfer using configured keys. Missing for 10: explicit mention of the `scp` command/protocol specifically (only SFTP is named) and independent hands-on corroboration of file-transfer reliability.
- [claimed-docs] “Dual-pane interface on the desktop: manage local or remote files side-by-side”
- [claimed-docs] “Integrated workflow: switch between a terminal session and an SFTP session for the same host with a single click”
- [claimed-docs] “Create and manage your SSH keys with passphrase protection. Everything is encrypted and easily accessible from any device.”
- [claimed-docs] “Items in the Keychain can be referenced by multiple Hosts and Groups without duplicating them.”
Working Copyn/aWorking 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.
power-userOpen multiple terminal sessions, each with its own context, appearance, and history
weight 3 · not comparableTermius Workspaces explicitly group multiple terminal sessions with per-session tab names, layout, working directories, and saved templates, while each Host retains its own connection context, keychain-linked credentials, and per-host session logs/history. Community evidence corroborates multi-session use in the field (e.g., managing multiple servers via saved snippets and SSH sessions), though performance complaints on Windows suggest some friction at scale. Missing for 10: independent hands-on verification of per-session appearance customization (themes/fonts) and no direct community testimony about running many concurrent tabs smoothly.
- [claimed-docs] “Workspaces group multiple terminal sessions into one focused environment... Broadcast the same input to multiple sessions”
- [claimed-docs] “Workspace templates capture: Included connections, Tab names, Layout configuration, Working directories, Running commands at the time of sav…”
- [claimed-docs] “Session logs are a record of your terminal activity. They help you review past work, troubleshoot issues, and collaborate with teammates.”
- [claimed-docs] “A group is a labeled collection of Hosts that share a common characteristic, such as a customer, location, or environment.”
- [community] “Combination of Termius's saved snippets and short shell scripts let me do monitoring without running a separate web-server behind auth. Easi…”
- [community] “Termius on Windows falls short of usability threshold due to slow performance at high resolutions—scrolling large text is much worse than gn…”
power-userKeep my terminal session alive across network changes and device sleep
weight 3 · not comparableA single community comment confirms Termius supports Mosh, which enables sessions to survive network changes, and another notes remote debugging while mobile, suggesting some resilience to connectivity drops. However there is no first-party documentation describing session persistence across network changes or device sleep, and no evidence addressing behavior specifically during device sleep. missing for 10: first-party docs on Mosh/session-persistence feature, explicit device-sleep resilience evidence, independent verification beyond one HN comment.
- [community] “Saved my butt once when my docker containers were bouncing while on vacation—debugged and deployed a fix from my iPhone while my wife drove.…”
- [community] “Wow, this app saved my butt over a year ago when I ran out of laptop battery in the field.”
power-userCustomize the font, colors, and cursor appearance of my terminal and persist the settings
weight 2 · not comparableTermiusnone0/10No vendor documentation describes font, color, or cursor customization for Termius, and a community report explicitly states the user could not add custom fonts, indicating this capability is not evidenced or is missing.
- [community] “Not sure if I missed something, but I can't add custom fonts.”