For product teams
Give your product a "Do this for me" button.
Users hand over the task they came to do. A workflow autopilot your team created completes it right in front of them, in their own session. Anything sensitive, they approve or type themselves.
Tours point. Chatbots wait. Users want it done.
A workflow autopilot is a computer-use agent that lives inside your product. It never chats; it acts. The user clicks the offer, watches the task get done step by step, answers a short question when the autopilot is unsure, and personally approves anything consequential.
How it works
- Map. Point the CLI at your repo:
npm install -g @holostaff/cli. One scan draws your real customer journey: routes, workflows, the tasks worth taking over. - Rehearse. Synthetic users run your real flows in real browsers. Every run is recorded, graded, and watchable.
- Certify. An autopilot ships only while its workflow passes the suite. Suites gate every pull request.
- Deploy.
holostaff deployopens a pull request: SDK init, journey stage markers, the embed. Merging is going live. Reverting is rollback. - Verify. Every handover is logged, watchable, and counted only when the task actually completed.
The safety envelope
- Every target is highlighted on screen before anything happens.
- Pay, submit, delete, send, sign: the user presses Allow first. No answer means no.
- Password, payment, and code fields are never typed by the autopilot. It points, the user types.
- Any keystroke from the user pauses it. Stop never leaves the screen.
Pricing
Scan and map are free. Going live starts a 14-day trial. Then you pay for simulation runs while you build and completed handovers when an autopilot finishes a task for a real user. A handover that stops or fails costs nothing.