Coding agents stop to ask for permission, finish a task or hit an error, and nobody is watching. With 1B Terminal and a few minutes of setup, those moments reach your Android phone as notifications you can answer.
Settings checked against each tool's official documentation on 4 November 2026.
1B Terminal·My server
The session needs your attention
ReplyEntery
$ claude
Why you miss your agent's questions
An agent that is waiting for you does nothing. 1B Terminal makes sure you find out.
It stops and waits
Claude Code, Codex, OpenCode and other agents pause before running a command or editing a file. If you aren't looking at the screen, the work stops until you come back.
Your phone hears it
1B Terminal turns the terminal bell and the agent's notifications (OSC 9 and OSC 777) into Android notifications for every session you aren't looking at. Also inside tmux: from version 1.2.0 the app turns on allow-passthrough in its own tmux session by itself.
Answer from the notification
Each alert has Reply, Enter and y buttons. Type or dictate an answer, confirm with Enter or say yes without opening the app.
Even if the agent doesn't notify
If a program never sends an alert, 1B Terminal can notify you when its output goes quiet after a burst of work: it has probably finished or is waiting for you.
Set it up in 1B Terminal
Five steps on your phone. The names in bold are exactly what you see in the app (version 1.2.0).
1
Install 1B Terminal
Get it from Google Play on your Android phone (Android 8.0 or later). There's no account to create.
On Hosts, tap + to open New host, enter the address, the user name and a key or password, and save. Connect once and check the server's fingerprint.
3
Turn on tmux for the host
In the host editor, under Session, turn on Attach to tmux on connect. Your agent keeps running on the server if the connection drops, and 1B Terminal lets its alerts through tmux. tmux has to be installed on the server.
4
Prepare the server for your agent
Open Settings › AI agents › Set up the server for agents (it's also in the ⋮ menu of a session). It shows the settings from the next section, ready to copy. The app never changes files on your server: you add them yourself.
5
Allow notifications
On Android 13 and later, allow notifications when the app asks. In Settings › Notifications, keep Notify when a session needs you on, turn on Notify when output goes quiet if you like, and keep Reply from the notification on to get the buttons.
Now start your agent and switch to another app or lock the phone. When the agent needs you, the notification arrives; tap it to go back to that session.
What to change in each agent
Only settings that appear in each tool's official documentation, with a link so you can check them yourself.
Claude Code
By default, Claude Code sends nothing to terminals it doesn't recognise; its documentation says “Other terminals: nothing”. Tell it to ring the terminal bell in any terminal, and 1B Terminal turns that bell into a notification.
File: ~/.claude/settings.json
{
"preferredNotifChannel": "terminal_bell"
}
You can also open /config in Claude Code, go to Local notifications and choose the terminal bell.
If you start tmux yourself
With Attach to tmux on connect, 1B Terminal already lets alerts through in its own session. If you start tmux yourself instead, add these lines from Claude Code's documentation and reload them with tmux source-file ~/.tmux.conf.
File: ~/.tmux.conf
set -g allow-passthrough on
set -g focus-events on
set -s extended-keys on
set -as terminal-features 'xterm*:extkeys'
Session status: Claude Code v2.1.295 and later report whether each session is working or waiting for you (OSC 7501), and 1B Terminal shows it on the session's tab. It only works when Claude Code runs outside tmux.
With “always”, Codex alerts you even while the terminal has focus. 1B Terminal never alerts you about the session you're looking at, so you won't get duplicates.
OpenCode's documentation doesn't say where that file lives; it does say you can point to one with the OPENCODE_TUI_CONFIG variable. OpenCode only alerts when the terminal isn't focused, and 1B Terminal tells it when you leave the session.
Google retired Gemini CLI for individual accounts on 18 June 2026. It still works with business licences and with an API key. If you use it that way, turn on Notify when output goes quiet so 1B Terminal alerts you when it stops.
Google's Antigravity CLI runs as agy. Its documentation doesn't describe a notification setting, so let 1B Terminal alert you when the output goes quiet.
In Settings › Notifications, turn on Notify when output goes quiet. When a session has been busy and then stops printing, 1B Terminal notifies you: the program has probably finished or is waiting for an answer.
Questions and answers
Do I need tmux?
No. Alerts also work in a plain SSH session, which the app keeps connected in the background. tmux is recommended because your agent keeps working on the server if the connection drops, and 1B Terminal goes back to the same session when it reconnects.
Does it work on iPhone?
No. 1B Terminal is only available for Android (8.0 or later).
Is anything sent to 1Byte Systems?
No. The connection goes straight from your phone to your server over SSH, and the notifications are created on the phone. There's no 1Byte server in between and no account.
Why don't I get alerts from the session I'm looking at?
On purpose: 1B Terminal only alerts you about sessions you aren't looking at, and at most once every 5 seconds per session.
Can I answer without opening the app?
Yes, with the Reply, Enter and y buttons on the notification. They're hidden while the app lock is on.
Get 1B Terminal
The SSH terminal for working with AI agents from your Android phone: keys, tmux, a key row made for agents and alerts that reach you.
