← Field Notes

The Best AI Coding Setup Isn't the Most Autonomous One (Here's Why)

This video explores the five levels of AI coding autonomy, from manual coding with AI as a reference tool to fully autonomous "dark factories" that ship code without human intervention. It emphasizes that the most reliab

5 min read

The Best AI Coding Setup Isn't the Most Autonomous One (Here's Why)

Source: The Best AI Coding Setup Isn't the Most Autonomous One (Here's Why) — Cole Medin (https://www.youtube.com/watch?v=muwRbfuKbR4) · published 2026-07-03
Speaker(s): Cole Medin (not stated)
Relevant to: Agentic OS, Bexar Labs, BexarByte, Trove, Cross-business

TL;DR

This video explores the five levels of AI coding autonomy, from manual coding with AI as a reference tool to fully autonomous "dark factories" that ship code without human intervention. It emphasizes that the most reliable and productive setup is level three, where AI writes most of the code but is guided by structured planning and validation. This approach balances autonomy with control, making it ideal for AI-native development workflows.

Key ideas

  • [00:00] AI coding assistance is used in many different ways, and understanding your current level is key to improving your workflow.
  • [01:27] Level one: "Spicy auto complete" — AI is used as a reference tool, not for writing code.
  • [02:12] Level two: "Coding intern" — AI writes boilerplate code, but not complex logic.
  • [02:41] Level three: "Junior developer" — AI writes most of the code, but humans are still involved in planning and validation.
  • [03:50] Level four: "Engineering team" — AI handles larger tasks autonomously, but humans are still in the loop for high-level direction.
  • [05:46] Level five: "Dark factory" — AI writes and ships code without human intervention, but it's risky and requires a highly reliable system.
  • [09:17] Sonar and Gitarr are tools that help validate and fix AI-generated code, improving reliability.
  • [11:31] A system for AI coding includes rules, sub-agents, and skills that guide the AI agent to understand your codebase and workflows.
  • [13:17] The R Piv Loop (research, planning, implementation, validation) is a structured process for using AI coding agents effectively.
  • [16:35] Level four and five require a mature system with multiple agents handling different stages of the development pipeline.
  • [17:51] A dark factory requires a planning agent, code generation agent, validation layer, deployment system, and orchestration layer.

Tools, services & specific callouts

Tool / service What it is How it's used in the video Use-case for my ventures
Gitarr AI code review and auto-fix tool Used to automatically review and fix pull requests, including vulnerabilities like SQL injection Bexar Labs, BexarByte, Trove — improves code quality and reduces bugs in AI-generated code
Sonar AI coding platform Integrates Gitarr for code review and validation Bexar Labs, BexarByte, Trove — enhances AI coding workflows with validation and reliability
Arkon Open-source harness builder Used to build workflows for a dark factory experiment Agentic OS — enables building complex agent workflows for automation
Dynamis Agentic Coding Course Educational resource Provides structured approach to building AI coding systems Bexar Labs, Agentic OS — helps developers build reliable AI coding workflows

How AI / automation is used

AI is used as a coding assistant across five levels of autonomy, from reference tool to fully autonomous code generation. The speaker advocates for level three, where AI writes most of the code but is guided by structured planning and validation. This involves:

  • Planning agents that break down tasks into structured plans.
  • Code generation agents that implement the plan.
  • Validation agents that review and test the output.
  • Orchestration agents that manage the workflow between different stages.

The speaker uses a R Piv Loop (Research, Planning, Implementation, Validation) to ensure reliability and control over AI-generated code.

SEO / GEO / marketing / growth

  • Focus on AI coding autonomy and reliability as key selling points for AI-native workflows.
  • Use case studies of companies like StrongDM to demonstrate real-world applications of dark factories.
  • Position Sonar and Gitarr as essential tools for validating AI-generated code, especially in high-stakes industries like banking.
  • Use educational content (e.g., courses, YouTube videos) to build trust and demonstrate expertise in AI coding systems.

Infrastructure & hardware

None in this video.

Notable quotes

"The dark factory is the dream, but yes, it takes a lot of engineering effort." — [19:39]
"You have to be very careful when you get to this level of autonomy." — [07:24]
"The only reason that we delegate all the coding to the agent is because we're sandwiching the implementation with a lot of planning and a lot of validation." — [04:50]
"We're starting to get to the point where the dark factory is becoming realistic." — [07:55]
"If there's one thing you have described wrong in the spec, that could lead to dozens of shipped deployments that are just botching what you wanted to create." — [07:30]

Actionable takeaways

  • Bexar Labs: Implement a structured AI coding workflow using the R Piv Loop to ensure reliability and control over AI-generated code.
  • Agentic OS: Build a system with planning agents, code generation agents, and validation agents to guide AI coding workflows.
  • BexarByte: Use tools like Gitarr and Sonar to validate and fix AI-generated code, especially in high-stakes environments.
  • Trove: Integrate AI coding agents into workflows with structured planning and validation to improve efficiency and reduce errors.
  • Cross-business: Position AI coding systems as a scalable solution for development teams, emphasizing reliability and control over autonomy.

Open questions / to verify

  • What is the exact version of Gitarr or Sonar used in the video?
  • What are the specific failure modes of dark factories mentioned in the referenced article?
  • How many companies have successfully implemented dark factories, and what are their specific use cases?

Filing metadata

  • Suggested title: "The Five Levels of AI Coding Autonomy and Why Level Three is the Sweet Spot"
  • Primary venture: Agentic OS
  • Secondary ventures: Bexar Labs, BexarByte, Trove, Cross-business
  • Type: Strategy
  • Keyword tags: AI coding, agentic systems, dark factory, code validation, AI autonomy, R Piv Loop, Gitarr, Sonar
  • One-line index hook: This article explores the five levels of AI coding autonomy, emphasizing that level three — where AI writes most of the code but is guided by structured planning and validation — is the most reliable and productive setup for AI-native development.

AI-assisted summary of a YouTube video — source. Generated by a local model and human-reviewed; verify specifics against the original before relying on them.