|
|
|
|
|
|
by StarPA
14 days ago
|
|
|
Congrats on the launch bro. I use computer-use agents daily as an end user (browser automation, even wireless ADB to install builds on my phone), so genuine question: how does your API handle the diffrence between reversible and ireversible actions ? Clicking around a page is one thing, but submitting a form, sending a message or confirming a payment is another — is there a mechanism for the agent to pause and hand back to the human before those, or is that left entirely to the caller? Asking cause in my exp that boundary is where trust in these agents is won or lost. |
|
|
We support explicit human approval gates in workflows, so you can have the agent prepare everything, then pause before steps like submitting a form, sending a message, or confirming a payment. The workflow moves to `awaiting_human`, and the caller approves or rejects it before execution continues.
Autonomous runs can also pause and hand over the live machine when the agent encounters something requiring human input. For teams that want stricter control, our lower-level API exposes each predicted action so the caller can inspect or approve actions before executing them.
Today, the irreversible boundary is primarily defined by the developer rather than us trying to universally infer what is consequential. We think explicit policy is safer because “irreversible” varies a lot by application.