Educational library
Agentic Coding in a Minute
Practical lessons for building software with coding agents. One concept per page. About a minute to useful understanding.
Learning paths
Follow a sequence
Start with a curated path, then branch into related lessons as you need them.
- Claude Code FundamentalsFrom first session through project instructions, permissions, planning, Git, testing, and MCP.
- Codex FundamentalsCodex-oriented setup: instructions, tasks, sandboxing, Git, verification, MCP, and automation habits.
- Git for Coding AgentsThe Git skills that matter when agents commit, branch, recover, and work in parallel.
- Agentic Engineering FundamentalsVendor-neutral loop: specify, plan, context, tools, execute, verify, retry, and approve.
Tracks
Browse by topic
Expandable tracks covering tools, techniques, and engineering practices for agentic development.
- Claude Code in a MinutePractical Claude Code usage from project instructions through advanced agent workflows.
- Codex in a MinuteCodex CLI and related agentic coding workflows, starting with project instructions and task setup.
- Git in a MinuteGit concepts that matter most when coding agents commit, branch, and work in parallel.
- MCP in a MinuteModel Context Protocol: servers, tools, permissions, and how coding agents use them.
- Context Engineering in a MinuteHow to feed agents the right context—and keep it from rotting mid-task.
- Agent Workflow in a MinuteVendor-neutral engineering patterns for planning, verification, and multi-agent work.
- Testing with Agents in a MinuteVerification gates, agent-written tests, and how to avoid fake green builds.
All lessons
Start anywhere
- Getting startedClaude Code is Anthropic’s agentic coding CLI: you give a task in a repo, it reads context, edits files, runs commands, and iterates with your approval boundaries.
- CLAUDE.mdCLAUDE.md is a project instruction file Claude Code reads so it follows your repo’s conventions without being reminded every session.
- PlanningAsk Claude Code for a short plan and file list before it edits, so you can reject bad approaches cheaply.
- PermissionsClaude Code permissions define which tools and actions the agent may take without asking—and which require human approval.
- Git workflowUse a branch-per-task Git workflow with Claude Code so agent commits stay reviewable and reversible.
- HooksClaude Code hooks are automation points around agent events—use them for checks and guardrails, not mystery side effects.
- Getting startedCodex is OpenAI’s coding agent surface for repository work—task in, inspected changes out, with project instructions guiding behavior.
- AGENTS.mdAGENTS.md is a repository instruction file for coding agents (including Codex) that records how to work in the project.
- Task specificationA good Codex task states outcome, constraints, and verification—so the agent can finish without inventing scope.
- SandboxingSandboxing limits what Codex can touch—filesystem, network, and privileges—so agent speed does not equal unrestricted access.
- AutomationAutomate Codex only after the human loop works: same task template, same gates, same review boundary.
- CommitsA commit snapshots a set of changes with a message—your unit of history for review and rollback.
- BranchesA branch is a movable pointer to a commit—your named line of history for a change.
- DiffsA diff shows what changed between snapshots—your primary review tool for agent output.
- RebaseRebase replays commits onto a new base—useful for updating a branch, dangerous on shared history.
- WorktreesGit worktrees let you check out multiple branches of the same repository into separate directories at once.
- Cherry-pickCherry-pick copies a commit onto your current branch—useful for rescuing a good agent fix from a messy branch.
- Parallel agent workspacesRun multiple coding agents safely by giving each a worktree, branch, and clear merge path.
- Bisectgit bisect binary-searches history to find which commit introduced a bug—vital when agent commits are frequent.
- RecoveryGit recovery tools—reflog, reset, revert—help undo agent mistakes without panicking.
- What MCP isMCP (Model Context Protocol) is a standard way for AI clients to connect to external tools and data through servers.
- Tools and resourcesIn MCP, tools are actions the model can invoke; resources are data the model can read.
- Local vs remote serversLocal MCP servers run near your machine; remote servers expose tools over the network—trust and latency differ.
- Permissions and securityMCP security is mostly about which servers you trust, which tools they expose, and what those tools can reach.
- Project instructionsProject instructions are durable repo-level guidance that coding agents load so they do not rediscover your process every session.
- Relevant file selectionRelevant file selection means loading only the files needed for the task—so the agent reasons over signal, not the whole repo.
- Context pollutionContext pollution is when irrelevant files, logs, or tool output crowd the model’s window and degrade the next decision.
- Task specificationA task specification defines outcome, scope, constraints, and verification for any coding agent—not just one vendor.
- Plan before executionHave the agent propose a short plan and file touch-list before it edits—so you can catch wrong approaches cheaply.
- Human approvalHuman approval boundaries are checkpoints where an agent must stop for a person before risky or irreversible actions.
- ExecutionExecution is the agent actually editing and running commands—bounded by the plan, permissions, and verification gate.
- Verification loopsA verification loop requires the agent to prove done with an external check—then fix—until the check passes or you stop it.
- RetriesRetries are bounded re-attempts after a failed verification—each attempt should use new evidence, not blind repetition.
- Parallel agentsParallel agents only help when tasks are partitioned, isolated on disk, and integrated through reviewable merges.
- Verification gatesA verification gate is a deterministic check that must pass before agent work is accepted.
- Test-first agent workflowsTest-first agent workflows make the agent write or confirm a failing check before implementing—so done means the check flipped green.
- Avoiding self-verificationDo not let an agent be the only judge of its own correctness—especially when it can edit the tests.