Text of code.claude.com › docs › en › glossary as Styx crawled it on Nov 19, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Glossary - Claude Code Docs

Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. This glossary defines Claude Code terminology. Each entry links to the page where the concept is covered in depth. For model-level concepts like tokens, temperature, and RAG, see the platform glossary .

For Claude Desktop terms such as desktop extension, MCPB, and DXT, see the Claude Help Center . A AGENTS.md A markdown file of project instructions you write for AI coding agents. If your repository has one and no CLAUDE.md , Claude reads it as your project instructions without you adding a second file. You can change the Project instructions setting in /config to have Claude read both files or only CLAUDE.md . Reading AGENTS.md directly requires Claude Code v2.1.277 or later.

In some sessions Claude can’t read AGENTS.md , so import it from a CLAUDE.md there instead. Learn more: AGENTS.md Agent teams Multiple independent Claude Code sessions coordinated by a team lead, with a shared task list and peer-to-peer messaging. Unlike subagents , which run within a single session and report only to the parent, teammates each have their own context window and you can interact with any of them directly.

Agent teams are experimental and disabled by default; see Enable agent teams . Learn more: Run agent teams Agentic coding A workflow where the AI can read files, run commands, and make changes autonomously while you watch, redirect, or step away, as opposed to chat-based assistants that only respond with text you must apply yourself. Claude Code is agentic because it has tools that let it act, not just advise. Learn more: How Claude Code works Agentic harness The tools, context management, and execution environment that turn a language model into a capable coding agent.

Claude Code is the harness; Claude is the model inside it. The harness supplies file access, shell execution, permission gating, memory loading, and the loop that chains actions together. Learn more: How Claude Code works Agentic loop The cycle Claude works through for every task: gather context, take action, verify results, and repeat until done. Each tool use returns information that informs the next step. You can interrupt the loop at any point to redirect.

Most extension points, including hooks , skills , and MCP , plug into specific phases of this loop. Learn more: How Claude Code works Artifact A live, interactive web page Claude Code publishes from your session to a private URL on claude.ai, so you can see output visually or share it instead of reading terminal text. The page updates in place when the session republishes. Artifacts you create from Claude Code appear in the same gallery as artifacts created in claude.ai conversations.

Sharing options depend on your plan: see Share an artifact . Learn more: Share session output as artifacts Auto memory Notes Claude writes for itself based on your corrections and preferences, stored per git repository under ~/.claude/projects/ . All worktrees of the same repository share one auto memory directory. The first 200 lines or 25 KB of the MEMORY.md index loads at the start of every session. Auto memory is the Claude-written counterpart to CLAUDE.md , which you write.

Learn more: Auto memory Auto mode A permission mode where a separate classifier model reviews actions instead of you, so Claude Code runs most of them without asking you. Claude Code still asks you before actions your explicit ask rules match. The classifier blocks scope escalation, untrusted infrastructure, and prompt injection . Claude Code v2.1.283 or later : auto mode is the built-in starting permission mode for interactive terminal and VS Code sessions Earlier versions : auto mode is the built-in starting permission mode only on Pro, Max, Ultra, and Team plans Learn more: Eliminate prompts with auto mode B Bare mode With --bare , Claude Code starts without loading hooks, skills, custom commands, subagents, installed plugins, MCP servers, auto memory, or CLAUDE.md, apart from skills in a directory you pass with --add-dir .

Recommended for CI and scripted calls where you need the same result on every machine. Learn more: Start faster with bare mode Bundled skills Prompt-based playbooks included with Claude Code, such as /batch , /code-review , /debug , and /loop . Unlike built-in commands, which execute fixed logic, bundled skills give Claude a detailed prompt and let it orchestrate the work, so they can spawn agents, read files, and adapt to your codebase.

Learn more: Bundled skills C Channel An MCP server that pushes events into your running session so Claude can react to things that happen while you’re away from the terminal. Channels can be two-way: Claude reads an inbound event and replies back through the same channel. Telegram, Discord, and iMessage are included in the research preview. Learn more: Channels Checkpoint A restore point created at each prompt you send that starts a turn.

Claude Code snapshots files before every edit so a checkpoint can revert them. Press Esc twice or run /rewind to restore code, conversation, or both to an earlier point, or to summarize part of the conversation from a selected message. Checkpoints are saved with the conversation, so a resumed session can still /rewind to them. Rewinding doesn’t undo a Bash command’s changes to a file unless Claude had already used its file editing tools on that file in your conversation.

Learn more: Checkpointing .claude directory The directory where Claude Code reads project-scoped configuration: settings, hooks, skills, subagents, rules, and auto memory. A project has .claude/ at its root; your user-level defaults are at ~/.claude/ . Learn more: The .claude directory CLAUDE.md A markdown file of persistent instructions you write for Claude, loaded at the start of every session as a user message after the system prompt.

Put project conventions, architecture notes, and “always do X” rules here. Project-root CLAUDE.md survives compaction and is re-read fresh from disk afterward. You can place CLAUDE.md at project scope in ./CLAUDE.md or ./.claude/CLAUDE.md , at user scope in ~/.claude/CLAUDE.md , or as managed policy for your organization. All discovered files are concatenated into context rather than overriding each other, ordered from broadest scope to most specific.

Claude Code can also load a project’s AGENTS.md files in place of CLAUDE.md. Learn more: CLAUDE.md files Cloud session A Claude Code session that keeps running after you close your laptop, because it runs on cloud infrastructure instead of your machine. That infrastructure is Anthropic-managed by default, or a self-hosted environment your organization operates. You start one from claude.ai/code, the Claude mobile app, the Desktop app with Cloud selected, claude --cloud , or a cloud scheduled task .

A session in your terminal, IDE, or the Desktop app with Local selected is a local session; to reach a local session from another device, use Remote Control . Learn more: Use Claude Code in the cloud Command A reusable instruction you invoke by typing /name in the prompt. Built-in commands such as /clear , /model , and /compact control the session. You can define your own commands as files in .claude/commands/ , or install them from a plugin .

Skills are the recommended way to package multi-step commands. Two other uses of the word are unrelated: claude CLI subcommands such as claude mcp add , listed in the CLI reference , and the command field of a stdio MCP server entry, which specifies the executable Claude Code launches to start the server. Learn more: Commands · Skills Compaction Automatic summarization of your conversation when the context window approaches its limit.

Project-root CLAUDE.md and auto memory survive compaction, but instructions given only in conversation may not. Run /compact to tr

The rest of this page is on the live site.