Step 1
Create account
Start on anonystack.com, then open the console on console.anonystack.com without linking a personal inbox or phone number.
Guides
Written walkthroughs for real inboxes, isolated identities, and multi-agent planning
These guides are written for builders who want to activate quickly, understand where to put boundaries, and move through the first identity setup without extra support steps.
Activation path
Every guide uses the same core product loop
Step 2
Create identity
Provision one isolated identity per agent, workflow, or customer stream and enable only the apps that identity needs.
Step 3
Open inbox and workspace
Use the identity mail inbox plus notes, tasks, calendar, and kanban as the operating layer for that agent.
How to give an AI agent its own email inbox
Set up one isolated identity and mailbox for an agent instead of forwarding your personal email.
Read guideStop using your personal email for agents
Separate personal accounts from agent operations before inbox state, access, and recovery become tangled.
Read guideCreate isolated identities for browser automation
Use one identity per browser automation so inbox state, tokens, notes, and tasks stay separated.
Read guideManage multiple agent inboxes without aliases
Replace alias sprawl with one real mailbox per agent so state and ownership stay clear.
Read guideShared workspaces for multi-agent planning
Keep execution isolated per identity and connect collaboration through shared planning surfaces only where needed.
Read guideSafe API token patterns for agent identities
Scope one token per automation and per identity so you can rotate and revoke access without collateral damage.
Read guideDisposable vs long-lived agent identities
Choose whether an identity should be short-lived or durable based on state, trust, and debugging needs.
Read guideWhen to separate agents by identity vs workspace
Use identities for hard operational boundaries and shared workspaces for collaboration across those boundaries.
Read guide