Founding beta

Help test Skerry

The beta focuses on reconnect reliability, tmux and terminal-agent workflows, keyboard behavior, safe uploads, and clear SSH trust decisions.

Who this beta is for

You are a strong fit if you have one or more of these workflows:

• tmux-based work on an SSH server you control or are authorized to use;
• Claude Code, Codex, OpenCode, or another terminal TUI;
• an iPad hardware keyboard;
• Tailscale SSH or a homelab you can test safely; or
• an iPhone touch-first workflow with enough history to exercise scrolling.

Join

1. Apply for the Founding Beta.
2. If selected, accept the email invitation from Apple TestFlight.
3. Install the current Skerry build on the device you listed.
4. Read the current “What to Test” notes in TestFlight before starting.

Do not send hostnames, IP addresses, usernames, fingerprints, terminal output, customer information, uploaded files, or credentials with your application.

Twenty-minute core test

1. Add a host and compare its displayed host-key fingerprint with a trusted source before accepting it.
2. Connect, type a few safe commands, create another app tab, and switch between tabs.
3. Attach to tmux and rapidly switch windows and panes using Skerry's native controls.
4. In a coding agent or TUI, confirm touch scrolling moves history instead of cycling prompts or selecting text.
5. With the software keyboard open, rotate portrait → landscape → portrait. Confirm the terminal refills the available space and the action bar remains visible.
6. Lock the device briefly, return, and confirm the session repaints and reconnects without creating an unexpected tmux client.
7. Upload a small disposable file. Confirm the destination and that the name is inserted only after verification.
8. If relevant, test a hardware keyboard, on-device dictation, search, selection, and local attention notifications.

Send useful feedback

TestFlight feedback is preferred. Include:

• Skerry version and build;
• device model and iOS/iPadOS version;
• software or hardware keyboard and orientation;
• Wi-Fi, cellular, VPN, or Tailscale;
• plain shell, tmux, Claude Code, Codex, OpenCode, or other TUI;
• steps, expected result, actual result, and whether it repeats after reconnecting.

Screenshots and recordings are optional. Crop or redact terminal content, commands, paths, hostnames, and customer data. Never send passwords, private keys, recovery codes, or full host-key material.

Leaving the beta

Stop testing in TestFlight and delete Skerry. Remove temporary server accounts and keys. Remove Skerry-managed credentials inside the app before deletion when possible because Keychain items can survive app deletion.