Claude Code Glossary: 20+ Terms in Plain Human English

A Claude Code glossary of terms for non-programmers: tokens, context window, skills, hooks, MCP, subagents — each in one sentence plus a simple analogy.

6 min readUpdated 2026-06-12EAEvgeny ArsentyevEvgeny Arsentyev · PhD

This is a Claude Code glossary of terms written for humans, not engineers: every word you'll actually meet in your first month, explained in one plain sentence plus an analogy. The official glossary has dozens of entries; I've ruthlessly picked the twenty-something a beginner genuinely bumps into.

I'm Evgeny, and my problem with most glossaries is that they define jargon using other jargon, like a dictionary written by a snake eating its tail. So here's my rule: if my mom wouldn't get the analogy, the entry gets rewritten. (And yes — it's pronounced "clode code", like the French name Claude.)

What's the difference between Claude and Claude Code?

Claude is the AI model — the brain. Claude Code is the harness around it: the tools, memory, and permission system that let that brain actually read your files, run commands, and make changes instead of just chatting. The docs call this an agentic harness; I call it giving the brain hands.

Hold onto that split — brain versus harness — because half the words below describe the brain's thinking and half describe the harness's machinery. Knowing which side a term lives on tells you most of what it means before you even read the definition.

What can Claude Code do? The core mechanics

Before the parts, the engine. These seven terms describe how the model reads, remembers, and reasons — the mechanics under every single thing Claude Code does for you.

Tokens, context window and thinking

How it thinks: the core mechanics

  1. 1Token — the small chunk of text AI actually reads and counts; like syllables for a model, and everything is billed and measured in them.
  2. 2Context window — the working memory of one session, holding your chat, files, and instructions; a desk that only fits so many papers.
  3. 3Compaction — automatic summarizing when that desk gets full: old papers are condensed into a one-page brief so work can continue.
  4. 4Extended thinking — visible step-by-step reasoning before the answer, shown in gray italics; the model showing its rough draft.
  5. 5Effort level — a dial for how hard the model thinks on each reply; low is a quick glance, high is a deep stare at the whiteboard.
  6. 6Agentic coding — a workflow where the AI acts (reads, runs, edits) while you supervise, instead of just advising you in chat.
  7. 7Agentic loop — the repeated cycle behind every task: gather context, act, check the result, repeat until done. Like cooking by tasting.

What are skills, hooks, commands and MCP?

These four are the extension points — the ways you bolt new abilities onto Claude Code. They're also the four terms most likely to scare a beginner off, which is a shame, because each is a one-liner.

Commands, skills, hooks, MCP, plugins, output styles

How you extend it

  1. 1Command — a reusable instruction you trigger by typing /name; a speed-dial button for a prompt.
  2. 2Skill — a folder with instructions Claude loads when relevant or when you call /skill-name; a recipe card it pulls out at the right moment. Skills are the modern successor to custom commands.
  3. 3Hook — a handler that fires automatically at fixed moments, like after every file edit; a doorbell that always rings, no AI discretion involved.
  4. 4MCP (Model Context Protocol) — an open standard plugging Claude into outside services like Slack, Jira, or databases; a universal power adapter for tools.
  5. 5Plugin — a bundle of skills, hooks, agents, and MCP servers installed as one unit; an IKEA flat-pack of extensions.
  6. 6Output style — a setting that changes Claude's tone and behavior by editing its system prompt; same brain, different uniform.

Who does the work: sessions, subagents and modes

The last cluster is about organizing the work itself — where a conversation lives, how it gets undone, who Claude delegates to, and what it's allowed to touch. These are the words you'll reach for most once you're actually building.

Sessions, checkpoints, subagents and permission modes

How the work is organized

  1. 1Session — one conversation tied to one folder, with its own memory; a separate notebook per project.
  2. 2Checkpoint — a restore point made at every prompt; press Esc twice or run /rewind to time-travel back before a bad change.
  3. 3CLAUDE.md — a plain text file of standing instructions you write, read at the start of every session; the note you tape to a colleague's monitor.
  4. 4Auto memory — notes Claude writes about your preferences in MEMORY.md and reloads each session; its private diary about working with you.
  5. 5Subagent — a helper Claude spawns with its own separate memory that returns only a summary; an intern sent to the archive so your desk stays clean.
  6. 6Permission mode — the session's baseline rule for what needs your approval; cycled with Shift+Tab.
  7. 7Plan mode — a permission mode where Claude researches and proposes but edits nothing until you approve; an architect who must show blueprints first.
  8. 8Worktree isolation — running Claude in a separate copy of the project so parallel sessions can't collide; giving each cook their own kitchen.
  9. 9Sandboxing — an OS-level fence around what commands can touch on disk and network; a playpen with hard walls.
  10. 10Non-interactive mode — running one prompt via `claude -p` and exiting, no conversation; a vending machine instead of a waiter.
  11. 11Verification loop — giving Claude a check it can run (tests, a build) so it iterates until things actually pass; the taste test that decides dinner is ready, not the chef's confidence.

What is "thinking" in Claude Code, and can I watch it?

Yes — the gray italic text that streams before an answer is extended thinking, the model reasoning out loud. You can turn the dial with the effort level, and the popular "ultrathink" keyword is just a shortcut for cranking it up. Watching the thinking is the single best free lesson in how the AI approaches your problem — and the best way to see your own vocabulary in action.

See your context window live
/context

Run this inside any session to watch the "desk" fill up: system prompt, files, memory, conversation. Five minutes of looking at it teaches the token/context/compaction trio better than any glossary.

Old names you'll meet in blog posts

The internet is full of outdated terms. Headless mode is now called non-interactive mode (same -p flag). Custom commands are now skills (old files still work). And "slash commands" are now just commands — the slash survived, the name didn't. If a tutorial uses the old words, it's vintage, not wrong.

Don't memorize this list — bookmark it. Then open a session, run /context, ask Claude to do something small, and watch the thinking stream by. Within a week you'll catch yourself saying "let me compact this session" like you've been doing this for years. Vocabulary follows usage, never the other way around.

#claude-code#glossary#terms#beginners#foundations
EAEvgeny Arsentyev

Author

Evgeny Arsentyev

PhD · Chief Product Officer at a healthtech company

▌ Reading is the blue pill

Want to actually build this?

Guides explain. The free course transforms — personalized, gamified, and built to get you shipping fast.

◉ Take the red pill →