The Anthropic Certified Architect, Foundations is the first official Claude technical certification. It is also brand new and still in an early-adopter phase, which makes it hard to value. The free Anthropic Academy courses are the part worth doing today. The credential is a bet on a job market that does not exist yet.
The Anthropic partner program, the Claude Partner Network, launched in 2026. The surprise is how open it is: membership is free and any organization bringing Claude to market can join. That means joining is not the achievement. It is a box of enablement tools, and it gives you a multiplier, not leads. Here is what it actually is.
Claude Code ships with five built-in agent types: Explore, Plan, general-purpose, statusline-setup, and claude-code-guide. Most people know two of them. The other three run constantly and shape how much your sessions cost. This is the full catalog, what each one is for, and why knowing them changes how you read your own terminal.
A large context window in Claude Code feels free, and it is the opposite. Every token you load is re-billed on every turn after. The prompt cache that should make that cheap expires in five minutes, turning a tenth-price read into a higher-price write. And accuracy fades as the window fills. Here is the real cost.
Claude Code effort mode looks like a cost dial: turn it down to spend fewer tokens. The official docs say otherwise. Effort is a behavioral signal, not a strict budget, so low effort does not reliably cut spend and can quietly raise it. Here are the five levels, where they stop, and how to set effort with intent.
The general-purpose agent in Claude Code is not the main agent and not something you pick. It is a built-in subagent Claude routes to on its own for complex, multi-step work. It inherits your model and, in current Claude Code, spawns as a fork of your conversation. This post explains how it actually works and what that costs you.
Claude Code scheduled jobs come in three forms with very different guarantees: the in-session /loop, Desktop tasks, and Cloud routines. A missed run does not queue up a backlog. And despite a common belief, none of them creates a Windows Task Scheduler entry or a .bat file. Here is how each one actually behaves.
A Claude Code stop hook runs the moment Claude finishes a turn and can refuse to let it stop. It is the one hook that inverts control: Claude must pass your check before the turn ends. This post covers what a stop hook is, why exit code 2 is the whole game, the infinite-loop trap to avoid, and the patterns worth wiring up.
A surprising Claude Code bill is almost never one big expense. It is four different cost shapes stacked up: a context window that bills every turn, subagents that each cost a fixed chunk, skills that cost almost nothing until used, and caching that can cut the recurring cost or not. Budgeting tokens means knowing the four shapes.
When a Claude Code subagent fails, you cannot open it and look inside. It ran in its own isolated context and handed back a summary. Debugging a subagent is the skill of reading that summary, recognizing context-isolation failures, and designing subagents that report enough to be diagnosed. Here is how to do it.
A subagent in Claude Code is a specialized worker that runs in its own fresh, isolated context window, with its own tools and permissions, and reports back only a summary. It is how Claude does a noisy side task without flooding your main conversation. Here is what a subagent is, what file defines it, and when it earns its cost.
Making AI emails sound like you is not a prompting trick. A tone guide produces press-release sludge. The fix is a voice corpus built from your own sent folder, a style file you version like code, and a draft-only rule. Harper Reed trained Claude on roughly 200 sent emails and the gap closed.