A
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 teamsAgentic 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 worksAgentic 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 worksAgentic 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 worksArtifact
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 depends on your plan: on Pro and Max, a public link that anyone can open; on Team and Enterprise, sharing within your organization, plus public links once an Owner enables them. Learn more: Share session output as artifactsAuto 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. On Pro, Max, and Team plans, auto mode is the built-in starting permission mode for interactive terminal and VS Code sessions. The classifier blocks scope escalation, untrusted infrastructure, and prompt injection. Tool results are stripped from what it sees, so hostile content in a file or web page can’t manipulate it directly. Learn more: Eliminate prompts with auto modeB
Bare mode
With--bare, Claude Code starts without loading hooks, skills, custom commands, subagents, 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: ChannelsCheckpoint
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. PressEsc 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. They’re separate from git and don’t track changes made through the Bash tool.
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: