Logged-in pages
Give an agent access to pages behind a login.
The useful web is signed in. Your invoices, your dashboards, your suppliers' price lists, your own SaaS tools - none of it answers an anonymous fetch. Unfenced lets an agent work those pages without ever handling your password.
The rule that shapes everything else
A stored secret never enters the model. You add a login once, in the dashboard, into an encrypted vault. The agent can see that a credential exists and which site it is for - it never sees the value. When a page needs it, the agent asks for the credential by name and the engine types it into the field the way a person would.
There is no route that reveals a stored secret, and adding one is not a feature request we intend to accept. The one deliberate exception is a single-use 2FA code you hand over in the moment: it is shape-checked so a password cannot be passed off as one, kept out of the session replay, and logged as a kind rather than a value.
Signing in once, and staying signed in
Some sites take a password. Others only take "Continue with Google", which is not something that can be typed at all. Both are handled the same way from your side: you sign in once, and the session is kept encrypted so the next run - tomorrow, or next month - starts already signed in rather than at a login wall.
You can keep more than one account for the same provider. The agent asks which one to use, or remembers your answer for that site if you would rather it did not ask again.
What the agent may actually do
Reading is broad; acting is not. An agent can only click, type and submit on sites you have put on an allowlist, and it cannot add a site to that list itself - it can ask, which raises a request you approve with one tap, but the grant is yours to give. On an allowed site, a step that submits is then refused until the agent re-sends it deliberately - a guard against a slip rather than a second approval from you.
A refusal comes back as policy rather than as an error, so a well-built agent stops and tells you instead of retrying a wall two hundred times.
What you can see afterwards
Every session is recorded as a screencast of the real page, because we are driving somebody else's site and a DOM recording would not survive it. You can watch what the agent did, which is the only honest answer to "what happened at 3am" - and every action leaves a signed, hash-chained receipt you can verify offline.
Let an agent work your signed-in web
Access is by invitation while we are in private preview. Tell us which sites you would start with.