APX is a free, open-source desktop app that runs your own team of AI agents on your machine.
An agent can help with a website without turning your password into another message in a chat. The important question is not simply whether the agent can open a browser. It is who signs in, which session is used and what the agent is allowed to do afterward.
Start with a narrow task: “Open this site, let me sign in, then find the invoice. Do not send or change anything.” Check the address before entering credentials. If the site asks for a one-time code or CAPTCHA, complete it yourself rather than putting the code in the conversation or asking the agent to bypass the check.
In APX, a browser handoff lets the person take over the tab for a sensitive step and return it. That depends on the desktop browser being available: a headless server browser cannot be taken over in the same way. There are other options, including approved import of an existing login for a domain and site-scoped sign-in variables. The latter can fill an allowed field without showing the value to the agent. Neither is a reason to give every site access to a credential.
A successful login is not proof that the requested job was done. Check the account, inspect the result, and review the destination before approving a consequential action. When access is no longer needed, sign out at the site and review permissions. Removing a saved variable does not necessarily close an already open session.
The practical rule is simple: use a real handoff for the secret, then verify the outcome of the work.
Read the complete browser safety guide and APX browser documentation. Explore APX and its official video channel.
Top comments (1)
Handing 2FA back to the person is the right default. A log of which domains the agent touched during the session also makes the verify step much easier afterwards.