Agentic engineering shifts the developer role from manual coding to orchestrating AI agents that automate the full software lifecycle from ticket to deployment. Using Claude Code with MCP servers and git worktrees allows a single person to manage the output and quality of an entire engineering organization.

Links

Notes and resources at ocdevel.com/mlg/mla-24
Try a walking desk - stay healthy & sharp while you learn & code
Generate a podcast - use my voice to listen to any AI generated content you want

The Shift: Agentic Engineering

Andrej Karpathy transitioned from "vibe coding" in February 2025 to "agentic engineering" in February 2026. This shift represents moving from casual AI use to using agents as the primary production coding interface. The goal is to automate the software engineering lifecycle, allowing a single person to manage system design and outcomes while agents handle implementation.

Tooling and Context Efficiency

Minimize MCP servers to preserve context. 12 active servers consume 66,000 tokens, which is one-third of Claude's 200K window. Lazy-loading MCP definitions reduces usage by up to 95%.

GitHub MCP: Accesses GitHub API for PR creation, issue management, and Actions.
Context7: Fetches version-specific documentation to prevent hallucinations in libraries like React or Prisma.
Sequential Thinking: Forces structured reasoning for complex architecture decisions.
Playwright: Performs browser automation for E2E testing and UI debugging.
Memory: Local knowledge-graph for persistent project context across sessions.
Hooks: PostToolUse auto-formats code via Prettier. PreToolUse blocks dangerous commands like rm -rf or writes to .env. SessionStart with a compact matcher re-injects instructions after context compaction.

High-Impact Workflows

Plan-First Mode: Use Shift-Tab for read-only exploration. Create TODOs and milestones before implementation to reduce backtracking.
Git Worktrees: Claude Code supports parallel sessions via the --worktree flag. This allows 3 to 5 simultaneous agents to work on different branches in a single repository.
Headless Mode: Use the --print flag and JSON formatting to script Claude into external automation or CI/CD pipelines.

The Automated Engineering Pipeline

Trigger: Issues are filed or labels like claude-autofix are applied. Tools like n8n or OpenClaw can also trigger sessions via webhooks or Slack.
Implementation: Claude plans, implements changes, and writes tests in an isolated worktree.
Self-Review: The code-review plugin runs four parallel agents to score changes for correctness and security.
CI and Auto-Fix: Claude monitors CI status, auto-fixes failures, and merges PRs to staging via squash once checks pass.
Human Gate: The engineer reviews the accumulated changes in the staging branch before merging to main for production deployment.

Career Transition

The role of the engineer moves from writing code to acting as an engineering operator. Daily work involves triaging issues, making architectural judgment calls, and optimizing the automation system. Maintaining a CLAUDE.md file under 100 lines ensures maximum token efficiency and performance for the agentic team.