Local AWS emulators are one of those tools where the value is inversely proportional to how much you trust your staging environment. If your staging account perfectly mirrors prod, you don't need a local emulator. But nobody's staging perfectly mirrors prod, so you end up needing something like this for the fast feedback loop on IAM policies, Step Functions state machines, and anything involving SQS/SNS fanout where the iteration cycle against real AWS is measured in minutes per attempt. The question is always parity — how closely does the emulation match real AWS behavior at the edges? LocalStack has been chasing that for years and still hits gaps. Curious how Floci handles the services where AWS's own behavior is underdocumented.
One thing I notice across all these coding agents is that none of them have a trust or reputation layer. If an agent generates code, merges a PR, or deploys something — there is no cross-tool way to verify whether that agent has a track record of reliable output. We treat every agent invocation as equally trustworthy. In a world where agents are increasingly calling other agents' tools via MCP, that seems like a gap. The agent running your code review has no way to know if the agent that wrote the code has ever produced working code before.