Amazon traced a December disruption to engineers using its Kiro AI coding tool, but says the problem 'stemmed from a misconfigured role,' and was not a case of AI going rogue.

Amazon Web Services experienced a 13-hour interruption to one system used by its customers in mid-December after engineers allowed its Kiro AI coding tool to make certain changes, according to four people familiar with the matter.

AI coding tools have enabled a flood of bad code that threatens to overwhelm many projects. Building new features is easier but maintaining them is just as hard.

Because AI coding tools are trained on vast libraries of public code, they can generate snippets governed by restrictive open-source licenses. That raises important compliance questions, especially with licenses like GPL or AGPL, which could, in theory, require companies to open-source any software built on top of that output.

Two minor AWS outages have reportedly occurred as a result of actions by Amazon’s AI tools.

A new study finds vibe coding improves when humans give the instructions, but declines when AI does, with the best hybrid setup keeping humans foremost, with AI as an arbiter or judge. New research from the United States,

OpenCode creator Dax Raad argued it isn't necessarily a good thing that AI is lowering the cost of production for companies.

Anni Chen says vibe coding is hard to resist. It speeds up her productivity, but she doesn't trust it blindly.