Fantastic Vibes and Where To Find Them
summary
Empirical report on using coding agents: teams defining agent teams with a Docker Agents YAML topology and sharing them as OCI images on Docker Hub see reproducible results, sandboxes with sandbox network and file restrictions prevent data leaks, and session tooling (Slagent/Slot, CCsession, Argus) reveals cost, files touched and replayable context. Concrete outcomes include a case of 100K+ lines removed safely and examples of wasted days; rules that work are narrow scopes, validation gates, and mandatory human review before merge.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:24Coding agent outputs
- 3:07Custom agent teams with Docker
- 6:37Sandboxes for secure execution
- 11:33Collaborative coding via Slack
- 14:19Tracking coding sessions
- 16:44Managing agents like developers
- 18:29Tracking intent in code
- 22:42Coding agents change workflows
- 25:30Future trends and questions
related talks
25mBeyond the IDE: Toward Multi-Agent Orchestration
50mPanel: Beyond The Vibe: Code Quality First
40mHow To Tame Your Agents?
27mAgentic Coding with Discipline & Skill: Practical Techniques and Tips
24mAI Governance for developers: A practical framework for deploying autonomous coding agents safely…
08mHow to Improve your Vibe Coding
11mBuilding Secure Backend Services with AI Agents
22mBuilding Secure Services with AI Agents: Patterns From Real-World Engineering