Coding agents do their best work on long tasks, and long tasks are the ones you don’t want to watch from your chair. The trouble is that agents stop. Claude Code asks for permission to run a command, finishes a turn and waits for the next message, or runs into an error. If you are away from your desk, the agent just sits there.
The AgentVera mobile app is now available for iOS and Android, and it is built for exactly that gap. It connects to the AgentVera desktop app on your computer and lets you run your agents from your phone: chat with them, approve requests, read the terminal, check the diff and start new ones. In this post I walk through what it does, how to set it up and how I use it day to day.
What the app gives you
The app is a full remote for the agents running on your computer. Here is the short version:
| From your phone | Where in the app |
|---|---|
| See every agent, grouped by project | Agents tab |
| Approve or deny a request | Approve and Deny on each request |
| Message an agent, with files, photos or voice | Chat tab on the agent |
| Watch the terminal and send keys | Terminal tab on the agent |
| See which files changed | Changes tab on the agent |
| Start a new agent in a project | New agent, with an optional Workspace |
| Send one message to several agents | Broadcast |
| Tasks, night shift, Git, Docker, SSH and more | More tab |
| Kanban boards | Boards tab |
It works with whatever coding agents your desktop has installed. Claude Code and Codex are the usual pair, and the other CLIs you run in AgentVera show up the same way.
The agents still run on your computer. The phone sends messages and actions and shows you the result, so the desktop app has to stay open and the computer awake.
How the connection works
You don’t open ports, set up a VPN or expose your machine. The desktop app keeps an outbound connection to the AgentVera server, and the phone reaches your computer through it. Conversations, terminal output and diffs pass through the server and are not stored there.
If the computer goes to sleep or loses its connection, the app tells you the computer is offline and shows the last known state. Nothing is lost; the agents pick up again when the computer is back.
Setting it up
Setup takes a couple of minutes:
- On the desktop app, sign in to your AgentVera account (Settings → Account). A free account is enough.
- Open Settings → Phone and turn on Control from your phone. It is off by default.
- Decide on the three extra toggles: Allow typing into the terminal, Git actions from the phone and Docker actions from the phone. Each one is off until you turn it on.
- Install AgentVera on your phone from the App Store or Google Play.
- Sign in with the same account: Google, Sign in with Apple on iOS, or email and password. If your account uses two-factor authentication, enter the code from your authenticator app or a backup code.
Your phone then appears under Connected phones on the desktop. Remove signs that phone out, and it can’t reach your computer again until it signs in.
The app has a dark theme and speaks English and Turkish. Under Settings → Language you can pick System, English or Türkçe.
The Agents tab
The Agents tab lists your agents grouped by project, the same way the desktop sidebar does, with a count of how many are working and how many are waiting. There is a search box and two segments: All and Pending. The tab carries a badge when approvals are waiting, so you can see at a glance whether anything needs you.
Starting an agent from the phone
From the Agents tab you can start a new agent. Pick the Computer, the Project and the Kind (Claude Code, Codex or another CLI your desktop has), then write the first message. Under the options you can set the Model, Effort, Account and an optional Role, such as “You are a senior reviewer; write the tests first.”
The Workspace option starts the agent in a new git worktree on its own branch, so it works without touching your main folder. If you are new to the idea, Git worktrees for parallel agents explains why it matters when several agents work on one repository.
Inside an agent: Chat, Terminal and Changes
Open an agent and you get three tabs.
Chat
Chat is where you talk to the agent. Each message shows whether it is queued, sending or not sent, and Show earlier turns loads older history. A message can be up to 20,000 characters.
You can attach files and photos, up to 10 per message and 50 MB each. A screenshot of a broken screen is often the fastest way to explain a bug from your phone. There is also voice dictation of up to 60 seconds; the recording is transcribed on your desktop and lands in the message box.
Terminal
Terminal shows the agent’s terminal. In Text mode the output rewraps to fit your phone’s width, and you can pinch to zoom. Screen mode shows it as the terminal draws it. Copy all output puts everything on your clipboard.
When Allow typing into the terminal is on, you can type and use the special keys: Esc, Tab, Ctrl-C, the arrows, Enter and Shift-Tab. When it is off, the terminal is view only. I keep it off on most machines and turn it on only when I know I will need to answer a CLI prompt by hand.
Changes
Changes lists the files the agent touched, each marked as new, deleted, renamed or modified, with the number of additions and deletions. It is enough to tell whether the agent stayed inside the files you expected before you say “carry on”.
Actions
From the agent’s actions you can Interrupt the current turn, Stop the agent, Resume it later and Switch account when one account is close to its limit. The conversation carries on under the new account. If limits are a regular problem for you, Claude Code usage limits covers how they work.
Approvals without the desk
When an agent asks for permission, the request shows up in the app with Approve and Deny. The Pending segment and the tab badge make sure you don’t miss one.
There is no always-allow button on the phone. Rules that approve things automatically stay a desktop decision, which I think is the right call: a quick tap on a small screen is not the moment to widen what an agent may do.
Broadcast and undo
Broadcast sends one message to several agents at once. Select the agents, write the message and tap Send to all. Busy agents queue it and take it when their turn ends. I use it for things like “stop and commit what you have” at the end of the day.
If an agent went the wrong way, Undo last turn puts back the files it changed in that turn. Turn points lets you go back to an earlier turn, and a point from before the undo is kept so you can return to it. Undo needs Git actions from the phone turned on on the desktop.
Notifications
Push notifications tell you when something needs you. Each one has its own toggle:
- When approval is needed
- When a turn finishes
- When something fails
- Task reminders
- When a limit passes 90%
Notifications contain no code and no message text. They tell you that something needs a look; the content stays in the app, behind your sign-in. You can also turn on a Face ID or biometric lock for the app.
The More tab
The More tab holds the rest of your desktop:
- Tasks: your tasks and reminders, with snooze.
- Night shift: queue work for the night. The night shift is part of the Pro plan.
- Automations: scheduled jobs and rules, with a way to run one now.
- History: past conversations, search, and resume one.
- Limits: usage for each of your accounts.
- Git: status, stage, commit, branches, push, pull and log. Anything that writes needs Git actions from the phone.
- Docker: containers, live logs, start, stop and restart. Changes need Docker actions from the phone.
- Reviews: the review inbox, findings and CI logs.
- Statistics: tokens, agent hours and models.
- Team: members and roles. Live team status needs the Team plan.
- SSH: hosts, keys, snippets, a terminal, SFTP and port forwards. Keys live in an end-to-end encrypted vault; the server only holds ciphertext.
- Settings: language, notifications, the biometric lock and deleting your account.
The Boards tab has your kanban boards, on the Pro and Team plans: cards with labels, due dates, checklists, comments and attachments, sharing, and sending a card straight to an agent.
App, Telegram or the browser view?
AgentVera gives you three ways to reach your agents from a phone. They overlap, and each has its place:
- The mobile app is the full remote: chat, terminal, diffs, new agents, approvals and the rest of your desktop.
- Telegram is good for quick replies. You get notifications, approve with a tap and start work with /new, /team and /night. Control Claude Code from your phone with Telegram covers the setup.
- The browser view at app.agentvera.dev/agents works when you can’t install anything. Review from your phone shows status, approvals and finished work with diffs in any browser.
I keep Telegram for the “agent finished” pings and open the app when I need to read or steer.
Common mistakes
- Letting the computer sleep. The agents run on your machine. If it sleeps, the app shows the last known state and nothing moves until it wakes.
- Turning on every desktop toggle on day one. Start with control only. Add terminal typing, Git or Docker actions when you actually need them.
- Approving blind. Before you tap Approve on a command you don’t recognize, check the Chat and Changes tabs to see what the agent is doing.
- Sending vague tasks. Typing on a phone pushes you toward short messages. Use voice dictation or attach a screenshot instead of writing “fix the login”.
- Forgetting lost phones. If you change or lose a phone, use Remove under Connected phones on the desktop.
- Expecting the phone to replace the desk. Reviewing a large refactor or resolving a merge conflict is still easier on a big screen. The app keeps agents moving until you get there.
Checklist
- Signed in to AgentVera in the desktop app
- Control from your phone turned on
- Terminal typing, Git and Docker actions set the way you want
- Mobile app installed and signed in with the same account
- Your phone listed under Connected phones
- Notifications picked, biometric lock on
- Computer set not to sleep while agents work
Wrapping up
A Claude Code mobile app is less about writing code on a small screen and more about not leaving agents waiting. With AgentVera on your phone you see what every agent is doing, answer approvals, read the terminal and the diff, and hand out the next task, whether it goes to Claude Code, Codex or another agent on your computer. The app is free and available for iOS and Android.
You can download AgentVera for your desktop, start for free and check the plans when you need the night shift or team features.