Product guide
How Drover fits around your agents.
Drover is a remote control plane for work that remains inside Herdr on your own machine. This guide explains the model without hiding its current beta boundaries.
The system model
- Drover for iPhone
- The native iOS 18+ interface for viewing state and sending supported input.
- Drover Host
droverd, a standalone macOS/Linux process beside Herdr. Drover has no macOS or iPadOS app, and neither is planned.- Herdr
- The authoritative orchestrator and terminal-session source. Drover does not create a parallel hosted workspace.
- Cloud control plane
- Minimal signaling, short-lived relay credentials, generic push hints, and entitlement checks. Terminal payloads remain end-to-end encrypted.
Objects you navigate
Drover mirrors Herdr’s hierarchy instead of flattening every process into an invented chat thread:
Host→Herdr session→Workspace→Tab / pane→Agent
The verified hostname is always visible where host identity matters. A user nickname may accompany it, but never replace it.
Connection order
- LAN direct: local discovery and an encrypted direct session.
- WAN direct: peer-to-peer WebRTC when the network permits it.
- Managed TURN fallback: an encrypted blind relay when a direct path cannot be established.
Capability status
| Capability | Status | Boundary |
|---|---|---|
| Session and agent state | Beta scope | Mirrors the authoritative host. |
| Prompt / terminal input | Beta scope | Connected sessions only. |
| Off-network + push | Pro | Entitlement-gated at launch. |
| Approve / deny exact requests | Planned | Never inferred from ambiguous terminal text. |
| Interrupt / stop / manage agent | Planned | Not represented as available until end-to-end verified. |
Where to go next
Keep your agents within reach.
Join beta updates for installation access and product progress.