Temper documentation
Give every user's agent its own computer
A long-lived, isolated machine per end user, with credentials the agent can't steal, network access only where you allow it, approvals for risky actions and a tamper-evident audit log.
- Getting startedGet an API key, create an environment for a user, connect their Gmail and approve the first action.
- ConceptsEnvironments, data disks, credentials, approvals, egress, audit, browsers, usage and your team.
- GuidesBring your own OAuth app, handle approval webhooks, store your model API key.
- SecurityWhat Temper protects against, how, and what is still on you.
- API referenceEvery endpoint, generated from the OpenAPI spec: environments, exec, idle, schedules, agent, templates, browser, audit, secrets, team, usage, connections, approvals.