What's your actual vibecoding workflow right now?

Reddit r/AI_Agents News

Summary

The post inquires about current workflows for vibecoding and AI engineering, inviting comparison of tools like Codex, Claude Code, and n8n to optimize the development process from idea to software.

I'm curious what everyone is actually using for vibecoding and AI engineering right now. Not just which model you think is best, but your full workflow from idea to working software. Are you using Codex, Claude Code, Cursor, Gemini, n8n, or a combination of tools? How do you handle planning, coding, testing, debugging, documentation, and keeping the AI from breaking something that already works? I've been building my own workflow around Codex and Claude Code, but the software changes so quickly that I want to compare notes with people who are actively shipping projects. What does your current setup look like, and which part of it saves you the most time?
Original Article

Similar Articles

I vibecoded something engineers are starring in github

Reddit r/AI_Agents

The author announces iai-mcp, a local memory tool for Claude Code that retains context across sessions, and reflects on the positive community feedback and rapid iteration following its GitHub release.

Vibe coding and agentic engineering are getting closer than I'd like

Simon Willison's Blog

Simon Willison reflects on how vibe coding and agentic engineering are converging in his own workflow, raising concerns about code review responsibilities as AI coding agents like Claude Code become increasingly reliable. He explores the ethical tension between trusting AI-generated code in production and maintaining software engineering standards.

How Do We Stop Vibe Coding?

Hacker News Top

The article discusses the rise of 'vibe coding' using AI agents, its risks to code quality and developer understanding, and calls for rethinking software engineering practices to move beyond merely generating code from intent.