Remote agent control
Step away without turning a live session into a black box.
Long-running coding tasks create an attention problem: the agent may finish, fail, or wait for input after you leave the workstation. Drover keeps that state visible on iPhone.
The workflow
- 1
Start work in Herdr
Your normal host, repository, terminal, and agent tooling remain unchanged.
- 2
Walk away
Drover Host maintains the authenticated bridge without moving the session to a hosted workspace.
- 3
Read live state on iPhone
See the verified host, Herdr session, workspace, pane, agent, and connected state—not a detached notification summary.
- 4
Respond only when authoritative
Send supported prompts or input over the live channel. If the connection is gone, the UI becomes read-only.
Why the boundary matters
A generic remote terminal can expose everything while explaining very little. A generic chat client can hide whether a response reaches the intended process. Drover’s object hierarchy and verified hostname keep the action tied to the actual Herdr session.
Good fit
- Long test, build, refactor, migration, or review runs that often pause for attention.
- Developers who already orchestrate agents through Herdr.
- Workspaces that must remain on a personally controlled macOS or Linux host.
- Situations where truthful disconnected behavior matters more than optimistic automation.
Need the system view? Read Drover documentation or the security model.
Take the next agent run with you.
Join beta updates for installation access and product progress.