Initial problem
Agents that send mail, sign up for services, or run code need accounts and tools of their own. Sharing personal accounts or pasting credentials into prompts makes access hard to audit and revoke. The agent should also keep its inbox and history when a team switches clients.
Implementation
Teams create agents in a dashboard, assign inboxes, credentials, and machines, then connect a client through MCP or REST. Each token grants specific permissions and can be revoked. A paired local connector uses stored credentials only for approved destinations and actions. The service records usage and limits additional spending to a prepaid balance.
Outcome
My contribution
Impact
What mattered
Agent email with conversations, attachments, search, and shared mailbox state
Encrypted credential vaults with destination grants and a paired local connector
Linux machines for running commands, working with files, and browser workflows
Scoped MCP and REST access for Codex, Claude Code, Cursor, and other clients
Organization ownership, audit history, quotas, and prepaid usage controls
Insights
The landing page shows an agent with its own inbox, vault, and machine
Technical frame
The technical frame sits at the end on purpose: it shows the engineering substance behind the solution.
Next project
Know what your coding agents cost.
View project