Termius vs a-Shell

Agent access

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

   weight 2 · round to Termius
   Termius✓fullprobed8/10

   A 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…”

   proof ↗⚑ flag

   a-Shell—none0/10

   Probe of llms.txt returns 404 and no agent-oriented docs or API spec are found anywhere in the evidence pack; a-Shell provides only standard shell/vim/help docs.

   • [probe] “PROBE llms.txt: HTTP 404 at https://holzschu.github.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://holzschu.github.io/openapi.json, https://holzschu.github.io/swagger.json, https://holzschu.g…”
   • [github] “For help, type `help` in the command line. `help -l` lists all the available commands. `help -l | grep command` will tell you if your favori…”

   proof ↗⚑ flag

2. ai-native userUse an official CLI

   weight 2 · round to a-Shell
   Termius—none0/10

   The 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…”

   proof ↗⚑ flag

   a-Shell~partialclaimed4/10

   a-Shell is itself a full command-line environment on iOS with many built-in commands and Apple Shortcuts integration that lets users script and automate shell tasks, which could be leveraged by an AI-driven automation. However, there is no evidence of any AI-specific CLI features, agent APIs, or documented AI-native workflow support beyond generic shell scripting/Shortcuts. Missing for 10: explicit AI-agent integration, documented programmatic/automation API beyond Shortcuts, any mention of AI-native use cases.

   • [github] “a-Shell is compatible with Apple Shortcuts, giving users full control of the Shell. You can write complex Shortcuts to download, process and…”
   • [github] “For help, type `help` in the command line. `help -l` lists all the available commands. `help -l | grep command` will tell you if your favori…”
   • [claimed-docs] “Use 'pip install' to add more Python packages (if they are pure Python).”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Termius—none0/10

   No 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…”

   proof ↗⚑ flag

   a-Shell—none0/10

   a-Shell offers Apple Shortcuts integration and a CLI command set, but there is no documented public API (REST/OpenAPI/SDK) for programmatic control; explicit probes for llms.txt and OpenAPI specs both returned 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://holzschu.github.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://holzschu.github.io/openapi.json, https://holzschu.github.io/swagger.json, https://holzschu.g…”
   • [github] “a-Shell is compatible with Apple Shortcuts, giving users full control of the Shell. You can write complex Shortcuts to download, process and…”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Termius
   Termius~partialclaimed4/10

   Termius 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   a-Shell is a terminal/shell app for iOS providing Unix commands, Python, Vim, and Shortcuts integration, but no evidence shows any AI-generated insights, suggestions, or data analysis features.

   ⚑ flag

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

   weight 2 · round drawn
   Termius—none0/10

   Termius 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.

   ⚑ flag

   a-Shell—none0/10

   a-Shell is an iOS terminal app with no evidence of background execution, scheduling, or autonomous automation capability—Shortcuts integration allows manual triggering but not persistent background automation, and iOS sandboxing generally prevents apps like this from running unattended tasks.

   ⚑ flag

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

   weight 3 · round to Termius
   Termius~partialclaimed4/10

   Termius 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   a-Shell is a terminal/shell app for iOS with Unix commands, Python, Vim, etc., but no evidence anywhere in the pack of a built-in AI assistant or any AI delegation capability.

   ⚑ flag

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

   weight 2 · round to Termius
   Termius~partialclaimed5/10

   Termius 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   a-Shell is a traditional command-line shell requiring exact command syntax (e.g. clang, vim, pip install, config, bookmark); there is no evidence of natural-language command parsing or AI-native interaction, and llms.txt/openapi probes returned 404.

   • [github] “For help, type `help` in the command line. `help -l` lists all the available commands. `help -l | grep command` will tell you if your favori…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://holzschu.github.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://holzschu.github.io/openapi.json, https://holzschu.github.io/swagger.json, https://holzschu.g…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Termius—none0/10

   Termius 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…”

   proof ↗⚑ flag

   a-Shell—none0/10

   a-Shell is a mobile terminal app with a `help` command listing built-ins, but there's no evidence of an interactive API reference with runnable examples; probes for llms.txt and OpenAPI specs both returned 404.

   • [probe] “PROBE llms.txt: HTTP 404 at https://holzschu.github.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://holzschu.github.io/openapi.json, https://holzschu.github.io/swagger.json, https://holzschu.g…”
   • [github] “For help, type `help` in the command line. `help -l` lists all the available commands. `help -l | grep command` will tell you if your favori…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Termius—none0/10

   A 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…”

   proof ↗⚑ flag

   a-Shell—none0/10

   a-Shell is a terminal app with no API surface, and probes for OpenAPI/Swagger specs and llms.txt all returned 404, confirming no machine-readable API spec is published.

   • [probe] “PROBE llms.txt: HTTP 404 at https://holzschu.github.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://holzschu.github.io/openapi.json, https://holzschu.github.io/swagger.json, https://holzschu.g…”

   proof ↗⚑ flag

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

   weight 2 · round to Termius
   Termius✓fullcommunity8/10

   Termius 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…”

   proof ↗⚑ flag

   a-Shell~partialclaimed3/10

   a-Shell is a full Unix-like shell environment and its Shortcuts integration is described as enabling users to 'download, process and release files using a-Shell commands,' implying scripting-based batch workflows, but no evidence explicitly documents loop constructs, xargs, or batch file processing across many items. Missing for 10: explicit documentation of scripting/looping over multiple files, examples of bulk file processing, independent corroboration of batch workflows.

   • [github] “a-Shell is compatible with Apple Shortcuts, giving users full control of the Shell. You can write complex Shortcuts to download, process and…”
   • [github] “For help, type `help` in the command line. `help -l` lists all the available commands. `help -l | grep command` will tell you if your favori…”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Termius—none0/10

   Termius 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   a-Shell is an iOS terminal app; evidence shows shell commands, Shortcuts integration, and window management, but no rule-based automation engine (triggers/conditions/actions on events) is documented anywhere in the pack.

   ⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Termius—none0/10

   Termius 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.

   ⚑ flag

   a-Shell—none0/10

   No evidence of any cron-like scheduler or recurring job/workflow mechanism in a-Shell; Shortcuts integration allows triggering commands but no scheduling capability is documented. This is an applicable axis for a shell/terminal app, but no supporting evidence exists.

   ⚑ flag

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

   weight 1 · round drawn
   Termius—none0/10

   Termius 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.

   ⚑ flag

   a-Shell—none0/10

   No evidence of any versioning, review, or rollback mechanism for automations/scripts; a-Shell offers command history, bookmarks, and Shortcuts integration but nothing about tracking changes or reverting automation scripts.

   ⚑ flag

Mesh network

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

   weight 2 · round to Termius
   Termius✓fullcommunity8/10

   Termius 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   The evidence pack contains no mention of SSH, SFTP, or any direct server-connection capability for a-Shell; it only covers compilation, Python packages, Vim, window management, Shortcuts integration, and accessibility. Since a terminal app plausibly could offer direct server connectivity, the axis applies, but no evidence documents it here.

   ⚑ flag

Cross device sync

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

   weight 2 · round to Termius
   Termius✓fullcommunity8/10

   Termius 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   No evidence of any host/connection management feature, let alone cross-device syncing of saved hosts or settings; a-Shell is a local iOS terminal app with no mentioned cloud sync capability for connection profiles.

   ⚑ flag

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

   weight 3 · round drawn
   Termius—none0/10

   Evidence 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…”

   proof ↗⚑ flag

   a-Shell—none0/10

   a-Shell's evidence pack shows it operates on files, config, and bookmarks, but there is no documentation or claim about an explicit data export mechanism, open-format guarantee, or ability to migrate history/config/bookmarks out of the app. The probes for llms.txt/openapi also returned 404s, showing no additional documentation on this front. Missing for 10: any statement on export formats, data portability tools, or guarantees that user data (history, bookmarks, config) isn't locked into a-Shell-specific formats.

   • [github] “Each window has its own context, appearance, command history and current directory. `newWindow` opens a new window, `exit` closes the curren…”
   • [github] “You can also bookmark the current directory with `bookmark`. `showmarks` will list all the existing bookmarks, `jump mark` and `cd ~mark` wi…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://holzschu.github.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://holzschu.github.io/openapi.json, https://holzschu.github.io/swagger.json, https://holzschu.g…”

   proof ↗⚑ flag

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

   weight 2 · round to a-Shell
   Termius—none0/10

   Termius 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…”

   proof ↗⚑ flag

   a-Shell~partialclaimed4/10

   The evidence confirms a-Shell's source lives in a public GitHub repository (holzschu/a-shell) with visible commands, structure, and documentation, implying the code is readable/inspectable. However, no evidence pack item cites an explicit open-source license (e.g., MIT, BSD, GPL) or license file. missing for 10: explicit license text/name, license badge or LICENSE file citation, confirmation of redistribution/modification rights.

   • [github] “Each window has its own context, appearance, command history and current directory. `newWindow` opens a new window, `exit` closes the curren…”
   • [github] “For help, type `help` in the command line. `help -l` lists all the available commands. `help -l | grep command` will tell you if your favori…”

   proof ↗⚑ flag

Ai coding agents

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

   weight 2 · round to Termius
   Termius~partialclaimed6/10

   Termius 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   No evidence a-Shell offers natural-language-to-command generation; it's a traditional shell/terminal app for iOS with no AI or NLP command-generation feature mentioned anywhere in docs, GitHub, or community posts.

   ⚑ flag

Credential protection

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

   weight 2 · round to Termius
   Termius✓fullclaimed8/10

   Termius 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   No evidence that a-Shell supports biometric authentication (Face ID/Touch ID) for securing remote connections such as SSH; the docs cover unrelated features like compiling, editing, and shell commands.

   ⚑ flag

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

   weight 2 · round to Termius
   Termius~partialcommunity6/10

   Termius 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…”

   proof ↗⚑ flag

   a-Shell—none0/10

   No evidence in the pack mentions SSH key storage, hardware-backed secure enclave, or biometric protection for a-Shell; the docs focus on shell commands, package installation, and appearance customization. This is a plausible security axis for a terminal app dealing with SSH, but absence of any supporting evidence means it must be marked none.

   ⚑ flag

Ssh connections

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

   weight 2 · round to Termius
   Termius✓fullclaimed8/10

   Termius 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   a-Shell supports multiple independent windows each with their own context (a-shell-gh-1), but there is no evidence of any mechanism to group sessions and broadcast a single command to all of them simultaneously.

   • [github] “Each window has its own context, appearance, command history and current directory. `newWindow` opens a new window, `exit` closes the curren…”

   proof ↗⚑ flag

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

   weight 2 · round to Termius
   Termius✓fullclaimed8/10

   Termius 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   No evidence pack item mentions scp, sftp, ssh key configuration, or remote file transfer capability in a-Shell; documentation covers compilers, Python packages, Vim, bookmarks, Shortcuts, and accessibility but nothing about SSH-based file transfer.

   ⚑ flag

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

   weight 3 · round to a-Shell
   Termius—none0/10

   All 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”

   proof ↗⚑ flag

   a-Shell~partialclaimed4/10

   The evidence confirms a-Shell is a genuine command-line environment (help/help -l lists commands, and the example 'help -l | grep command' implies grep is a working built-in), and it supports compiling/running code and pip installs, suggesting a real UNIX-like command set. However, the pack never explicitly documents ls, cat, tar, or curl as available commands. Missing for 10: explicit documentation or example usage of ls, cat, tar, and curl, and independent confirmation that these specific commands run natively.

   • [github] “For help, type `help` in the command line. `help -l` lists all the available commands. `help -l | grep command` will tell you if your favori…”
   • [claimed-docs] “clang/clang++ compiles your C/C++ files to webAssembly with wasi included. Execute the resulting files using 'wasm command'.”
   • [claimed-docs] “Use 'pip install' to add more Python packages (if they are pure Python).”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Termius✓fullcommunity8/10

   Termius 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…”

   proof ↗⚑ flag

   a-Shell✓fullclaimed8/10

   First-party GitHub docs confirm each window (multiple terminal sessions) has its own context, appearance, command history, and current directory, with `newWindow` to open additional sessions and `config` to customize appearance per session. Missing for 10: independent hands-on corroboration specifically of multi-window session isolation (community comments are about an unrelated web demo/HN thread, not this feature).

   • [github] “Each window has its own context, appearance, command history and current directory. `newWindow` opens a new window, `exit` closes the curren…”
   • [github] “You can change the appearance of a-Shell using `config`. It lets you change the font, the font size, the background color, the text color an…”

   proof ↗⚑ flag

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

   weight 3 · round to Termius
   Termius✓fullcommunity9/10

   Termius 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.…”

   proof ↗⚑ flag

   a-Shell—none0/10

   No evidence in the pack mentions SSH functionality or key types (Ed25519, ECDSA, RSA) supported by a-Shell; documentation covers compiling, Python, Vim, and window/config features but nothing about SSH connectivity.

   ⚑ flag

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

   weight 2 · round to Termius
   Termius✓fullclaimed8/10

   Termius 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   No evidence in the pack mentions SSH key generation, ssh-keygen, or SSH functionality at all for a-Shell; the documentation covers compiling, Python, Vim, window management, and Shortcuts integration but nothing about SSH key pairs or passwordless server access.

   ⚑ flag

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

   weight 2 · round to Termius
   Termius✓fullcommunity8/10

   Docs 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.”

   proof ↗⚑ flag

   a-Shell—none0/10

   No evidence of saved-host SSH profiles, credential storage, or one-tap connect features; only bookmarks for directories and general shell features are documented.

   • [github] “You can also bookmark the current directory with `bookmark`. `showmarks` will list all the existing bookmarks, `jump mark` and `cd ~mark` wi…”
   • [github] “For help, type `help` in the command line. `help -l` lists all the available commands. `help -l | grep command` will tell you if your favori…”

   proof ↗⚑ flag

Terminal customization

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

   weight 2 · round to a-Shell
   Termius—none0/10

   No 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.”

   proof ↗⚑ flag

   a-Shell~partialclaimed6/10

   The `config` command explicitly supports changing font, font size, background color, text color, and cursor color/shape (a-shell-gh-2), directly matching the story's customization request. However, there is no documented evidence that these settings persist across sessions/app restarts, and community feedback (unrelated HN comments) doesn't corroborate the persistence or usability of these settings. missing for 10: explicit confirmation that config changes persist across sessions, independent/hands-on corroboration of the customization workflow.

   • [github] “You can change the appearance of a-Shell using `config`. It lets you change the font, the font size, the background color, the text color an…”

   proof ↗⚑ flag