Blink Shell vs a-Shell
Blink Shell wins · 9–4 (12 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 drawnBlink Shellnone0/10Probe confirms no llms.txt exists (404) and no agent-oriented API docs are found; Blink Shell is a terminal/SSH client with no evidence of agent-friendly documentation.
a-Shellnone0/10Probe 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…”
ai-native userDrive the product through a documented public API
weight 3 · round drawnBlink Shellnone0/10No public API or SDK is documented; probes for llms.txt and OpenAPI/Swagger specs all returned 404, and no evidence pack item describes a programmatic/API interface for driving Blink Shell.
a-Shellnone0/10a-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…”
Api quality
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnBlink Shellnone0/10Blink Shell is a terminal/SSH client, not an API-providing service, but the axis was probed and no machine-readable API spec exists — probes show 404 for llms.txt and all OpenAPI/swagger candidate paths, and no docs mention any API spec.
a-Shellnone0/10a-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.
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userDefine rules that trigger actions automatically on events
weight 3 · round drawnBlink Shellnone0/10No evidence Blink Shell supports defining rules or triggers for automated actions on events; it is a terminal/SSH/Mosh client with no automation-rule engine documented.
ai-native userSchedule recurring jobs or workflows
weight 2 · round drawnBlink Shellnone0/10Blink Shell is a terminal/SSH/Mosh client; there is no evidence of any scheduling, cron-like, or recurring workflow/job automation capability in the docs or community discussion.
Git code — core git and code operations — cloning, branching, pushing, code browsingGit code
Core git and code operations — cloning, branching, pushing, code browsing
Repo management
developerClone Git repositories over HTTPS, SSH, or the Git protocol
weight 3 · round drawnBlink Shellnone0/10Blink Shell's documented built-in commands (cat, grep, wc, cd, ls, etc.) do not include git, and no evidence pack item shows native git clone support over HTTPS, SSH, or git protocol; it only documents scp/sftp for file transfer and ssh/mosh for remote sessions, implying git operations would need to happen on a remote server, not natively in Blink.
- [claimed-docs] “cat, grep, wc, cd, setenv, ls, touch, cp, rm, ln, mv, mkdir, rmdir, df, du”
- [github] “scp user@host.name.edu:filename . sftp localFilename user@host.name.edu:~/”
developerCommit and push changes directly from my device
weight 3 · round to Blink ShellBlink is an SSH/Mosh terminal client that connects to remote hosts (including VS Code servers, GitHub Codespaces, GitPod) where a developer could run git commands, but the evidence never mentions git itself, a git client, or any explicit commit/push workflow — it's an indirect capability via a generic shell rather than a documented feature. missing for 10: explicit mention of git support, any documented git commit/push workflow, hands-on confirmation of using git from within Blink.
- [claimed-docs] “A coding experience fitted to your device, that connects to Microsoft Visual Studio Code for web, GitHub Codespaces, GitPod or your own VS C…”
- [claimed-docs] “Work on local projects, or seamlessly on remote machines thanks to Blink Files.”
- [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
- [claimed-docs] “cat, grep, wc, cd, setenv, ls, touch, cp, rm, ln, mv, mkdir, rmdir, df, du”
power-userSign my commits with a GPG or SSH key for verification
weight 1 · round drawnBlink Shellnone0/10Blink Shell is an SSH/Mosh terminal client; evidence covers SSH key pair generation for server login, but there is no mention of GPG or SSH commit signing for git operations anywhere in the docs or community discussion.
developerReview pull requests from my phone while on the go
weight 3 · round to Blink ShellBlink Shell is a mobile terminal/SSH client that lets developers connect to remote dev environments (SSH, Mosh, VS Code for web, GitHub Codespaces, GitPod) where command-line git tools or web-based review could be used, but the evidence pack never mentions git, GitHub, gh CLI, or any PR-review-specific feature. This is a generic terminal capability stretched to cover the story rather than a documented PR-review workflow. Missing for 10: explicit git/GitHub CLI support, PR/diff viewing UI or workflow, mobile-optimized review tooling, and any user/community confirmation of doing PR reviews via Blink.
- [claimed-docs] “A coding experience fitted to your device, that connects to Microsoft Visual Studio Code for web, GitHub Codespaces, GitPod or your own VS C…”
- [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
- [claimed-docs] “Work on local projects, or seamlessly on remote machines thanks to Blink Files.”
a-Shellnone0/10a-Shell is a terminal/shell app for iOS with git-like command-line tools, but the evidence pack shows no PR review functionality, no GitHub/GitLab integration for reviewing diffs, comments, or approvals from mobile. Nothing indicates a UI or workflow for browsing/reviewing pull requests.
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 to Blink ShellBlink Shell is a direct SSH/Mosh client built on libssh, connecting straight to hosts via hostname/user with no cloud relay or VPN required, and this is corroborated by community reviews praising its solid direct connectivity and open-source transparency. Missing for 10: independent technical audit confirming no telemetry/relay involvement, and no explicit statement ruling out any proxy usage.
- [claimed-docs] “In Blink type mosh [user@]hostname. For example : mosh irwin@irwinvb.”
- [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
- [claimed-docs] “Hosts: create hosts that can be accessed with only the hostname.”
- [claimed-docs] “Supports Ed25519, ECDSA and RSA keys. It is built on top of libssh and libssh2.”
- [community] “Been using it (beta testing on iPhone and paid version on iPad so I can compare) for a while. Improving steadily, solid connectivity. So far…”
- [community] “Bought it even though it apparently has no agent forwarding... Pretty good, refresh seems faster than Prompt, especially when using htop and…”
a-Shellnone0/10The 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.
Offline sync — stories about offline sync in this arenaOffline sync
Stories about offline sync in this arena
Cross device sync
developerAccess and work with files and repositories from other apps' sandboxes on my device
weight 2 · round to a-ShellBlink Files (docs-8) enables working with local and remote projects, and drag-and-drop selection lets users move content to/from other apps (docs-16), suggesting some file interoperability with other apps' sandboxes, but there's no explicit documentation of Files-app document-provider integration or direct access to another app's sandboxed storage/repos. missing for 10: explicit Files app/document-provider integration details, concrete examples of accessing another app's sandbox, independent corroboration of this capability.
- [claimed-docs] “Work on local projects, or seamlessly on remote machines thanks to Blink Files.”
- [claimed-docs] “To start selection mode, Tap and drag. You can drag selections to other apps, or from other apps into Blink.”
a-Shell explicitly supports accessing other apps' sandboxed directories via the `pickFolder` command using iOS 13's app sandbox access API, plus bookmarking directories for repeated use, enabling developers to work with files/repos across app sandboxes directly from the shell. Missing for 10: no explicit mention of git/repository workflows using this feature, and no independent/hands-on corroboration of pickFolder working reliably in practice.
power-userSync my saved hosts and connection settings across all my devices
weight 2 · round drawnBlink Shellnone0/10There is no evidence of cross-device sync for hosts/settings; in fact a community comment explicitly requests this feature ('Could you consider adding config sync via iCloud/Dropbox? It's quite a pain to sync host lists across several iOS devices'), indicating it was not available.
- [community] “Could you consider adding config sync via iCloud/Dropbox? It's quite a pain to sync host lists across several iOS devices.”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userRead the product's source under an open license
weight 2 · round to Blink ShellGitHub repo (blinksh/blink) is publicly available and community notes describe it as an open-source development process on GitHub, but the license itself is disputed—one commenter questions GPL compatibility with the App Store, and no evidence pack item explicitly names or confirms an OSI-approved open license for the source. missing for 10: explicit license file/name confirmation, resolution of the GPL/App Store tension, first-party statement of licensing terms.
- [github] “If you would like to participate on its development, we would love to have you on board! There are two ways to collaborate with the project:…”
- [community] “The way in which Blink really blows the competition (e.g. Prompt) out of the water is its open source development process... Carlos [is] hig…”
- [community] “I thought GPL was incompatible with the App Store? Wasn't VLC famously pulled from the App Store over a complaint about this?”
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…”
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 drawnBlink Shellnone0/10No evidence anywhere in the pack mentions Face ID, Touch ID, biometric authentication, or fingerprint-based unlock/authentication for Blink Shell; the security features documented are SSH key types and password-less key auth only.
- [claimed-docs] “Supports Ed25519, ECDSA and RSA keys. It is built on top of libssh and libssh2.”
- [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
power-userStore my SSH keys in a hardware-backed secure enclave protected by biometrics
weight 2 · round drawnBlink Shellnone0/10Evidence shows Blink Shell supports creating SSH key pairs (docs-12) but there is no mention of hardware-backed secure enclave storage or biometric protection for keys anywhere in the docs, GitHub, or community discussion.
- [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
a-Shellnone0/10No 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.
Terminal ssh — terminal and SSH workflows — shells, sessions, remote accessTerminal ssh
Terminal and SSH workflows — shells, sessions, remote access
Local dev environment
developerEdit files with a terminal-based editor and run syntax/lint checkers inside the app
weight 2 · round to a-ShellBlink Shellnone0/10Blink Shell is documented as an SSH/mosh terminal with a small set of built-in local commands (cat, grep, wc, cd, ls, etc.) and its 'coding experience' feature explicitly delegates editing to external VS Code servers/Codespaces/Gitpod rather than a built-in terminal editor. No evidence describes a bundled terminal-based text editor (e.g., vim/nano) or any built-in syntax/lint checking capability inside the app itself.
- [claimed-docs] “cat, grep, wc, cd, setenv, ls, touch, cp, rm, ln, mv, mkdir, rmdir, df, du”
- [claimed-docs] “A coding experience fitted to your device, that connects to Microsoft Visual Studio Code for web, GitHub Codespaces, GitPod or your own VS C…”
- [claimed-docs] “Work on local projects, or seamlessly on remote machines thanks to Blink Files.”
a-Shell ships Vim for file editing and explicitly documents running syntax checkers via vim-lsp/ALE, plus compilers (clang) for building/checking C/C++ code. However, evidence lacks detail on lint checker installation/setup specifics, dedicated linters for other languages, or hands-on confirmation of this workflow succeeding. missing for 10: independent/hands-on verification of lint checker setup, broader language linting support beyond vim-lsp/ALE mention.
- [claimed-docs] “a-Shell comes with Vim included. You can edit your files and even run syntax checkers using e.g. vim-lsp or ALE.”
- [claimed-docs] “clang/clang++ compiles your C/C++ files to webAssembly with wasi included. Execute the resulting files using 'wasm command'.”
developerInstall additional pure-Python packages using pip directly on my device
weight 2 · round to a-ShellBlink Shellnone0/10Blink Shell's evidence describes it as an SSH/Mosh terminal client with a small set of built-in local commands (cat, grep, wc, ls, etc.) and remote connectivity features; there is no mention of a bundled Python runtime or pip package management on-device. No evidence supports installing pure-Python packages locally.
- [claimed-docs] “cat, grep, wc, cd, setenv, ls, touch, cp, rm, ln, mv, mkdir, rmdir, df, du”
a-Shell's official docs explicitly state pip install works for pure-Python packages directly on-device, matching the story exactly. missing for 10: independent hands-on confirmation of pip install working, and details on limitations (e.g. packages requiring compiled extensions).
- [claimed-docs] “Use 'pip install' to add more Python packages (if they are pure Python).”
Ssh connections
power-userGroup multiple terminal sessions together and broadcast the same command to all of them
weight 2 · round drawnBlink Shellnone0/10Evidence shows Blink supports multiple shells, split view, and switching between sessions, but there is no mention of grouping sessions or broadcasting a single command to multiple sessions simultaneously.
a-Shellnone0/10a-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…”
developerTransfer files to and from remote hosts via scp and sftp using my configured keys
weight 2 · round to Blink ShellGitHub docs explicitly show scp and sftp usage examples with remote hosts, and Blink supports configured SSH keys (Ed25519, ECDSA, RSA) for authentication per docs, confirming key-based scp/sftp transfers work. Missing for 10: independent hands-on verification of scp/sftp specifically (community discussion focuses mostly on ssh/mosh) and no detail on edge cases like large file transfer performance.
- [github] “scp user@host.name.edu:filename . sftp localFilename user@host.name.edu:~/”
- [claimed-docs] “Supports Ed25519, ECDSA and RSA keys. It is built on top of libssh and libssh2.”
- [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
developerRun local UNIX commands like ls, grep, cat, tar, and curl directly in the app
weight 3 · round to Blink ShellDocs explicitly list built-in commands including ls, grep, cat, cd, touch, cp, rm, mv, mkdir, df, du (blink-shell-docs-4) and file transfer via scp/sftp (blink-shell-gh-1), covering much of the 'run local UNIX commands' story. However, tar and curl are never mentioned anywhere in the evidence pack, so support for those specific commands is unconfirmed. missing for 10: explicit documentation or confirmation that tar and curl are supported as local commands, independent hands-on verification of command behavior.
- [claimed-docs] “cat, grep, wc, cd, setenv, ls, touch, cp, rm, ln, mv, mkdir, rmdir, df, du”
- [github] “scp user@host.name.edu:filename . sftp localFilename user@host.name.edu:~/”
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).”
power-userOpen multiple terminal sessions, each with its own context, appearance, and history
weight 3 · round to a-ShellDocs confirm multiple shells can be opened (two-finger tap to create, swipe to switch) and each session can persist via Mosh even after sleep, plus per-shell customization via themes/fonts and hosts. However, there's no explicit evidence that each session maintains fully independent appearance/history configuration simultaneously (e.g., per-tab theme or scrollback isolation) beyond global settings. Missing for 10: documented per-session independent history/appearance settings, and independent corroboration of multi-session workflows beyond basic split-view/switching.
- [claimed-docs] “To create a new shell, tap the screen with two fingers. To switch between active shells, swipe side to side.”
- [claimed-docs] “don't be afraid to put your device to sleep, when you wake it up later, your connections will be intact.”
- [claimed-docs] “You can flawlessly jump from home, to the train, and then to the office thanks to Mosh. Blink is rock-solid connected all the way.”
- [claimed-docs] “You can rock your terminal and roll your own themes and fonts beyond our included ones. And yes, we include Pragmata Pro by default!”
- [github] “We've incorporated SplitView, for those necessary Google searches and chats with coworkers.”
- [claimed-docs] “Hosts: create hosts that can be accessed with only the hostname.”
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…”
developerConnect to remote servers using SSH with Ed25519, ECDSA, or RSA keys
weight 3 · round to Blink ShellDocs explicitly confirm support for Ed25519, ECDSA, and RSA keys via libssh/libssh2, with key pair creation and hostname-based ssh usage documented, and community discussion corroborates Ed25519 support as a differentiator from competitors. Missing for 10: independent hands-on verification of ECDSA/RSA specifically (community focus is mostly on Ed25519).
- [claimed-docs] “Supports Ed25519, ECDSA and RSA keys. It is built on top of libssh and libssh2.”
- [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
- [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
- [community] “Does it support Ed25519 keys? This is one of the things that Panic's Prompt still lack support of, and I really miss it.”
power-userGenerate SSH key pairs for password-less access to my servers
weight 2 · round to Blink ShellOfficial docs explicitly describe the 'Keys' feature for creating SSH key pairs for password-less server access, supporting Ed25519, ECDSA, and RSA, corroborated by community discussion confirming Ed25519 support (a differentiator vs competitors). Missing for 10: independent hands-on verification of the key-generation UX itself beyond docs description.
- [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
- [claimed-docs] “Supports Ed25519, ECDSA and RSA keys. It is built on top of libssh and libssh2.”
- [community] “Does it support Ed25519 keys? This is one of the things that Panic's Prompt still lack support of, and I really miss it.”
power-userConnect to a saved host with one tap without re-entering credentials
weight 2 · round to Blink ShellDocs confirm saved 'Hosts' allow access via just hostname, SSH key pairs enable password-less login, and connections persist through sleep/network changes via Mosh — together supporting one-tap reconnection to saved hosts without re-entering credentials. missing for 10: no explicit demonstration of a literal one-tap UI flow, and no independent hands-on account specifically validating passwordless saved-host connection.
- [claimed-docs] “Hosts: create hosts that can be accessed with only the hostname.”
- [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
- [claimed-docs] “don't be afraid to put your device to sleep, when you wake it up later, your connections will be intact.”
- [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
a-Shellnone0/10No 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…”
Ux ergonomics — stories about ux ergonomics in this arenaUx ergonomics
Stories about ux ergonomics in this arena
Terminal customization
power-userCustomize the font, colors, and cursor appearance of my terminal and persist the settings
weight 2 · round drawnDocs confirm custom fonts/themes support with Pragmata Pro included by default and that users can 'roll your own' fonts/themes, but there's no explicit mention of persisted settings, cursor appearance customization, or color-scheme granularity beyond fonts/themes. missing for 10: dedicated docs on color scheme/cursor customization, explicit confirmation settings persist across sessions/devices, independent hands-on corroboration of theming.
- [claimed-docs] “You can rock your terminal and roll your own themes and fonts beyond our included ones. And yes, we include Pragmata Pro by default!”
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…”
Not comparable on these axes
ai-native userRun the product headlessly / in CI for automation
weight 2 · not comparableBlink Shelln/aBlink Shell is an iOS/iPadOS terminal/SSH client app designed for interactive mobile use; running it headlessly or in a CI pipeline is a category mismatch as it has no server/daemon mode or CI-oriented interface.
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/mosh client for iOS, not an AI agent or MCP-capable platform; MCP server integration is outside its product category.
ai-native userConnect an agent via an official MCP server
weight 3 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for iOS, not an AI agent or coding assistant; there is no indication it plays the agent role nor offers an MCP server role. Connecting to AI-coding tools like VS Code Server/Codespaces is client-side usage, not an official MCP server axis, so this story is a category error for this product type.
ai-native userUse an official CLI
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client app, not an AI agent or developer platform for which an 'official CLI for AI-native workflows' would be a meaningful axis; it is itself a shell/CLI tool, not something with a separate AI-oriented CLI product to evaluate.
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).”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client for iOS, not an agent-management or API-credential-issuing platform; there is no concept of scoped API credentials for agents in its feature set. This axis is a category error for this product type.
ai-native userBuild against official SDKs
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client app, not a platform or service with an SDK/API surface for developers to build against; the story of building against official SDKs is a category error for this product type.
ai-native userSubscribe to events via webhooks
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client app, not a service or platform with an event system; webhooks are not a fair capability for this kind of product.
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client; AI-generated insights from data is a wrong-axis capability for this product category, not something a terminal emulator would plausibly ship.
ai-native userSet up automations that run autonomously in the background
weight 2 · not comparableBlink Shelln/aBlink Shell is a mobile SSH/Mosh terminal client, not an automation/agent platform; there's no concept of background autonomous automations in its feature set. This axis is a category error for a terminal client rather than a missing feature.
a-Shellnone0/10a-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.
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for iOS; nothing in the evidence indicates a built-in AI assistant feature. This story is a category error for this product type — a terminal emulator does not deliver AI-agent delegation itself.
ai-native userOperate the product with natural-language commands
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client for iOS; the evidence shows only standard shell commands, key management, and terminal UI features, with no natural-language or AI command interface of any kind. This axis (operating via natural-language commands, agenticness) is a category mismatch for a traditional terminal emulator, not a missing feature it could plausibly ship as part of its product identity.
a-Shellnone0/10a-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…”
ai-native userExplore an interactive API reference with runnable examples
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client app, not an API-driven platform or SDK; an interactive API reference with runnable examples is not a relevant capability for this product category.
a-Shellnone0/10a-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…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client for connecting to remote hosts; it has no concept of sandbox environments or production/test data separation - that's an axis for testing/dev platforms, not a terminal emulator app.
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client app, not a platform offering a programmatic API for third-party/agent integration; the story of versioned APIs with a deprecation policy is a category error for this product type.
ai-native userPerform bulk operations across many items at once
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client for iOS; bulk operations across many items is not a fair capability for this kind of product—it's a terminal emulator, not a batch-processing or automation platform.
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…”
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client for iOS, not an automation platform with workflows or agent scripts that could be versioned, reviewed, or rolled back; this axis is a category error for this product type.
power-userAmend the latest commit or undo unpushed commits to fix or split them
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for iOS, not a git tool; git commit editing is a wrong-axis capability for a terminal emulator itself (any git operations would occur via a remote shell's own git binary, not Blink Shell functionality).
developerSearch and navigate code content using fuzzy matching, filters, and regular expressions
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for iOS, not a code search or navigation tool; it provides basic Unix utilities like grep but no fuzzy matching, code-aware filters, or regex-based code navigation features. This axis is a category error for a terminal emulator app.
a-Shellnone0/10The evidence pack shows a-Shell as an iOS terminal app with grep, help search, and vim, but no evidence of dedicated fuzzy-matching code search, filters, or regex-based code navigation tooling like fzf, ripgrep, or ctags integration.
- [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] “a-Shell comes with Vim included. You can edit your files and even run syntax checkers using e.g. vim-lsp or ALE.”
power-userVisualize the full commit graph across branches
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for mobile devices, not a git tool or GUI for visualizing commit history; git graph visualization is outside its product category.
power-userInteractively rewrite history by deleting, editing, squashing, or reordering commits
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for iOS, not a git tool or version control interface; interactive rebase/history rewriting is a git-code capability entirely outside its product category (though a user could run git commands via a remote shell, that's not a feature of Blink itself).
developerResolve merge conflicts across many files at once with a dedicated tool
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for iOS; it provides shell access to remote machines but has no built-in merge-conflict resolution tooling. Resolving merge conflicts is a git-tooling/IDE feature, not something a terminal emulator would plausibly ship, so this axis is a category error for this product.
developerCreate pull requests on hosted Git platforms directly from my device
weight 3 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/mosh client for iOS; it provides shell access and code-editor integrations but has no Git platform integration for creating pull requests. This is a category error—PR creation is a GitHub/GitLab web-workflow feature, not something a terminal emulator app would surface directly (users could only do it via git CLI/gh CLI inside a remote shell, which is the remote host's tooling, not Blink's).
power-userStash and unstash changes to temporarily clear my working directory
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for iOS; git stash/unstash is a git version-control operation, not a function of a terminal emulator itself. This is a category error — the axis belongs to a git tool or IDE, not a shell/SSH client.
power-userClone, update, and manage Git submodules within a repository
weight 1 · not comparableBlink Shelln/aBlink Shell is an SSH/Mosh terminal client; any git operations would rely entirely on the remote host's own git binary, not a Blink-native capability. Git submodule management is not a feature category this type of product ships, so the axis does not apply.
developerPreview Markdown, HTML, and other rendered files with live reload
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client, not a file preview or rendering tool; live-reload preview of Markdown/HTML is outside its category.
a-Shellnone0/10a-Shell is a terminal/shell app with vim editing and command-line tools, but there is no evidence of any Markdown/HTML preview or live-reload rendering capability.
- [claimed-docs] “a-Shell comes with Vim included. You can edit your files and even run syntax checkers using e.g. vim-lsp or ALE.”
- [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…”
power-userRoute all my internet traffic through a specific device on my network using an exit node
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for iOS/iPadOS, not a VPN or network-routing tool; 'exit node' traffic routing (e.g., VPN mesh networking) is a completely different product category and wrong axis for this kind of tool.
developerGet secure infrastructure access to resources wherever they live, including Kubernetes clusters
weight 3 · not comparableBlink Shellnone0/10Blink Shell provides SSH/Mosh terminal access to hosts, but there is no evidence of any Kubernetes-specific integration (kubectl exec, kubeconfig management, cluster access) or broader infrastructure-access features beyond generic SSH to named hosts.
developerUse subnet routers to reach devices outside my local network as if I were on it
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for iOS, not a VPN or network-mesh product; subnet routing to reach devices as if on the local network is a VPN-style capability entirely outside its category (wrong axis).
ai-native userDo everything through the API that I can do in the UI
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client app, not a service with a programmatic API surface distinct from its UI; the notion of an API replicating UI functionality is a category mismatch for this product type.
ai-native userExport all of my data in open formats and leave
weight 3 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client app, not a data-storage or SaaS platform that accumulates user data subject to export; there is no 'user data' corpus (documents, records, etc.) to export in the sense this story implies. Data export/lock-in is a category mismatch for a shell/terminal emulator.
a-Shellnone0/10a-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…”
ai-native userSelf-host the core product
weight 3 · not comparableBlink Shelln/aBlink Shell is a client-side terminal/SSH app that runs locally on the user's device and connects to servers the user already controls; there is no hosted backend or SaaS component for an 'ai-native' user to self-host. The self-hosting axis applies to server/platform products, not to a local iOS client app, so this is a category mismatch rather than a missing capability.
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableBlink Shelln/aBlink Shell is a local terminal/SSH client app, not a data-storage or cloud service; data residency/region selection is not a meaningful axis for this product category.
ai-native userPrevent my data from being used to train AI models
weight 3 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client, not an AI model or AI service that trains on user data; the question of preventing data being used for AI training is a category error for this product type.
ai-native userControl data retention and deletion
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for iOS; it does not process or store user data on behalf of an AI service, so data retention/deletion controls are a category error for this kind of product.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableBlink Shellnone0/10No evidence in the pack mentions telemetry, analytics, usage tracking, or any opt-out/privacy settings for Blink Shell; the evidence is entirely about SSH/Mosh features, UI, and community feedback unrelated to data collection.
ai-native userHave an AI agent analyze my pull requests and suggest code improvements from my phone
weight 3 · not comparableBlink Shelln/aBlink Shell is a mobile SSH/mosh terminal client; it provides connectivity and file transfer to remote hosts but has no AI agent, PR analysis, or code-review capability of its own. This is a category error for a terminal client, not a missing feature.
ai-native userGet AI-generated commit message suggestions based on my staged changes
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client for iOS, not a git or AI tool; there is no evidence of git integration or AI features at all, and generating commit messages is outside its product category (terminal emulator/SSH client).
ai-native userDirect an AI agent to browse, search, edit, commit, pull, and push in a repository via conversation
weight 3 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH client for iOS, not an AI agent or agentic coding tool; there is no evidence of any AI agent integration for directing conversational browse/search/edit/commit/pull/push workflows. This story presumes an AI-native agent product, which is the wrong axis for a terminal emulator.
a-Shellnone0/10a-Shell is an iOS terminal app with git-like commands and vim available, but there is no evidence of any AI agent integration, conversational control, or automation for browsing/searching/editing/committing/pulling/pushing via an AI agent — the evidence only covers manual shell usage, Shortcuts, and UI features.
ai-native userAssign an issue to an AI coding agent and receive a ready-to-review pull request
weight 3 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for iOS; it has no agent-assignment or autonomous coding-agent workflow that produces pull requests. This capability is entirely outside its product category (terminal emulator/remote shell), not a failed axis.
ai-native userConverse with an AI agent in natural language to get insights into repositories and open pull requests
weight 2 · not comparableBlink Shelln/aBlink Shell is an SSH/Mosh terminal client for iOS; it has no AI agent, chat interface, or repository/PR insight capability. This story concerns AI-native conversational agent features, which is entirely outside Blink Shell's product category as a terminal emulator.
developerManage and track cloud-based coding agent tasks from my phone
weight 2 · not comparableBlink Shelln/aBlink Shell is a terminal/SSH/Mosh client for connecting to remote shells; it has no concept of cloud-based coding agent task management or tracking. This story is a category error for a terminal emulator, not a missing feature.
ai-native userDescribe what I want in plain language and have the tool generate the corresponding shell command
weight 2 · not comparableBlink Shelln/aBlink Shell is an SSH/Mosh terminal client for iOS; it has no natural-language-to-shell-command generation feature. This is a wrong axis for a terminal emulator/SSH client—no evidence suggests it offers any AI/NLP command generation capability.
developerStore credentials once in a secure vault and reference them from multiple hosts
weight 2 · not comparableBlink documents separate 'Keys' and 'Hosts' management features, implying SSH keys can be created once and associated with host entries for password-less access, which aligns with a credential-vault-and-reuse pattern. However, there is no explicit documentation confirming a single stored key can be referenced across multiple distinct hosts, no mention of encryption-at-rest or vault security guarantees, and no independent/community confirmation of this specific reuse workflow. Missing for 10: explicit multi-host key reuse documentation, vault security/encryption details, and independent corroboration of the workflow.
- [claimed-docs] “Hosts: create hosts that can be accessed with only the hostname.”
- [claimed-docs] “Keys: Create SSH key pairs for a more secure, password-less access to your servers.”
- [claimed-docs] “In Blink type ssh [user@]hostname. For example : ssh irwin@irwinvb.”
power-userKeep my terminal session alive across network changes and device sleep
weight 3 · not comparableBlink Shell is built around Mosh, explicitly marketed for surviving network changes (train, home, office) and device sleep with connections remaining intact, backed by docs and community praise of solid connectivity. Missing for 10: independent hands-on verification specifically testing sleep/network-switch persistence rather than general connectivity praise.
- [claimed-docs] “You can flawlessly jump from home, to the train, and then to the office thanks to Mosh. Blink is rock-solid connected all the way.”
- [claimed-docs] “don't be afraid to put your device to sleep, when you wake it up later, your connections will be intact.”
- [claimed-docs] “In Blink type mosh [user@]hostname. For example : mosh irwin@irwinvb.”
- [community] “Been using it (beta testing on iPhone and paid version on iPad so I can compare) for a while. Improving steadily, solid connectivity. So far…”
- [community] “Bought it even though it apparently has no agent forwarding... Pretty good, refresh seems faster than Prompt, especially when using htop and…”