Open-source project
blinksh/blink avatar
blinksh/blink

Blink Shell for iOS: a Mosh-based terminal you build yourself

Blink Mobile Shell for iOS (Mosh based)

7,019 stars763 forksSwiftGPL-3.0

At a glance

What is it?
Blink is a Swift terminal for iPhone and iPad that pairs SSH with Mosh for connections that survive network changes. It ships through the App Store, but the repository also documents a full self-build path with Xcode.
Who is it for?
Blink suits engineers who already run a Mosh server and want a real terminal on an iPad, and it suits anyone willing to build the Xcode project from source under GPL-3.0. It is the wrong tool if you need pipes in the local shell, if you cannot install Mosh on the remote host, or if you expect the repository to hand you a finished binary rather than a build recipe.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 6 days ago.
What is it written in?
Mainly Swift, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • blinksh/blink7,019 ★ · +70
Star history
Repository2026-09-232026-11-15
blinksh/blink6.9k7k

70 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The problem Blink solves on an iPad

A plain SSH session over a cellular link dies every time the device changes network. The README states that Mosh overcomes the unstable and intermittent connectivity associated with mobile connections, and that a Blink session can survive switching from home to a train to an office. That is the core claim: the transport, not the terminal emulator, is what makes the product. The second problem is rendering. The README says Blink uses Chromium's HTerm so that output such as dmesg appears immediately and difficult encodings render correctly. The audience is therefore narrow and specific: people who administer Unix servers and want to do it from an iPhone or iPad rather than from a laptop. The README is explicit that Blink was not built to fix a website on the go, which is a useful boundary. It is a working shell, not a convenience wrapper around a control panel.

Mosh, SSH and the local command set

Blink is written in Swift and the repository separates concerns into directories such as SSH/, Sessions/, BlinkConfig/, BlinkFiles/ and BlinkSnippets/. The remote side is handled by libssh2, OpenSSL, libmoshios and protobuf, all of which the build script fetches. The local side is different: Blink bundles a set of shell utilities inside ios_system.framework, which the README describes as precompiled. Those utilities include cd, ls, cp, rm, mkdir, chmod, gzip, tar, grep, wc, curl, scp and sftp. You can call them one at a time or drive them from small Python or Lua scripts. The README notes that redirection works with ">", "<" and "&>" but that there is no pipe. That single missing operator changes how you work: a long grep pipeline has to be rewritten as a script or run on the remote host instead. The scp and sftp commands are implemented by rewriting arguments into curl syntax, which the README presents as a deliberate trade-off. The lighter implementation costs less memory and reduces the chance of function name collisions, but the README warns that some switches may not carry exactly the same meaning as their standalone counterparts.

Installing Blink and running a first remote command

The App Store is the shortest path. The README links to the App Store listing and says Blink is available there now. If you want to build it yourself, the README gives a sequence that clones the repository with submodules, fetches the frameworks and resources, and removes a stale workspace directory. Run it from a shell where xcode-select points at Xcode.app rather than the command line tools.

bash
git clone --recursive https://github.com/blinksh/blink.git && \
    cd blink && ./get_frameworks.sh && ./get_resources.sh && \
    rm -rf Blink.xcodeproj/project.xcworkspace/xcshareddata/

The README then tells you to copy the template configuration file and edit the copy, which is where your Apple developer id goes. If you do not want iCloud, push notifications or keychain sharing, the README says to turn those capabilities off in the project before doing anything else, then select your connected device under Product, Destination and build.

bash
cp template_setup.xcconfig developer_setup.xcconfig

Once Blink is running, curl is the transfer tool and it reuses the keys you created with the config command. The README shows passing an explicit key path and password when the default key is not the right one.

bash
curl scp://host.name.edu/filename -o filename --key $SHARED/id_rsa --pass MyPassword

Sandbox paths and the environment Blink sets

iOS will not let a process write to the home directory. The README states that only ~/Documents/, ~/Library/ and ~/tmp are writable, and that most Unix programs expect their configuration under $HOME. Blink works around this in MCPSession.m by defining a group of variables, including PYTHONHOME, SSH_HOME, CURL_HOME and SSL_CERT_FILE, all pointing into the writable locations. The README says that changing these permanently is best done by editing MCPSession.m. That is a real constraint rather than a preference: any tool you install that hardcodes a path under ~ will not find its configuration unless you either redefine HOME or set the specific variable yourself with setenv. The README also notes that the bundled commands live in a precompiled framework and points to the upstream ios_system repository if you want to add more commands by editing source.

No pipes, no bundled Mosh server, and other limits

The missing pipe is the most visible limitation, and it is documented rather than accidental. The second is on the server side: Mosh has to be installed on the remote machine, and the README sends you to mosh.org for that. If you cannot install software on the host, you are limited to SSH and lose the reconnect behaviour that Mosh provides. The third is that the repository does not hand you a binary. The README describes building through Xcode with a developer id, and points to BUILD.md for compiling the libraries yourself. Anyone expecting a downloadable artifact from the GitHub project will be disappointed.

How Blink differs from a desktop terminal emulator

iTerm2 and similar desktop terminals assume a stable network and a full POSIX shell, and they solve problems like window management, profiles and scripting on macOS. Blink takes the opposite position: it assumes the network will drop, so it builds on Mosh, and it assumes the local shell is a small curated set, so it ships a fixed list of commands inside ios_system.framework instead of a full userland. That means a desktop terminal gives you pipes and a complete toolchain, while Blink gives you session persistence across network changes and a terminal that fits an iPad screen with split view. The two are not substitutes. If your work is a long pipeline of local text processing, a desktop terminal is the right tool. If your work is staying attached to a remote session while you move between networks, the transport difference is the whole point.

Licence and maintenance

The repository is licensed GPL-3.0, with the licence text in the COPYING file and copyright holders listed in AUTHORS. That matters if you plan to distribute a modified build: the GPL-3.0 obligations attach to the code you redistribute, and the README's self-build instructions are aimed at running Blink on your own devices rather than at shipping a fork. The repository is not archived, and the last push was on 2026-06-29. The repository has no published releases, so there is no versioned changelog to plan against. Anyone building from source should expect to re-run the framework and resource scripts when they pull, and should treat the raw branch as the development line, since the README mentions invitations to test future versions on that branch. This is not legal advice; read COPYING before redistributing anything.

Editorial conclusion

Blink suits engineers who already run a Mosh server and want a real terminal on an iPad, and it suits anyone willing to build the Xcode project from source under GPL-3.0. It is the wrong tool if you need pipes in the local shell, if you cannot install Mosh on the remote host, or if you expect the repository to hand you a finished binary rather than a build recipe. Verify three things before committing: that mosh is installed on every server you plan to reach, that your Apple developer id is set in developer_setup.xcconfig if you build yourself, and that the commands you rely on are among those listed in the README, since there is no pipe operator.

Frequently asked questions

What is Blink Shell for iOS?

It is a terminal for iOS and iPadOS built on Mosh and SSH, written in Swift. The README describes it as a professional, desktop-grade terminal that keeps connections alive across unstable mobile networks.

How do I install Blink Shell?

The README links to the App Store listing, and also documents a self-build path that clones the repository with submodules and runs get_frameworks.sh and get_resources.sh before opening the project in Xcode.

Does Blink Shell support pipes in its local shell?

No. The README states that redirection with ">", "<" and "&>" is supported but that there is no pipe, so pipelines have to be rewritten as scripts or run on the remote host.

What commands are available inside Blink?

The README lists file operations such as cd, ls, cp, rm, mkdir and chmod, inspection tools such as cat, grep and wc, plus curl, scp, sftp and tar. They live in the precompiled ios_system.framework.

Do I need Mosh installed on my server to use Blink?

Yes, if you want the connection persistence the README describes. It says Mosh is readily available and points to mosh.org for installation on the server side.

Official sources

  1. blinksh/blink on GitHub
  2. Issues
  3. License: GPL-3.0
  4. Project website
  5. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/blinksh-blink.svg)](https://hysenlabs.com/projects/blinksh-blink)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/blinksh-blink.svg)](https://hysenlabs.com/projects/blinksh-blink)

Was this useful?