Skip to main content
Mythos

The complete feature surface of ๐Ÿ“Claude Code, organized by ๐Ÿ“Anthropic's own documentation categories and compiled from its published docs. Features with a dedicated memo link to it; the rest are listed by capability. Terms are defined separately in the ๐Ÿ“Claude Code Glossary. For the full collection, browse ๐Ÿท๏ธ#feature-of-claude-code.

Surfaces

  • Terminal CLI โ€” the full-featured command line for editing files, running commands, and managing a whole project
  • VS Code extension โ€” inline diffs, @-mentions, plan review, and conversation history inside the editor
  • JetBrains plugin โ€” IntelliJ, PyCharm, WebStorm and others, with interactive diffs and selection context sharing
  • Desktop app โ€” parallel sessions with git isolation, visual diff review, an integrated terminal, and app previews
  • Claude Code on the web โ€” browser sessions with no local setup, for long tasks and repos you do not have locally
  • Claude Code on mobile โ€” start, monitor, and steer tasks from the Claude app for iOS and Android
  • Development containers โ€” run Claude Code inside a dev container for a consistent, isolated environment across a team

Instructions and Memory

  • ๐Ÿ“CLAUDE.md โ€” a markdown file read at the start of every session for standards, architecture, and context
  • Auto memory โ€” accumulates build commands and debugging learnings across sessions without you writing anything
  • ๐Ÿ“Claude Code Memory โ€” file-based persistence that survives across conversations
  • The .claude directory โ€” where CLAUDE.md, settings, hooks, skills, commands, subagents, workflows, and rules live
  • Nested CLAUDE.md files โ€” per-package instructions so a monorepo session stays focused on the code in hand

Extending Claude Code

  • ๐Ÿ“Skill โ€” packaged repeatable workflows a team can share, plus custom commands and bundled skills
  • ๐Ÿ“Slash Command โ€” a typed command invoking a built-in or a skill registered via plugin
  • ๐Ÿ“Hook โ€” shell commands that run automatically on file edits, task completion, or input requests
  • ๐Ÿ“Claude Code Plugin โ€” skills, agents, hooks, and MCP servers bundled as one installable unit
  • Plugin marketplaces โ€” discover, install, and distribute prebuilt plugins across teams and communities
  • ๐Ÿ“MCP Server โ€” connects to external tools and data over ๐Ÿ“Model Context Protocol (MCP)
  • Output styles โ€” alternative system prompts that adapt Claude Code for work beyond software engineering
  • Keyboard shortcuts โ€” customize keybindings through a configuration file

Agents and Orchestration

  • ๐Ÿ“Subagents โ€” specialized agents with isolated context for task-specific work, running in the background by default
  • Agent view โ€” dispatch and manage many sessions from one screen, showing which ones need your input
  • Agent teams โ€” coordinate multiple instances with shared tasks, inter-agent messaging, and central management
  • Dynamic workflows โ€” a rerunnable script orchestrating many subagents for audits, migrations, and cross-checked research
  • ๐Ÿ“Worktree โ€” isolated git worktrees so parallel sessions never collide on the same files
  • Cross-session messaging โ€” list and message your other sessions on one machine, or across machines via Remote Control

Session Control

  • ๐Ÿ“Plan Mode โ€” propose an approach before any writes, and proceed only on your approval
  • ๐Ÿ“Auto Mode โ€” a classifier handles routine decisions against repos, buckets, and domains your org trusts
  • ๐Ÿ“Permissions โ€” fine-grained allow, ask, and deny rules over tools, commands, and MCP calls
  • Permission modes โ€” cycle how often Claude asks before editing files or running commands
  • ๐Ÿ“settings.json โ€” global and project-level configuration, plus environment variables
  • Sessions โ€” name, resume, branch, and switch conversations, including resuming the session that opened a pull request
  • Checkpointing โ€” track, rewind, and summarize edits and conversation to manage session state
  • ๐Ÿ“/goal โ€” sets a completion condition and keeps working across turns until it holds
  • Interactive mode โ€” keyboard shortcuts, input modes, and the interactive features of a live session
  • Voice dictation โ€” speak your prompts with hold-to-record or tap-to-record
  • Status line โ€” a custom bar monitoring context usage, cost, and git status
  • Screen reader mode โ€” VoiceOver and NVDA support, plus magnifier, reduced-motion, and colorblind-friendly themes
  • Fullscreen rendering โ€” flicker-free output with mouse support and stable memory in long conversations

Context and Cost

  • ๐Ÿ“context window โ€” what loads automatically, what each file read costs, and when rules and hooks fire
  • ๐Ÿ“Compaction โ€” automatic summarization as a conversation approaches the context limit
  • Prompt caching โ€” managed automatically, with a model switch triggering one slow uncached turn
  • ๐Ÿ“ENABLE_PROMPT_CACHING_1H โ€” the extended one-hour cache for important but less frequently hit context
  • ๐Ÿ“Model โ€” model configuration including aliases such as opusplan
  • Fast mode โ€” faster Opus responses, toggled per session
  • Cost management โ€” token tracking, team spend limits, and the levers that actually reduce spend

Automation and Scheduling

  • ๐Ÿ“Claude Code Routines โ€” cloud runs on a schedule, on API calls, or on GitHub events, working while your machine is off
  • Desktop scheduled tasks โ€” recurring runs on your own machine with direct access to local files and tools
  • /loop and cron tools โ€” repeat a prompt within a session, poll for status, or set a one-time reminder
  • ๐Ÿ“Headless Mode โ€” run Claude Code programmatically from the CLI, Python, or TypeScript
  • Deep links โ€” open a session from a URL, so a click in a runbook, alert, or dashboard lands in the right repo

Remote Work and Handoff

  • Remote Control โ€” continue a local session from your phone, tablet, or any browser
  • Cloud sessions โ€” move work between web and terminal with the cloud and teleport flags
  • Dispatch โ€” message a task from your phone and open the desktop session it creates
  • Cloud environments โ€” configure network access levels, environment variables, setup scripts, and caching
  • Self-hosted environments โ€” run cloud sessions on infrastructure you control, with your own runners and identity

Integrations

  • Chrome โ€” test web apps, debug with console logs, automate form filling, and extract data from pages
  • Computer use โ€” open apps, click, type, and see your screen on macOS from the CLI
  • GitHub Actions โ€” respond to mentions, automate tasks, and turn issues into pull requests
  • GitLab CI/CD โ€” the same automation on GitLab pipelines
  • Code Review โ€” automated PR review catching logic errors, security vulnerabilities, and regressions
  • ultrareview โ€” a deep multi-agent cloud review that finds and verifies bugs before you merge
  • Claude Tag โ€” brings Claude into your team's Slack channels
  • Slack โ€” delegate coding tasks from a workspace; being retired for Team and Enterprise in favor of Claude Tag
  • Artifacts โ€” publish session output as a live, interactive page on claude.ai, private or shared
  • GitHub Enterprise Server โ€” connect web sessions, code review, and plugin marketplaces to a self-hosted instance

Security and Isolation

  • Sandboxed Bash tool โ€” filesystem and network isolation for safer, more autonomous execution
  • Sandbox environments โ€” pick an isolation level across the sandboxed tool, sandbox runtime, dev containers, Docker, and VMs
  • Claude Security plugin โ€” scans a codebase for vulnerabilities and turns findings into patches you review and apply
  • security-guidance plugin โ€” has Claude review its own changes for vulnerabilities and fix them in the same session
  • Zero data retention โ€” available to qualified Claude for Enterprise accounts, with a documented disabled-feature set

Agent SDK

  • Agent SDK โ€” build production agents with Claude Code as a library, in TypeScript or Python
  • Custom tools โ€” define your own functions as tools through an in-process MCP server
  • Structured outputs โ€” return validated JSON from agent workflows using JSON Schema, Zod, or Pydantic
  • SDK sessions โ€” persist, resume, and fork conversation history, optionally mirrored to S3, Redis, or your own backend
  • File checkpointing โ€” track file changes during a run and restore files to any previous state
  • Tool search โ€” scale an agent to thousands of tools by loading only what the task needs
  • Observability โ€” export traces, metrics, and events to your backend over OpenTelemetry
  • SDK hosting โ€” subprocess architecture, session persistence, scaling, and multi-tenant isolation

Enterprise Deployment

  • Managed settings โ€” centrally enforce policy, model access, and configuration across an organization
  • Server-managed settings โ€” deliver that configuration from a server without device management infrastructure
  • Claude apps gateway โ€” a self-hosted gateway with SSO, per-group model access, spend limits, and OTLP telemetry
  • Other LLM gateways โ€” route Claude Code through a gateway your organization already runs
  • Amazon Bedrock โ€” run Claude Code against Bedrock with its own setup and IAM configuration
  • Claude Platform on AWS โ€” the Anthropic-operated API with AWS authentication and Marketplace billing
  • Google Cloud's Agent Platform โ€” formerly Vertex AI, with its own setup and IAM configuration
  • Microsoft Foundry โ€” run Claude Code through Foundry
  • Managed MCP โ€” restrict which MCP servers users can add or connect to, with allowlists and denylists
  • Team analytics โ€” usage metrics, adoption tracking, and engineering velocity in a dashboard
  • OpenTelemetry monitoring โ€” export Claude Code telemetry to your observability backend
  • Enterprise network configuration โ€” proxy servers, custom certificate authorities, and mutual TLS
  • Feature availability matrix โ€” which features work on each subscription plan, console, and cloud provider

Contexts

Created with ๐Ÿ’œ by One Inc | Copyright 2026