How-tos, step by step.

Control your AI coding agents Pro

Termoire can notify you when a background coding agent needs you, and let you approve or deny its permission prompts from your phone, watch, or lock screen. This works by installing a tiny hook on each host — here's what it does, how to set it up, and how to remove it completely.

What gets installed

When you enable background notifications for a host, Termoire writes a small directory and patches your agent CLI's own config so it forwards its hook events to Termoire's push relay. Nothing else on the host is touched, and every change Termoire makes is tagged with a # termoire-notify marker so it's easy to find and remove.

Files written to the host:

~/.termoire/notify.sh    # forwards agent events (fire-and-forget)
~/.termoire/approve.sh   # long-polls for your approve/deny decision
~/.termoire/push.pub     # your device's public key (encrypted delivery)

Set it up

1. 1 In Termoire, open the host and go to Agents & notifications → Background notifications.
2. 2 Pick the agent CLIs you use on that host from the install checklist and tap Install. Termoire connects over SSH and writes the files above.
3. 3 Grant notification permission on your device if you haven't already. That's it — the next time an agent needs you, you'll get a notification you can act on.
4. 4 For Codex, confirm the one-time /hooks trust prompt in the CLI on the host, as the install sheet notes.

Remove it from the app

The simplest way to uninstall is from Termoire: open the host's Agents & notifications screen and turn off background notifications (or use Remove hooks). Termoire walks every CLI it knows about and cleans up every file and config entry it created.

Remove it by hand

If you'd rather do it on the host yourself — or you no longer have the app — remove the directory and then strip the marked entries from each CLI's config. Everything Termoire added carries the trailing # termoire-notify comment.

1. Delete the Termoire directory (removes notify.sh, approve.sh, and push.pub):

rm -rf ~/.termoire

2. Remove the hook entries from each agent CLI you installed, by editing its config and deleting the entries whose command contains # termoire-notify:

1. 1 Claude Code — edit ~/.claude/settings.json; under hooks, delete the entries whose command contains # termoire-notify.
2. 2 Codex — edit ~/.codex/hooks.json; remove the marked entries. If you enabled [features] hooks = true only for Termoire, revert it in ~/.codex/config.toml.
3. 3 Gemini CLI — edit ~/.gemini/settings.json; remove the marked hooks.
4. 4 OpenCode — delete the plugin file ~/.config/opencode/plugin/termoire.ts.
5. 5 Qwen Code — edit ~/.qwen/settings.json; remove the marked hooks.
6. 6 Kimi CLI — edit its TOML config; remove the marked entries.
7. 7 Factory Droid, Cursor, Grok, Copilot, Goose, pi, Oh My Pi, Crush, and Amp — remove the # termoire-notify-marked entry from each tool's hooks/plugin config, or delete the Termoire plugin file it added.

Eternal Terminal (ET)

Eternal Terminal is a third connection option alongside SSH and Mosh. It bootstraps over SSH, then keeps your session alive across socket drops and IP changes by re-attaching the same session and replaying exactly the gap — no byte lost.

On the host

ET needs the Eternal Terminal server and its helper on the machine you connect to. Install them from your package manager or from eternalterminal.dev:

# Debian/Ubuntu
sudo apt install et

# Fedora/RHEL
sudo dnf install et

# macOS
brew install MisterTea/et/et

Make sure etserver is running (or reachable via systemd) and that its port — 2022 by default — is open to you.

In Termoire

1. 1 Add or edit a host and set Connection to Eternal Terminal (or Auto, which prefers a resilient transport and falls back to SSH).
2. 2 If your etserver uses a non-default port, set it in the host editor.
3. 3 Connect. A live ET tab shows an ET badge; if etserver isn't reachable, Termoire quietly falls back to plain SSH.

Import hosts from Tailscale

If your machines are on a tailnet, you can add any of them in one tap instead of typing addresses by hand.

1. 1 Create a Tailscale API access token in the Tailscale admin console.
2. 2 In Termoire, tap + → Import from Tailscale and paste the token.
3. 3 Pick the machines to add. Termoire prefills each one's MagicDNS name, port, and display name — it never guesses a credential.
4. 4 Hosts on your tailnet show a TAILNET badge, and a one-tap hint offers the short MagicDNS name while editing.

QR pairing

Move a host between two Termoire devices with a single scan — no credentials ever travel in the code.

1. 1 On the device that has the host, open its context menu and choose Share as QR. The code carries the name, address, port, user, and an auth-kind hint — never passwords, keys, or identities.
2. 2 On the other device, tap + → Scan a QR code and point it at the code. Termoire prefills the host editor for you to review.
3. 3 You can also scan a plain ssh://user@host:port URI. Nothing is saved or connected until you confirm.

SFTP file browser & uploads Pro

Browse, upload, and download files on any SSH host without leaving Termoire.

1. 1 From a session's toolbar, open the Files (SFTP) browser to navigate the host, then upload, download, make, rename, or delete.
2. 2 Paste an image (⌘V or the ribbon paste key) or drop a file onto the terminal to upload it to ~/.termoire/uploads/ and drop the remote path at your prompt — handy for handing a screenshot to a coding agent.
3. 3 Transfers show progress and can be cancelled; a failed upload never leaves a truncated file behind.

Port forwarding Pro

Forward TCP ports over your connection — reach a database, a dev server, or an internal service as if it were local.

Add a forward

1. 1 In the host editor, open Port Forwarding and add a rule: choose Local (-L) or Remote (-R), then set the bind host/port and the target host/port. Optionally auto-start it on connect.
2. 2 Connect. A live per-session panel shows each forward's status, the actual bound port (including ephemeral binds), and its active connection count, with a live toggle and a copy-address action.
3. 3 For a local forward, point your browser or client at the bound local address.

Ask the live prompt on Support, or email [email protected].