Loading…

Offline · reconnecting

Your sessions, still running

Every terminal on every one of your machines, in one list. Close the tab, lose the train's signal, lock your phone — the work keeps going, and you come back to exactly where you were.

Sessions

/

Order

Your sessions keep running on their machines. Pick one to pick up where you left off, or start a new one.

Claude

No Claude sessions yet. Start one from Jump to (“Claude in…”) or New session.

Reconnecting…

New session

Machine Name Folder

Start with Shell Claude Code Command

Workspace

Name

Home folder on each machine

New sessions you start in this workspace open in its home folder. Empty means your home (~).

Session

Text size 12

Fit to this screen Key bar

Key size Medium

Workspace keys1–9 switch, Shift+1–9 sends the pane, J flips, E arranges, W closes. Always Ctrl+Alt (Alt alone belongs to the terminal): arrows move, F full, Enter adds a shell Keep panes arrangedPanes even out by themselves when one opens or closes Notify me when it needs me

Close ? Whatever is running in it stops.

Reply

Compose

Press Enter after

New snippet

On all your devices

Name Command

Press Enter after

Share view-only

Anyone with the link can watch this session live, including the last 500 lines and any other window in it. They cannot type, resize it or see your other sessions, and it is encrypted end to end like your own connection.

1 hour 1 day Until I stop

Open a port

A private link to a web app listening on this machine, for you only, for 12 hours. Unlike your sessions it is not encrypted end to end: the relay passes the pages along.

Nothing of yours is listening on this machine. Start your dev server, then look again.

Download a file

Path

↑↓moveEntergoEscclose

Saved layouts

A layout keeps your workspaces, their splits and the sessions in them. Restoring one brings it all back and starts any session that is no longer running, in its folder (Claude carries on its last conversation).

Snapshots

Each one is kept on the machine it came from.

Switch session

Term

Order of sessions

Yours Name Recent

Compact listSmaller rows, previews only when a session needs you Typing aheadIn a shell on a slow line, show your typing at once, faintly underlined until the machine confirms it. Programs that draw their own input, like Claude Code, are left alone

Approved browsers

Off by default: signing in to your Hoq account is enough. Turn it on for a machine and it also asks for a browser it has approved, so even someone who took over id.hoq.app could not open a session there.

Notifications

On this device

When Claude Code needs youIt asks for permission or finishes its turn

When a long command finishes20 seconds or more; editors, pagers and logins never count

Always If it fails Never

To tell a failure from a success, run hoq-term shell on on that machine.

When a session ends Allow and Deny on notificationsWhere this device shows notification buttons (computers, Android; not iPhone) Hide what is on screenNotifications say only what happened and where. Their text travels through id.hoq.app and Apple or Google, unlike your sessions, which are encrypted end to end Quiet hoursNothing between these times

From to

Let permission requests throughClaude Code is stuck until you answer

Add a machine

On the computer you want to add, run:

curl -fsSL https://term.hoq.app/install.sh | sh

Add ?

It installs hoq-termd for your user; this page then asks you to approve the computer, and it appears here. The line works once, for 15 minutes. It works behind home routers: nothing on that computer listens to the internet. Linux or macOS, with Node 18+ and tmux 3.2+ (on a Mac: brew install node tmux).

Advanced: a machine on the tailnet, by address

Name Address

Put this in ~/.config/hoq-term/config.json on that machine, then restart hoq-termd. It is shown once.