Sign in everywhere with Aion ID
- One SSO account. The same user in the Hub, in the Discovery report, in the knowledge base, and in the /app shell.
- The header button goes to the Aionflow sign-in page. This marketing site does not store passwords.
Developers
The agent moves through the page
The agent moves through the page
you already have open.
You sign in once, with Aion ID. The agent sits on the tab. Below: the step log, MCP, and action packs.
The agent in the browser
- The agent works on the page already open in the window. You enter an address and load the page first, then you start it.
- page-agent reads the page as an accessibility tree: reference, role, name. Then it clicks and fills fields.
- When the page asks a human (captcha, slider), the agent stops. You take over the browser window and resume.
A log of the steps
- As it moves through the page you see the steps: start, pause, finish, and how many steps ran.
- Passwords do not enter that trace. Secrets are stripped before they are written to the log.
Programming and automation
Only what is in the Surf code.
page-agent
- Page tools: snapshot, click, fill. The shape is an accessibility tree.
MCP tools
- The public list: profile.open, profile.close, proxy.check, sync.start, vault.totp.
- Results do not include secrets. vault.totp returns a one-time code for a profile and an origin, not the TOTP secret.
- The tool server sits with the client.
Action packs
- A recorded flow can be invoked as a pack for the agent.
- Extension packs are a short allowlist switched on per profile.
Parallel browse
- In the agent drawer you paste many addresses or queries, one per line, and start a fan-out.
- The window chrome shows a counter, pause, and cancel.
A vault shared with the agent
- The agent reads and writes passwords for the active profile (vault.get, vault.save) and can ask for a TOTP code.
- The vault list shows the username and the origin. The password in clear text is neither on the list nor in the trace.