AI agents
An agent that can actually see what broke.
Not a chat window bolted onto a dashboard. Temps ships a real AI agent sandbox, an AI chat that reads your own traces and metrics, and an AI gateway — all wired into the same telemetry every other feature already collects.
Bring your own provider keys
Ask questions about a checkout latency spike and get answers pulled from your own traces, metrics, and revenue data — not a generic assistant guessing from a prompt.
It reads your telemetry, not a generic prompt
The AI chat pulls from the same traces, metrics, and error data every other Temps feature already collects — ask about a specific spike and get an answer grounded in what actually happened.
A real sandbox, not a container ID
Agent sandboxes run on a Docker/Firecracker backend with an in-browser command runner and password-protected preview URLs — a workspace you can actually open and watch, not a black box.
One gateway, any provider
The AI gateway sits behind a single OpenAI-compatible endpoint. Bring your own provider keys and swap models without rewriting integration code.
Usage tracked per project
Token and request usage is visible per project from day one — no separate dashboard to check.
Scoped deployment tokens for CI and agents
Agents and CI pipelines authenticate with role-scoped API keys, so automated deploys get exactly the access they need and nothing more.
Hand an error straight to an agent
When something breaks, the same error tracking and tracing data that surfaces the problem can hand it directly to a sandboxed agent already reading your codebase.
Bring your own provider keys
Give your agents something real to work with.
Install Temps, deploy a project, and the sandbox, gateway, and telemetry are already there — no separate service to wire up.
Try it yourself — quickstart guide