Agentic Coding
Top tech stories today across software, hardware, AI, and product launches. Senior engineer audience — skip rumour churn and pre-announcement leaks. Lead with shipping-now stories and what changed for builders.
Karpathy's 90% automation loop, Claude Code's 40-prompt architecture revealed, hooks that ping you back
1 min read
Agentic engineering leap
Karpathy just drew a line between vibe coding and what comes next.
In a 30-minute talk, he frames agentic engineering as the evolution past prompting—the skill shift isn't writing code, it's designing the loop your agents run inside [Source: X]. He shares how he automates 90% of his coding routine by building workflows from scratch rather than babysitting individual completions. The mental model: you're the architect of the system, not the typist inside it.
If you're still prompting one task at a time, this talk is your wake-up call.
Claude Code prompt internals
Someone just open-sourced Claude Code's entire brain.
A new GitHub repo extracts all ~40 system prompts and 110+ total prompt strings from version 2.1.169—including subagent instructions for Plan and Explore modes, the CLAUDE.md creation assistant, and slash commands like /batch, /code-review, and /security-review [Source: GitHub]. You'll also find the coordinator mode instructions for delegating to worker agents, memory consolidation patterns, and the Workflow system for multi-subagent orchestration with concurrency control. This is the reference manual Anthropic never published.
Study how the official prompts handle context—then mirror the patterns in your own CLAUDE.md.
Hooks for parallel agents
Running multiple agents means you need a better notification system.
A new deep-dive covers Claude Code hooks that fire at startup, close, when the agent asks a question, or when it finishes a task [Source: TDS]. The practical use: configure a sound notification when any agent needs your review, so you can context-switch across parallel sessions without constantly polling. Pair this with checkpoint recaps in your CLAUDE.md—have the agent present remaining tasks as checkboxes—and returning to a thread after 30 minutes takes seconds instead of minutes.
Your multi-agent workflow just got a lot quieter.
Spend tokens for quality
Faster isn't always cheaper.
The same guide argues for Claude Code's extended thinking mode when you need implementations that actually stick [Source: TDS]. The logic: longer agent processing time often beats fast but error-prone outputs that require manual correction cycles. Combined with OpenClaw and cron jobs for unattended tasks like code reviews and bug triaging, you can spend tokens efficiently without hovering over every session.
Trade latency for correctness—your refactor queue will shrink.
Piebald-AI/claude-code-system-prompts - GitHub4 hours ago ... All parts of Claude Code's system prompt, 27 builtin tool descriptions, sub agent prompts (Plan/Explore/Task), utility prompts (CLAUDE.md, compact, ...github.com
Based on your search intents about advanced Claude Code prompting, agentic coding workflows, and Cursor AI pair programming, I found relevant information about Claude Code's system architecture and advanced techniques. This GitHub repository contains an up-to-date extraction of Claude Code's ~40 system prompts and 110+ total prompt strings as of version 2.1.169, maintained by the team behind Piebald. The repository includes detailed documentation of agent prompts for subagents like Explore and Plan modes, specialized creation assistants for CLAUDE.md generation, and advanced slash commands like /batch for parallelizable changes, /code-review with multiple effort modes, and /security-review for vulnerability analysis. The system also documents numerous utility agents including background job orchestration, conversation summarization, memory consolidation for persistent context, and autonomous operation guidelines. For workflow automation, the repository details coordinator mode instructions for delegating work to worker agents, various skill definitions for scheduling and recurring tasks, and tools like the Workflow system for deterministic multi-subagent orchestration including concurrency control and resume behavior. The content covers best practices for agent design patterns, tool surface optimization, context management strategies, and agentic coding patterns that directly support the kind of advanced development automation and "vibe coding" workflows you're interested in mastering.
Karpathy framing agentic engineering as the next step past vibe ...9 hours ago ... 90% of my coding routine is automated by AI agents.” In this 30-minute talk, Andrej Karpathy explains how to build an AI agent workflow from scratch. Worth ...x.com

Andrej Karpathy frames agentic engineering as the evolution beyond vibe coding, emphasizing that the critical skill shift is moving from writing code to designing the loop that agents operate within. In a 30-minute talk, Karpathy shares how he automates 90% of his coding routine using AI agents and provides guidance on building AI agent workflows from scratch, positioning agentic engineering as the next level of development practice.
4 New Techniques to Maximize Claude Code | Towards Data Science14 hours ago ... Active usage of Claude Code hooks; Ultracode maximizes the effort used by coding agents to perform more advanced work; Make your coding agent present the ...towardsdatascience.com

The article covers four advanced techniques for maximizing Claude Code and Codex that directly align with your interests. First, it recommends heavy usage of OpenClaw with cron jobs to run coding agents 24/7 for automated tasks like code reviews and bug triaging, allowing you to spend tokens efficiently without constant manual oversight. Second, it explains Claude Code hooks that trigger at specific events (startup, close, when asking questions, finishing tasks), enabling automation like sound notifications when the agent needs your review, helping you manage multiple parallel agents. Third, it discusses Claude Code Ultracode with extended thinking as a method to spend more tokens for higher-quality implementations, arguing that longer agent processing time often beats fast but error-prone outputs that require manual correction. Fourth, it suggests configuring your CLAUDE.md file to have agents present remaining tasks as checkboxes and provide recaps at the end of responses, making it easier to context-switch between multiple parallel coding agents and quickly understand what needs to be done when returning to a thread after 10-30 minutes.