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.
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.
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%.
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.Shift-Tab for read-only exploration. Create TODOs and milestones before implementation to reduce backtracking.--worktree flag. This allows 3 to 5 simultaneous agents to work on different branches in a single repository.--print flag and JSON formatting to script Claude into external automation or CI/CD pipelines.claude-autofix are applied. Tools like n8n or OpenClaw can also trigger sessions via webhooks or Slack.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.