Beyond the chat

In Level 10 you learned to make Claude do more in one sitting — subagents working in parallel, skills it reaches for automatically. But it was still you: typing a prompt, watching it work, reading the result.

This level is different. It’s about the two walls around that sitting, and how to take them down.

Wall one: Claude only sees the folder you opened it in. Wall two: Claude only works while you’re sitting there watching it.

The whole level is four tools that knock those walls down. Here’s the map before we go deep on each.

Wall one — Claude’s reach

By default Claude reads your files and runs commands in your project. That’s a lot. But your real work lives in more places than one folder: tickets in a tracker, messages in Slack, rows in a database, designs in Figma, a knowledge base in Notion.

MCP (Lesson 11.2 and 11.3) is the standard plug that connects those systems to Claude. Once a system is plugged in, Claude can read from it and act on it the same way it reads your files — no copy-pasting screenshots into the chat.

Wall two — the human in the chair

Right now, nothing happens unless you type. That’s safe, but it’s also a ceiling. Three tools lift it:

• Hooks (11.4, 11.5) — small automations that fire on their own when Claude does something. Format the file every time it’s edited. Block a dangerous command before it runs. You set it once; it happens forever, without being asked.
• Headless mode and the SDK (11.6, 11.7) — Claude with no chat window at all. A command you can pipe into, put in a script, or build a whole program around.
• Scheduled agents and CI (11.8, 11.9) — Claude on a clock or a trigger. Running at 9am Monday. Reviewing every pull request the moment it opens. While you sleep.

The honest framing

Most people who use Claude Code never touch this level, and that’s fine — Levels 0–9 are the whole job for most work. You’re here because you’ve hit the edge of what one person, typing, can keep up with. These four tools are how you get past that edge.

None of them is hard. Each is one idea. The trick is knowing which one fits the problem in front of you — and that’s mostly what the next eight lessons are for.

What’s next

Start with reach. We’ll meet MCP — the standard that lets Claude talk to systems far beyond your project folder — and figure out why it exists before we plug anything in.