Hello agent, meet localstack. LocalStack GmbH launched a dedicated entry point that lets your AI agent discover, install, and start using LocalStack without you having to explain anything. Here's what's in it and why LocalStack GmbH built it. AI and agents can accelerate your development workflows, but they also require an added layer of validation to ensure that what you are deploying to production does what you expect. This is especially true when relying on cloud services where a simple mistake by an agent could become costly. LocalStack already fits naturally into an agentic workflow and helps you test and verify your generated code without worrying about breaking the environment or incurring cloud costs. If you're using Claude, Cursor, or any agent-enabled tool to write and test AWS applications, LocalStack is the obvious local target. Developers have been wiring this up manually for a while now, and with the addition of its MCP server and skills, agents can go beyond just generating commands. They can actually operate LocalStack - starting it, deploying infrastructure, analyzing logs, generating IAM policies, etc. The problem wasn't agent capability. It was discoverability. A dedicated entry point for AI agents. This discoverability problem is why I created a dedicated entry point for AI agents at blog.localstack.cloud/ai. The page has two modes, switchable with a tab. The human view is what you're reading this post to understand - an explanation of what the page does, a copyable prompt to hand to your agent, and a reference to the skills and MCP tools available. The agent view renders the raw content your agent will actually read. To use it, copy this prompt and give it to your agent: That's it. Your agent takes it from there. What the agent sees. The /ai/agents.md file at the other end of that URL is a plain-text Markdown document written specifically for agents, not humans. It goes straight to a step-by-step setup flow, with enough context for an agent to work through it without asking clarifying questions. The flow opens with a Docker check, then walks through five steps: * Install lstk - LocalStack's new CLI that handles the Docker image, authentication, and container lifecycle in one tool (brew install localstack/tap/lstk or via npm). * Create an account - LocalStack requires an account; the agent pauses here and asks the user to sign up, then waits for confirmation. * Authenticate - lstk login opens a browser for auth, and the agent waits for the user to finish. * Start LocalStack - lstk start pulls the image and launches the container. * Configure the MCP server - the agent asks the user for their auth token, which is required to enable the MCP server, then writes the config to the right place for whichever client they're using. For automated or headless runs, the doc also describes an alternative path that requests a short-lived token and starts LocalStack without a browser login. MCP tools and skills. Once setup is complete, the agent has access to the full LocalStack toolchain. Through the MCP server, agents get access to: * localstack-management - start, stop, restart, and monitor container status. * localstack-deployer - deploy CDK, Terraform, and SAM stacks. * localstack-logs-analysis - analyze logs for errors and performance issues. * localstack-iam-policy-analyzer - generate least-privilege IAM policies from violations. * localstack-chaos-injector - inject faults to test system resilience. * localstack-cloud-pods - save and restore environment state snapshots. * localstack-state-management - manage local file-based state export/import workflows. * localstack-extensions - install, uninstall, list, and discover LocalStack Extensions. * localstack-ephemeral-instances - spin up temporary cloud-hosted LocalStack instances. * localstack-aws-client - run AWS CLI commands directly against LocalStack. * localstack-aws-replicator - replicate external AWS resources into a running LocalStack instance. * localstack-app-inspector - inspect application traces, spans, events, and IAM evaluations. * localstack-snowflake-client - execute Snowflake SQL queries and commands against LocalStack. * localstack-docs - search the LocalStack documentation. Through the skills at github.com/localstack/skills, agents get six structured workflows covering container lifecycle, infrastructure deployment (Terraform, CDK, CloudFormation, Pulumi), state management, log analysis, IAM policy analysis, and extensions. If you want a longer look at how skills work and why they matter, the WTH Are Agent Skills? post covers the pattern in depth. The agents.md document references both, explains what each tool does, and suggests a few things to try once LocalStack is running. Give it a try. If you're already working with AI agents day-to-day, give it a try. The simplest test is to open a new conversation and paste the prompt above. Watch what your agent does with it. The instructions are designed to be complete enough that the agent can run the whole setup flow. Head of Developer Relations at LocalStack Brian Rinaldi leads the Developer Relations team at LocalStack. Brian has over 25 years experience as a developer - mostly for the web - and over a decade in Developer Relations for companies like Adobe, Progress Software and LaunchDarkly. Get the latest tips, tutorials, and insights on local cloud development.

LocalStack has announced App Inspector, a new capability that helps software development teams debug cloud applications more efficiently. The tool simulates AWS-native production environments in a lightweight local container, enabling developers to identify issues without deploying to AWS. App Inspector provides visual representations of data flows between AWS services, event execution paths and resource dependencies within LocalStack's local sandbox. This eliminates the need to dig through logs and removes the latency of redeploying to cloud environments, offering near-instant validation. The tool addresses growing challenges as AI-generated code, which now comprises 30% to 50% of total code output, requires faster validation. Research shows up to 70% of major production incidents stem from misconfigurations. LocalStack, which has over 1,500 customers and hundreds of millions of Docker pulls, is backed by Notable Capital.

LocalStack simulates data flows across AWS cloud services to simplify debugging with App Inspector. Apr. 29, 2026, 12:00 PM ZURICH, April 29, 2026 (GLOBE NEWSWIRE) - LocalStack, the market leader in local cloud development, today announced App Inspector, a breakthrough capability in LocalStack for AWS that enables software development teams to identify issues in their cloud application environments faster and more easily than they can in traditional cloud-native development environments. LocalStack for AWS simulates AWS-native production application environments in a lightweight container that deploys on the customer's private infrastructure, making it possible for teams to validate code in safe, local environments without the security implications, complexity and costs of deploying to AWS. In traditional cloud-native development environments, developers face complex and time-consuming debugging processes that require waiting for infrastructure deployments and digging through logs for root-cause analysis. This lack of visibility creates delays and allows bugs to slip through unnoticed until they reach production. As more software teams rely on AI agents to build applications, the heightened volume and questionable quality of AI-generated code increases the impact of this bottleneck. "With 30% to 50% of code now being generated with the help of AI assistants, the pressure on development teams to validate AI-generated code quickly and reliably has never been greater, a challenge App Inspector is purpose-built to address," said Paul Nashawaty, Practice Lead and Principal Analyst, ECI Research and theCUBE Research. "We found that up to 70% of major production incidents stem from misconfigurations, yet most organizations still manage critical configuration through fragmented files and tribal knowledge, making the kind of early-stage visibility App Inspector provides essential to preventing costly production failures." By simulating the full application stack within a local sandbox container, LocalStack enables developers to understand application behavior more easily than they can when debugging against a public cloud environment. This includes insights such as data flows between AWS services, event execution paths and resource dependencies where misconfigurations often go unnoticed. App Inspector provides a visual representation of the interaction between services in the local emulation of the user's AWS application environment so developers can fix bugs without digging through logs. When redeploying a fix, the local container also eliminates the latency and provisioning delays of redeploying to cloud environments, providing near-instant validation. "The containerized nature of our sandbox environments introduces new possibilities for how software teams build, test and ship software to production," said Waldemar Hummer, LocalStack co-founder and CTO. "App Inspector leverages that advantage to provide developers the early-stage visibility needed to validate reliability in an efficient way. This is just the latest example of the unique capabilities of LocalStack that help software developers and agents ship reliable software faster than they can in the cloud." About LocalStack LocalStack's mission is to make cloud software development easier, faster and more impactful by unlocking the benefits of local infrastructure for cloud-based application environments. With more than 1,500 customers and hundreds of millions of Docker pulls, LocalStack has become the de facto standard for local cloud development worldwide. LocalStack is remote-first and backed by Notable Capital. For more information, please visit https://www.localstack.cloud/. Media and Analyst Contact: Amber Rowland [email protected] +1-650-814-4560 Markets Insider and Business Insider Editorial Teams were not involved in the creation of this post. Sponsored Financial Content