↓Skip to main content
Zeitgeist — a spike by Chris Gathercole
  1. Topics/
  2. Vibe Coding Approaches/

Gather — 21 August 2026

The Methodological Focus is Shifting From the Prompt to the “Harness” #

  • Vibe Coding vs Prompt-Driven: One Year Later, the Debate Is Already Outdated (Vertex AI Search Result) — Argues that the frontier of AI-assisted development has moved beyond prompt engineering to building a “harness” that allows agents to work safely. This harness consists of the tools and context surrounding the agent: Git for traceability, tests for feedback, linting for style, and explicit rules (e.g., in an AGENTS.md file) for constraints. The developer’s primary skill is shifting from prompt tuning to supervision and judgment: designing the harness, curating the context, and building observability for multi-agent systems.

  • What Is a Software Factory? The Agentic Operating Model, Defined (Augment Code) — Formalizes the “harness” concept into a defined operating model called a “software factory,” where AI agents write, test, and ship code within a pipeline where humans control the specification and merge-approval gates. This model is a direct response to the problem of agent-generated pull request volume overwhelming human review capacity, a trend quantified by Faros AI telemetry showing a 91% increase in PR review time for teams with high AI adoption. The article distinguishes this from simple CI/CD by noting that the coding step itself is now automated and must be managed as part of a system, citing OpenAI’s “Symphony” and Dropbox’s “Nova” as production examples.

  • How Do You Prompt AI to Build Your Projects? (There Are 7 Levels) (Medium) — Proposes a maturity model for AI development that progresses from unstructured “Level 1: Vibe Coding” to the more rigorous “Level 4: Spec-Driven Development.” At Level 4, the developer writes a formal specification document that lives in the repository alongside the code; when requirements change, the spec is edited first, and the code is then regenerated from the updated spec, creating a more structured and auditable workflow.

  • Because if you can’t test, then it’s vibe-broken (Level Up Coding) — Describes a specific prompting methodology for AI-driven testing that acts as a “harness” for the agent. The process involves first instructing the agent to understand the “spirit of the code” (its purpose), then guiding it to write tests for the “happy, sad, and angry paths” to ensure comprehensive coverage beyond simple success cases. This structured approach prevents the agent from simply altering tests or source code to pass without context.

Multi-Agent Orchestration Patterns Are Being Formalized #

  • Hybrid Multi-Agent Framework for Enterprise Web Application Generation (Preprints.org) — Introduces a hybrid system named “CodeCraft” that combines deterministic code generation with a multi-agent LLM pipeline to combat the inconsistency of pure “vibe coding” in large applications. The core principle is to use a Prisma schema and its Data Model Meta Format (DMMF) as a single source of truth for deterministic generators that create backend APIs, frontend manifests, and RBAC structures. A six-agent LangGraph pipeline is then used only for ambiguous tasks like clarifying requirements and validating the schema, constraining the probabilistic work.

  • The Multi-Agent Code Review Workflow For My Production Android Apps (daily.dev) — Details a specific, production-tested multi-agent pipeline for code review that emphasizes parallel, isolated execution. The workflow uses a “skip-checker” agent to triage changed files, then spawns three parallel agents (bug, convention, security) in separate contexts to prevent bias. An “issue validator” agent then grades the findings, and a “verify-audit” agent attaches proof (file, line number) before the issues are sent to a fixing agent. This pattern is designed to be faster and more reliable than a single, sequential review agent.

New Agent Architectures Emphasize Learning and Composability #

  • A Coding Agent That Actually Learns From Its Own Sessions (Medium) — Describes “Prime Agent,” an open-source agent designed for long-running tasks and learning over time. Its architecture is centered on two concepts: a “Recursive Language Model” (RLM) that treats context as programmable state, and a “Continual Harness” that allows the agent to make small, evidence-based updates to its own skills. The agent operates within a persistent IPython environment, meaning all actions—including file operations, tool use, and sub-agent orchestration—are managed through executable code, creating a unified and introspectable operating model.

  • Is Deepseek Harness Better Than Claude Code (The AI Brief) — Analyzes the architectural contribution of the new “DeepSeek Harness” framework, positioning it as an attempt to make the agent runtime itself a composable product. Unlike more opinionated (though still customizable) tools like Claude Code, DeepSeek Harness is designed around an event-driven architecture and distributable “profiles” that allow teams to package and share a known-good composition of models, tools, and configurations. This approach treats the orchestration layer as a form of systems engineering around the cost per accepted change.

A Key Originator Signals a Phase Shift #

  • OpenAI Cofounder Andrej Karpathy Explains Why He’s Never Felt More Behind as a Programmer (YouTube) — In a conversation at Sequoia Capital’s AI Ascent 2026, Andrej Karpathy, who helped popularize the term “vibe coding,” stated that he has “never felt more behind as a programmer.” He identified December 2025 as an inflection point where agentic coding tools began producing working code chunks that no longer required his correction, marking a significant shift in his own workflow and prompting his current focus on side projects to keep pace with the technology’s capabilities.

Meta-observations #

  • Emerging theme: The most significant trend is a clear shift in focus from the prompt (the “vibe”) to the harness — the structured environment of tests, formal specs, explicit rules, and verifiable pipelines that makes agent-generated code reliable and auditable.
  • Emerging pattern: Hybrid systems that combine deterministic, schema-driven code generators for predictable tasks with LLM-based agents for ambiguous requirements are emerging as a pattern to enforce consistency in large applications.
  • Emerging pattern: For review and analysis tasks, orchestrators are moving from single, sequential agents to spawning multiple, specialized sub-agents that run in parallel with isolated contexts to improve speed and reduce cognitive bias.
  • Source to watch: Augment Code is consistently publishing substantive, methodology-focused content that defines and formalizes emerging patterns in agentic software development.
  • Author to watch: Andrej Karpathy’s commentary continues to be a leading indicator of where the frontier of AI-assisted development is moving, even as he describes his own struggle to keep up.