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

Gather — 14 May 2026

Governance Layer Matures #

  • VibeX 2026 — 1st International Workshop on Vibe Coding and Vibe Researching (EASE 2026) — First dedicated academic workshop on vibe coding, co-located with the Empirical Software Engineering & Measurement conference. Topics: empirical studies of AI-assisted development practices, productivity measurement, software quality under vibe coding, and the human-AI collaboration loop. Signal: vibe coding has moved from blog-post discourse into empirical research territory.
  • Introducing the Agent Governance Toolkit: Open-source runtime security for AI agents (Microsoft Open Source) — Microsoft releases an open-source runtime security framework for AI coding agents. Intercepts agent actions in real time, applies policy rules, and produces an immutable audit trail. Positions governance not as a policy document but as a technical layer agents must pass through. Practical for multi-agent pipelines where individual agent behaviour needs to be auditable.
  • 6 Multi-Agent Orchestration Patterns for Production (Beam.ai) — Production-validated taxonomy: orchestrator-worker (known task decomposition), sequential pipeline (fixed linear steps), fan-out/fan-in (independent parallel work), multi-agent debate (quality verification), dynamic handoff (unpredictable routing), adaptive planning (open-ended problems). Model tiering is now standard: cheap/fast model (Haiku 4.5) for triage/routing agents, capable model (Sonnet 4.6) for reasoning agents.

Context Engineering as Practice #

  • Effective context engineering for AI agents (Anthropic Engineering) — Anthropic’s own framing: context engineering = curating what the model sees before inference. “Just in time” context: agents maintain lightweight identifiers (file paths, stored queries, web links) and load data into context at runtime via tools rather than pre-loading everything. 57% of enterprises run agents in production; quality remains the top barrier, and the problem is context governance, not code generation.
  • AGENTS.md Complete Guide for Engineering Teams (BuildBetter) — AGENTS.md has emerged as the de facto universal agent instruction format: read natively by Claude Code, Codex CLI, Cursor, Aider, Devin, GitHub Copilot, Gemini CLI, Windsurf, and Amazon Q. The cross-tool standardisation means a single AGENTS.md file functions across the IDE landscape without modification.
  • 2026 Agentic Coding Trends Report (Anthropic) — Anthropic’s quantified view: coding agent session duration grew from 4 min average to 23 min; 78% of sessions now involve multi-file edits; 57% of orgs run agents in production. The session-duration jump suggests agents are no longer being used for one-shot code generation but for sustained, multi-step workflows.

Karpathy — Second Brain Shift #

  • Andrej Karpathy Stopped Using AI to Write Code (Neural Notions, Medium) — Karpathy describes a working system beyond code generation: dumps raw research materials into a folder, points an LLM at it, and the LLM builds and maintains an interlinked wiki from scratch — writing articles, creating backlinks between related ideas, categorising concepts. Frame: the most interesting use of LLMs is knowledge synthesis, not code authorship. Note: Medium source but reporting on a direct Karpathy description.
  • Claude-Specific Expertise Anthropic’s own context engineering post directly operationalises what agentic engineering means in their toolchain — it’s the Claude Code runtime design document in public form.
  • Applications of Vibe Coding AGENTS.md cross-tool standardisation matters for enterprise: a single governance artefact now works across tool choices, removing one obstacle to setting company-wide AI coding policy.
  • Claude-Specific Expertise Code w/ Claude 2026 Outcomes feature is a direct implementation of multi-agent debate pattern — a grader agent evaluates the task agent’s output without seeing its reasoning.

Meta-observations #

  • Emerging pattern: Governance is now a technical discipline, not just a policy one. Microsoft’s toolkit, Anthropic’s context engineering post, and the OWASP Agentic Top 10 all treat governance as runtime infrastructure. Next gather: look for vendor certification or compliance attestation products in this space.
  • Keyword suggestion: "AGENTS.md" engineering teams — the cross-tool standardisation story is early and under-covered.