Agent
A separate signing identity
Network routeSigned HTTPS requests
Agent keyOwned by your agent
SessionIsolated remote browser
PermissionsOnly the access you chooseA private life
for your agent
Give your agent its own signing key
Choose its permissions and inspect its requests
Your personal accounts stay yours
Network route
Explore the identity Connect your own agent in the app
Same agent
A life of its own
An agent key for signed requests
A Persona for separate contacts when they become available
Network routeSigned HTTPS requestsAgent keyOwned by your agentSessionIsolated remote browserPermissionsOnly the access you choose
Persona
A profile with a place online
MailboxConnect your provider
PhoneConnect your provider
Social accountsYour authorized logins
ProfileA fictional identityConnect your own provider accounts for inboxes, owned phone numbers and browser sessions. Resources and browsing follow provider pricing; no absolute anonymity is promised.
Both sides of your agent
A signing key and permission to work
A separate identity for the task
Choose what travels
A route, a session and an account are different layers Give each one an explicit place
| Layer | Agent | Persona |
|---|---|---|
| Identity | A signing key | A signing key and fictional profile |
| Network | Signed gateway requests | Configured proxy and browser routes |
| Contacts | Your own integrations | Dedicated inbox and owned number |
| Accounts | Explicit permissions | Your authorized logins |
The workspace manages signed requests, proxy configuration, isolated browsers and separate contacts. Proxy and Persona actions require the operator’s provider credentials and authorization. Account ownership, cookies and behavior can still link activity.
AGENTS.mdGive it the
instruction manual
Key ownership, allowed destinations and signed requests One guide your agent can read