A research agent that reads for six hours, a coding loop that iterates until tests pass, a scraper that has to sleep between polite requests, none of that fits a function with a 15-second or 15-minute ceiling. On DenkOps the agent runs in a slot that has no request timeout at all: it stops when your code decides to stop, not when the platform decides.
If the process crashes mid-run, DenkOps attaches an ai_hint with the likely cause, file and line, useful when the agent itself, or you from Claude Code, needs to diagnose and redeploy without babysitting the terminal.
Yes. A DenkOps slot is a normal long-running process, not a function invoked per request, so an agent loop that calls the Claude API, waits, and calls again keeps going for as long as its own code runs, hours if needed, with no external timeout cutting it off.
On the durable disk mounted at /persist. It survives restarts, crashes and redeploys, so a checkpoint file, a task queue, or a key-value store written with the DenkOps SDK is still there if the process needs to resume.
← Deploy AI agents · FastAPI scheduled job guide · Bun+Hono scraper guide