Support

Support is email: support@goatr.app. There is no account to sign in to, no ticket portal and no chat — a person reads the inbox.

goatr is a small independent project. Bug reports and questions are welcome, including the ones that turn out to be ours.

What to include

• What you were doing, and what you expected to happen.
• What happened instead — the exact wording of any error on screen.
• The server you were connecting to: its OS and whether it is x86_64 or aarch64.
• Whether the problem is about connecting at all, or about sessions and tabs not coming back after you return to the app.
• The diagnostics export, if the problem is about sessions, tabs or attaching (below). It records the app build, so you do not need to look the version up.

A screenshot is fine and often faster than describing a screen. If you think you have found a security problem, say so in the subject line.

The diagnostics file

The app can record what it does while it is resuming a session, and export that as a file you attach to your own email. Nothing is uploaded automatically — the file only leaves your device if you share it.

1. Open Settings and find the Diagnostics section.
2. Turn on Collect Resume Diagnostics. It is off by default, so turn it on before reproducing the problem.
3. Reproduce the problem.
4. Come back to Settings and tap Export Resume Diagnostics, then send the file to yourself and attach it to your email. There is also an Export Resume Digest option if you would rather send the shorter summary.

The export is a sanitized set of resume timing events, and it is built from an allowlist of fields. It does not include terminal output, keystrokes, hostnames, usernames, passwords, keys or authentication details. Read it before you send it if you want to be sure — it is a plain text file.

Before you report a connection problem

• Session persistence needs a supported host: x86_64 or aarch64 Linux, or macOS 13 and later, with a writable, executable home directory. On anything else — another architecture, another OS, or a home directory you cannot write to — goatr still connects, but it degrades to a plain SSH session with no session persistence. That is expected, not a bug.
• On macOS hosts the setup step also needs the codesign tool available to your shell.
• Do not approve an unexpected host key. If the fingerprint on screen is not the one you know for that server, tap Cancel, not Trust Key, and check the server's fingerprint out of band. Report it only once you are certain the server is the one you meant to reach.
• Nothing is installed on a server until you approve it. goatr asks per server before it writes its session components to ~/.goatr, and that approval is tied to the host, user and authentication method it was given for.

Where to look next

Privacy covers exactly what goatr collects (nothing) and what it writes on your server, and Terms covers what you can expect from the app and what it expects of you.