We gave two @AnthropicAI Claude Code sessions the same task. One had access to Signadot and the signadot-validate skill. The other didn’t.
The one without shipped a broken change. The one with the signadot-validate skill caught it and fixed it on its own. đź§µ
youtube.com/watch?v=St2ckbmk…
Cognition ( @cognition) now triggers more Devins asynchronously than interactively. As @ido_pesok puts it, async agents are only useful if developers can trust what they come back with. In a cloud-native system, that trust is a runtime problem.
New on @thenewstack, Signadot CEO @arjuniyer_ on why a green test run against mocks says nothing about cross-service behavior, why where the verification loop closes decides what a defect costs, and how to close that loop before the PR.
thenewstack.io/verifying-asy…
We gave two @AnthropicAI Claude Code sessions the same microservices task. Same model, same prompt. One declared success. The other found a break the first one shipped.
3/4
Session two used signadot-validate. Only the changed service ran locally, with traffic routed to real dependencies in the cluster. A lightweight ephemeral environment, spun up per change. Playwright caught the break end to end, pre-PR.
4/4
The agent fixed the front end, revalidated, and shipped a change verified across the full stack. Closed verification loop. That is what turns agent speed into mergeable output.
Read the writeup and watch the demo: signadot.com/blog/claude-cod…
New tutorial: closed-loop microservices validation with @AnthropicAI Claude Code and Signadot.
The agent proves a change against your real system before the PR, not after.
signadot.com/docs/tutorials/…
2/3
The signadot-validate skill runs the loop inside Claude Code: wire the change into a lightweight ephemeral environment, run it against real cluster dependencies, read the result, iterate.
3/3
The agent keeps going until the check passes.
What reaches the reviewer is a merge-ready change, validated against the real system before the PR opens.
3/4
It reads the sandbox spec, forked workload and pod status, recent Kubernetes events, routing health across your mesh, and the Signadot operator's own diagnostic logs scoped to that sandbox.
4/4
Your app traffic, secrets, and workload logs are never sent. It reasons about the environment, not your data.
Available now in beta. Check out the docs: signadot.com/docs/reference/…
Tutorial: How to test Temporal workers using Signadot's lightweight ephemeral environments in Kubernetes.
If you are building agentic backends, durable workflows, or multi-step orchestration on Temporal and Kubernetes, this one is for you.
signadot.com/blog/how-to-tes…
Coding agents validate at machine speed, but only against the surface they can reach. Environments are solved (lightweight ephemeral envs give the agent a real cluster on demand). Tests are the gap. Integration tests live in CI, out of reach during the loop, so agents fall back to unit tests and mocks. Bugs land downstream.
What closes the gap: a plan. One end-to-end check for one user-visible behavior. Real cluster, real assertions, no pipeline. Ships today as two agent skills, signadot-plan and signadot-validate. Native in Claude Code, Cursor, Codex.
Full piece from CTO Anirudh Ramanathan @foxish_ on how we are building this for @thenewstack: thenewstack.io/ci-for-coding…
Signadot Plans is now in beta.
Reusable validation workflows your coding agents author from natural language and run against a real Kubernetes environment, ready in seconds for any change.
Platform teams own the action catalog. The boundary of what runs against your cluster stays where you want it.
Developers and agents author plans on top of that catalog. Many small, focused plans that cover the system.
Sandboxes. Plans. Skills.
The comprehensive agent-native platform for building and validating microservices on Kubernetes.
Available for all Signadot users today: signadot.com/blog/signadot-p…