--- title: Why Every QA Wolf AI Agent Gets Its Own Computer | daily.dev description: QA Wolf rebuilt the infrastructure behind its AI testing agents, moving away from a stateless, cloud-job model toward giving every agent session its own... canonical: https://daily.dev/posts/why-every-qa-wolf-ai-agent-gets-its-own-computer-tbfrgh1qs twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Why Every QA Wolf AI Agent Gets Its Own Computer | daily.dev og:description: QA Wolf rebuilt the infrastructure behind its AI testing agents, moving away from a stateless, cloud-job model toward giving every agent session its own... og:url: https://daily.dev/posts/why-every-qa-wolf-ai-agent-gets-its-own-computer-tbfrgh1qs og:image: https://api.daily.dev/og/posts/tbfrGh1Qs.png og:image:alt: Why Every QA Wolf AI Agent Gets Its Own Computer og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Why Every QA Wolf AI Agent Gets Its Own Computer **[QA Wolf](https://daily.dev/sources/qawolf)** · 10 min read · 1 upvotes · 0 comments ## Summary QA Wolf rebuilt the infrastructure behind its AI testing agents, moving away from a stateless, cloud-job model toward giving every agent session its own persistent cloud machine with a real filesystem, shell, and browser. The shift addressed four problems specific to long-running, human-facing agent sessions rather than typical disposable jobs: cold starts (solved with a pre-booted machine pool), retries (replaced with single-attempt execution to avoid duplicate side effects like bug reports), statelessness (replaced with frequent autosave to persistent storage so work survives machine loss), and trusted code (replaced with least-privilege access, private secrets handling, no cloud credentials, and fail-closed behavior). The result lets agents split large tasks across up to 50 parallel sub-agents, each with its own isolated machine and branch, using the same public QA Wolf CLI available to customers. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why do AI agent sessions need a dedicated machine instead of being run as typical stateless cloud jobs? Agent sessions behave like a coworker rather than a job: they pause waiting on people, hold work in progress, and run commands nobody reviewed ahead of time. QA Wolf found that giving each agent session its own isolated cloud machine with a real filesystem, shell, git, and browser worked better than building pretend tools like a custom file reader or search tool to substitute for a real OS. _Teams designing AI agent infrastructure can track emerging architecture patterns like this on daily.dev._ ### How does QA Wolf prevent an AI agent from retrying and duplicating actions like filing the same bug report twice? Agents get exactly one attempt instead of the automatic retries used for normal jobs, because retrying could duplicate side effects such as posting the same bug report twice. If the machine dies mid-task, the partial result (like an already-filed bug report) stays, and the failure surfaces visibly instead of silently redoing completed work; this differs from QA Wolf's own test runner, which retries failing tests up to three times. _Developers building reliable agent workflows can follow approaches like this via daily.dev._ ### How does QA Wolf keep AI agent work from being lost when the underlying machine crashes or is recycled? Unsaved changes are saved to persistent storage separate from the machine after a few seconds of inactivity, and at least every 30 seconds while typing, so a new machine can pick up from the last saved state instead of starting over. If a change can't be merged cleanly, the latest saved code is kept rather than risking a bad merge, limiting worst-case loss to a few seconds of work. _Engineers architecting stateful agent sessions can keep up with patterns like autosave recovery on daily.dev._ ## Similar posts on daily.dev - [Agentic AI for Test Workflows. Why Our QA Team Built It and How Testing Changed as a Result](https://daily.dev/posts/agentic-ai-for-test-workflows-why-our-qa-team-built-it-and-how-testing-changed-as-a-result-umuc6vsde) · Security Boulevard · 0 upvotes · 0 comments - [Computer use: How AI agents can automate almost anything](https://daily.dev/posts/computer-use-how-ai-agents-can-automate-almost-anything-gb3cmk4lt) · Red Hat Developer · 0 upvotes · 0 comments --- Tags: [#security](https://daily.dev/tags/security), [#ai-agents](https://daily.dev/tags/ai-agents), [#testing](https://daily.dev/tags/testing), [#infrastructure](https://daily.dev/tags/infrastructure) [View this post on daily.dev](https://daily.dev/posts/why-every-qa-wolf-ai-agent-gets-its-own-computer-tbfrgh1qs) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Why Every QA Wolf AI Agent Gets Its Own Computer","url":"https://daily.dev/posts/why-every-qa-wolf-ai-agent-gets-its-own-computer-tbfrgh1qs","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/why-every-qa-wolf-ai-agent-gets-its-own-computer-tbfrgh1qs"},"datePublished":"2026-10-01T17:01:56.666Z","dateModified":"2026-10-01T17:14:45.133Z","description":"QA Wolf rebuilt the infrastructure behind its AI testing agents, moving away from a stateless, cloud-job model toward giving every agent session its own...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e57658582521f7df17df10e426d772b0?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e57658582521f7df17df10e426d772b0?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"QA Wolf","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"QA Wolf","logo":"https://media.daily.dev/image/upload/s--B9OvVIWd--/f_auto,q_auto/v1788684983/logos/qawolf?_a=BAMAMicg0","url":"https://daily.dev/sources/qawolf"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/why-every-qa-wolf-ai-agent-gets-its-own-computer-tbfrgh1qs","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"security,ai-agents,testing,infrastructure","timeRequired":"PT10M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"QA Wolf","item":"https://daily.dev/sources/qawolf"},{"@type":"ListItem","position":3,"name":"Why Every QA Wolf AI Agent Gets Its Own Computer"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/why-every-qa-wolf-ai-agent-gets-its-own-computer-tbfrgh1qs#faq","mainEntity":[{"@type":"Question","name":"Why do AI agent sessions need a dedicated machine instead of being run as typical stateless cloud jobs?","acceptedAnswer":{"@type":"Answer","text":"Agent sessions behave like a coworker rather than a job: they pause waiting on people, hold work in progress, and run commands nobody reviewed ahead of time. QA Wolf found that giving each agent session its own isolated cloud machine with a real filesystem, shell, git, and browser worked better than building pretend tools like a custom file reader or search tool to substitute for a real OS. Teams designing AI agent infrastructure can track emerging architecture patterns like this on daily.dev."}},{"@type":"Question","name":"How does QA Wolf prevent an AI agent from retrying and duplicating actions like filing the same bug report twice?","acceptedAnswer":{"@type":"Answer","text":"Agents get exactly one attempt instead of the automatic retries used for normal jobs, because retrying could duplicate side effects such as posting the same bug report twice. If the machine dies mid-task, the partial result (like an already-filed bug report) stays, and the failure surfaces visibly instead of silently redoing completed work; this differs from QA Wolf's own test runner, which retries failing tests up to three times. Developers building reliable agent workflows can follow approaches like this via daily.dev."}},{"@type":"Question","name":"How does QA Wolf keep AI agent work from being lost when the underlying machine crashes or is recycled?","acceptedAnswer":{"@type":"Answer","text":"Unsaved changes are saved to persistent storage separate from the machine after a few seconds of inactivity, and at least every 30 seconds while typing, so a new machine can pick up from the last saved state instead of starting over. If a change can't be merged cleanly, the latest saved code is kept rather than risking a bad merge, limiting worst-case loss to a few seconds of work. Engineers architecting stateful agent sessions can keep up with patterns like autosave recovery on daily.dev."}}]} ```