Test Coding Agent Pull Requests with Argo CD and Signadot A Signadot tutorial demonstrates wiring Argo CD and Signadot sandboxes so that every pull request opened by a coding agent gets its own preview environment, with the agent reading test results back through the read-only Argo CD MCP server. An ApplicationSet turns each labeled pull request into an Application whose hooks create a sandbox for the changed service, run the PR's Playwright suite, and delete the sandbox on close, while Argo CD Notifications reports an `argocd/preview` commit status. The agent is blocked from kubectl, argocd and signadot access and can only push fixes based on preview results. Read this tutorial on Signadot docs https://www.signadot.com/docs/tutorials/argocd-coding-agent-pull-requests?utm source=devto&utm medium=referral&utm campaign=argocd-tutorial . Coding agents open pull requests faster than anyone can test them by hand. If you already run Argo CD, it can give each of those pull requests a preview of its own, and the Argo CD preview environments https://www.signadot.com/articles/argocd-preview-environments?utm source=devto&utm medium=referral&utm campaign=argocd-tutorial article explains why a Signadot sandbox https://www.signadot.com/docs/concepts/sandbox?utm source=devto&utm medium=referral&utm campaign=argocd-tutorial beats a full copy of the app for that. This tutorial builds the whole loop. A coding agent changes HotROD https://github.com/signadot/hotrod , a demo ride-sharing app, and opens a pull request. An Argo CD ApplicationSet turns the pull request into an Application whose hooks create a sandbox for the changed route service, run the pull request's Playwright suite against it, and delete the sandbox when the pull request closes. Argo CD Notifications reports the result as an argocd/preview check. When the check fails, the agent reads why through the read-only Argo CD MCP server https://github.com/argoproj-labs/mcp-for-argocd , pushes a fix and waits for the next result. Time: about 40 minutes. Example files: signadot/examples/argocd-tutorial https://github.com/signadot/examples/tree/main/argocd-tutorial Tip: What the agent can and can't do The agent pushes commits and reads Argo CD. It needs no kubeconfig and no Signadot API key, and the repository's Claude Code settings block kubectl , argocd and signadot . It can't sync or change anything in Argo CD, and its Argo CD account sees only preview Applications. The preview is its only way to test end to end. Each piece does one job: | Piece | Job | |---|---| | GitHub Actions | Builds ghcr.io/