Free starter · 30 min · No signup needed to read

Your first agent.
In 30 minutes.

A focused walkthrough that takes you from a blank terminal to a working AI agent that reads files, summarizes them, and saves the result. No prior agentic AI experience needed. Just a laptop and 30 focused minutes.

00 What you'll have at the end

By the end of this guide you'll have:

  • A working AI agent running on your machine
  • The ability to ask it to read any file and produce a summary
  • A starting point for everything else in the full course
This is intentionally small. The same four-part pattern — model, tools, memory, and run loop — scales into larger systems. The goal here is a working artifact you can inspect before adding complexity.

01 Mental model: what is an agent?

Strip away the marketing. An "agentic AI" is four pieces wired together:

Brain

An LLM — Claude, GPT, Llama, whatever. Reads context, decides what to do next.

Tools

Functions the LLM can call: read a file, write a file, run a command, hit an API.

Memory

Where it stores what it's learned — usually files, sometimes a database.

Loop

The thing that keeps it running. Could be a single prompt, a cron job, or a long-running process.

That's it. Everything else — multi-agent orchestration, MCP servers, vault patterns, brain cycles — is built on top of these four pieces.

For this starter, your agent will use:

  • Brain: Claude (via Claude Code, the official CLI)
  • Tools: Read, Write, Bash — built in to Claude Code
  • Memory: a file on your disk
  • Loop: a single command you run from the terminal

02 Setup (5 min)

You need three things. If you already have them, skip ahead.

1. A terminal

On Mac: Terminal (built in). On Windows: Windows Terminal with PowerShell or the Git Bash shell. On Linux: you already know.

2. Claude Code (the CLI)

Claude Code is the official Claude command-line tool. It IS the agent — you're not building one from scratch, you're configuring one.

install
# macOS / Linux
$ curl -fsSL https://claude.ai/install.sh | sh
# Windows (PowerShell)
$ irm https://claude.ai/install.ps1 | iex

Then verify:

verify
$ claude --version
claude-code 1.x.x

3. An Anthropic API key (or sign in)

Claude Code needs to talk to Claude. Either:

  • Easiest: run claude for the first time and follow the browser sign-in flow (Claude account)
  • Pro: get an API key at console.anthropic.com and set ANTHROPIC_API_KEY in your environment
Cost reality: Claude Code usage may be covered by a qualifying plan or billed through an API, depending on how you sign in. Check the current provider terms before running it, set a budget you understand, and avoid treating any monthly estimate as permanent. The full program covers cost visibility and routing choices.

03 Build your first agent

Now the fun part. Make a folder, drop a sample file in it, then ask Claude Code to summarize it.

first-agent
$ mkdir my-first-agent && cd my-first-agent
$ echo "The mitochondrion is the powerhouse of the cell. Mitochondria are responsible for energy production through ATP synthesis. They contain their own DNA, separate from the nucleus." > sample.txt
$ claude

Claude Code launches an interactive session. You're now talking to your agent.

Type this prompt and press Enter:

Prompt to your agent
Read sample.txt, write a one-sentence summary of it, and save the summary to summary.md. Then tell me what you did.

Watch what happens. Claude Code will:

  1. Use the Read tool to open sample.txt
  2. Compose a one-sentence summary in its head
  3. Use the Write tool to create summary.md
  4. Report back to you with what it did

Each of those tool uses is the agent doing things in the real world. That's the fundamental shift from "chatbot" to "agent": tools.

04 Run it and see it work

Quit Claude Code (Ctrl+C twice or type /exit). Then:

verify output
$ ls
sample.txt summary.md
$ cat summary.md
Mitochondria are organelles that produce
energy through ATP synthesis and contain
their own DNA.

The summary file exists. Your agent created it. You didn't write that file — the agent did.

That's the magic moment. Sit with it.

05 What you just did

You wired a brain (Claude), tools (Read + Write), memory (the filesystem), and a loop (one prompt) into something that did work.

This is the core pattern. Scheduled briefs, multi-step research, specialist agents, and custom skills all extend these four pieces. Each extension should earn its complexity by improving a real workflow.

The useful leap is repeatability, not spectacle. Run the same task again, inspect the output, identify a failure, and improve the instructions or permissions. That learning loop is what the full program expands.

06 Where to go from here

You have a foundation. Three honest options:

Keep going on your own

Try this prompt next: “Read all .txt files in this directory and write a combined summary to digest.md.” Watch how the same agent extends naturally to multi-file work.

Take the self-paced program

Ten modules extend this pattern into memory, custom tools, orchestration, security, cost controls, and a capstone based on your workflow.

Get self-paced — $149 →

Build it with me

The Guided Build includes the full program and one 90-minute screen-shared session to adapt it to real work or resolve a blocker.

Get guided — $449 →

That's the starter. If this got you somewhere, tell a friend.

— Alex