- 01
agentcore
aws bedrock agentcore in the browser — no account required
8 lessons ~109m bedrock-agentcore 0.2.2 (typescript) - 02
agentic patterns
skills, extensions, personas, handoffs — the building blocks of multi-turn agent systems.
7 lessons ~90m - 03
claude agent sdk
build your own coding agent in typescript. tool use, sub-agents, hooks, permissions.
8 lessons ~100m @anthropic-ai/claude-agent-sdk 0.2.119 (typescript)
the sandbox
ai
a growing set of hands-on courses for engineers working on real agent systems — the tools aws ships, the patterns that hold up in production, and the protocols between them. framework-agnostic where it can be, specific where it needs to be.
what /ai/ is
the /ai/ pillar is for engineers who already ship software and now need to ship agents. not "what is an llm." not "prompt engineering tips." every lesson assumes you can read typescript and have shipped at least one production system; we spend the time on the parts that actually break in production — runtime contracts, memory boundaries, tool schemas, identity propagation, observability, and the diff between a demo and a deploy.
how the lessons work
every lesson is a runnable typescript editor in your browser. types
are stripped and code executes in a module worker — no server, no
keys, no costs. for the agentcore course, we publish a mocked
bedrock-agentcore sdk with the same public surface as
the real one, so the code you write here is the code you'd ship,
minus the deploy. for agentic patterns, the model is replaced with
a scripted stand-in so you can iterate on the loop without burning
tokens. nothing you type leaves your browser.
what makes this different
most agent tutorials show you the happy path on someone else's framework. the courses here cover the unhappy path — what fails first under load, where the contract between agent and tool gets ambiguous, when memory is the wrong abstraction. opinions are owned, citations are inline, and the lesson list above is updated in place as the underlying tools evolve.
writing
- spec-kit, in practicethe spec is the artifact. the code is the side-effect
- eval-driven prompt iterationwrite the eval first. iterate the prompt against it
- tool use error handling patterns in typescriptthe agent doesn't care about exceptions. structure the result instead
- structured outputs: claude vs openai, in practicethe apis look similar. the failure modes don't