Skip to main content
What this unit solvesThe AI tools you pay for ship a full suite of built-in features: web search, code execution, Artifacts, persistent memory, connectors, slash commands. Most users tap less than a third of them. The problem is not complexity — it is the absence of a systematic way to track “what capabilities exist right now.” This unit inventories the built-in capabilities of the main tools so you know what each feature solves, where its limits are, and when it should be your first choice. It also establishes a rhythm for staying current: since you are already paying, use everything.

​
Learning objectives

  • Inventory the currently available built-in features of your primary AI tools (at minimum Anthropic Claude and OpenAI ChatGPT).
  • Track official changelogs and release notes for each tool so you know when new features land.
  • Explain what each built-in feature solves, where its limits are, and when to prefer it.
  • Identify plugins or custom-built solutions in your workflow that have already been superseded by built-in features, and decide whether to retire them.

​
1. Why tracking built-in capabilities matters: you are paying for more than you use

The largest hidden cost of a paid plan is not the bill — it is “feature sitting there unused equals money wasted.” A typical example: you subscribe to Claude Pro but only use the chat window to write prompts. Web search is off, Projects is empty, Artifacts has never run a front-end prototype, Cowork is not connected to anything on your desktop. A year passes and you have used 20% of what you paid for. The other 80% is not “irrelevant” — you just never read the changelog.
Build the update habitSpend 30 minutes each month scanning the release notes for your primary tools. Do not rely on third-party article summaries (they go stale and get truncated). Subscribe directly to official changelogs. Anthropic release notes: support.claude.com/en/articles/12138966-release-notes (as of 2026-05; verify the current URL on the official site). OpenAI: help.openai.com/en/collections/3742473-chatgpt. Google: support.google.com/gemini. GitHub: github.blog/changelog/label/copilot/. Cursor: cursor.com/docs [needs source verification: authoritative Cursor changelog URL as of 2026-05].
The reality of feature flags: some features roll out gradually to accounts and are not visible to all users at the same time. The settings panel in the Claude.ai interface and the /config command in Claude Code are the places where you actively confirm what is currently enabled. Features that are off by default are often the most undervalued and the ones that justify the paid tier.

​
2. Built-in tool inventory (as of 2026-05)

Claude.ai chat interface:
Built-in featurePurposeLimits
Web searchReal-time web lookup with citations during chatCitation source quality varies; academic verification still requires manual cross-checking
Code execution (Artifacts)Run JavaScript / Python in a sandbox during chat; output shareable HTML, SVG, interactive componentsSandbox resources are limited; not suitable for heavy computation. Language support: see current official docs [needs source verification: complete language list as of 2026-05]
Projects (incl. Project Knowledge)Create a project for a specific topic; keep documents, guidelines, and conversation context persistentEach project has a storage cap; curate what goes in rather than dumping entire folders
MemorySave preferences and facts across conversations (upgraded plans)Training opt-out and retention period must be confirmed in settings [needs source verification: Memory plan tiers as of 2026-05]
ConnectorsConnect Claude.ai to Google Drive, Dropbox, Gmail, and other sourcesRequires manual authorization; review OAuth scope
Research (Deep Research)Multi-step research tasks, cross-source synthesis with citationsRequires Pro / Max / Team plan
Slash commands/help, /clear, /compact, /init, and othersFull list: run /help in the interface
Claude Code CLI:
Built-in featurePurposeLimits
Read / Write / EditFile read and writeUse permissions.deny to block access to .env, sensitive paths, and restricted directories
Glob / GrepFile searchHeavy file loads consume context; use path-scoped rules or Subagent isolation
BashExecute shell commandsRead-only commands (ls, cat, grep, git status, etc.) proceed without a prompt [1]; others follow settings.json allow / deny rules
WebFetchFetch content from a specified URLSubject to WebFetch(domain:...) permission allowlist; fetched content is a prompt injection surface
WebSearchWeb searchSame underlying capability as Claude.ai built-in Web search
Slash commands/help, /clear, /compact, /init, /agents, /mcp, /permissions, and othersFull list: run /help
Agent / SubagentSub-tasks with isolated contextSee 04-5 Subagent
Skill / Hook / PluginCustom extensionsSee 04-3, 04-4, 04-6, 04-7
MCP clientConnect to external toolsSee 04-9 MCP Integration
LSP serverReal-time code intelligenceSee 04-7 Plugin; for TypeScript, Python, Rust and other mainstream languages, prefer pre-built integrations from the claude-plugins-official marketplace [1]
WorktreePhysical isolationSee isolation: worktree in 04-5 Subagent
Claude Cowork:A desktop agentic product from Anthropic, aimed at knowledge workers, capable of completing multi-step tasks on local files and applications. For the distinction from Claude Code, see 01-7 AI Tool Landscape 2026 and 02-2 Anthropic Claude Setup. The full built-in feature list for Cowork (file search, desktop integration, callable applications) should be verified against anthropic.com/product/claude-cowork [needs source verification].

​
3. Cross-vendor comparison

ConceptAnthropic Claude (primary)OpenAIGoogleGitHub CopilotCursor (brief)
Web searchClaude.ai and Claude Code, can be enabled [1]ChatGPT Plus/Pro built-inGemini Grounding built-inTriggered via Chat in IDE (semantic search)Triggered via Chat in IDE
Code execution sandboxClaude.ai Artifacts (JS/Python) [needs source verification]Advanced Data Analysis (Python)Gemini sandbox (Python)Cloud coding agent runs in isolated environmentNot in primary workflow
Persistent memoryProjects Knowledge, Claude Code Memory [1]ChatGPT Memory [needs source verification]Gems memory [needs source verification]Not in primary workflowNot in primary workflow
Built-in connectorsClaude.ai connects to Google Drive, Dropbox, etc. [needs source verification]ChatGPT connects to Google Drive, Dropbox, GitHubDeep Workspace integration (Docs / Drive / Gmail / Calendar)@github context (PRs, issues)@Codebase and @Docs
Slash commandsClaude Code /help, /compact, /init, etc.ChatGPT does not emphasize slash commands; GPTs provide entry pointsGemini built-in commands/fix, /tests, /explainIDE / menu
Interactive output (Artifacts / Canvas)Artifacts (HTML, code, SVG) [needs source verification]Canvas(primarily conversational)Not applicableNot applicable
Multi-file editing agentClaude Code + SubagentCodex CLI / CloudAntigravity CLICopilot Edits, Agent modeComposer
MCP clientBuilt-in (/mcp and .mcp.json) [2]Scope: verify against current OpenAI docs [needs source verification]Scope: verify against current Google docs [needs source verification]Preview stage [needs source verification]Built-in [needs source verification]
Custom extension mechanismSkill / Subagent / Hook / PluginCustom GPT, Codex skills / agentsGems, Antigravity skills / agents.prompt.md, prompt files.cursor/rules/*.mdc, Composer rules
Naming clarifications
  • Claude Code and Claude.ai are two separate products: the former is a CLI agent (developer-facing); the latter is a chat interface (knowledge-worker-facing). Claude Cowork is a third product (desktop agentic), and it is not interoperable with Claude Code.
  • OpenAI Codex CLI, ChatGPT, and Operator are three separate product lines: CLI for developers, chat for knowledge workers, cloud browser agent. Their built-in features do not cross over.
  • Google Gemini, Gemini for Google Workspace, and Antigravity are three separate product lines: standalone chat app, Workspace assistant, CLI agent. Their built-in features do not cross over.
  • Cursor is a third-party IDE (Anysphere). This Playbook lists it briefly for comparison only.

​
4. How to stay current

Four tracking paths, from lightest to deepest:
1

Official release notes

Anthropic: support.claude.com/en/articles/12138966-release-notes [needs source verification: URL still valid as of 2026-05]. OpenAI: help.openai.com/en/collections/3742473-chatgpt. Google: support.google.com/gemini. GitHub: github.blog/changelog/label/copilot/. Cursor: cursor.com/changelog [needs source verification].
2

Official changelog RSS

Most vendors provide an RSS feed. Subscribe with any RSS reader and get notified automatically when features land.
3

Official X / Twitter accounts

@AnthropicAI, @OpenAI, @GoogleAI, @GitHubCopilot, @cursor_ai. Feature announcements typically appear before the full release notes.
4

Direct feature flag inspection

Do not wait for the changelog to find out what is new. Once a month, open your primary tool’s settings page and scan the “Experimental features,” “Beta,” and “What’s new” sections.
Version number does not equal new featuresThe difference between Claude Code v2.1.x and v2.1.y does not necessarily indicate a feature change. Read the “What’s new” section of the release notes; do not rely on the version number alone. For CLI tools, claude --version returns the patch version number, which frequently has no relationship to functional changes.
The 30-minute monthly routinePut it on the calendar: the first Monday of every month at 09:00, 30 minutes, scan “primary CLI release notes + chat interface changelog + settings page new feature flags” in that order. Thirty minutes multiplied by the value of the features you discover and actually use compounds faster than any prompt engineering gains.

​
5. The criteria for full use: what each feature solves and where it stops

Do not use something just because it looks impressive. Do not ignore something just because you have never tried it. Run every feature through these three questions:
  1. What problem does it solve? If you cannot write down a concrete scenario in one sentence, it is not worth adopting.
  2. Where are its limits? Input capacity, output constraints, rate limits, quotas, plan tiers, failure conditions.
  3. Which step in your workflow can it replace? Replacement has value; stacking it on top only adds complexity.
Common judgment traps:
  • Web search: excellent for recent data, pricing, news, documentation changes. Not a substitute for academic citation work that requires precise sourcing (citation quality varies; URL hallucination is a real risk).
  • Code execution / Artifacts sandbox: excellent for quick verification, interactive demos, front-end prototyping. Not suitable for heavy computation (resources are limited) or services that require persistent state.
  • Projects / Memory: excellent for standing information you want across every conversation (glossaries, team conventions, research direction). Not appropriate for sensitive personal data (training opt-out requires per-item confirmation), or for infrequent one-off context.
  • Connectors: excellent for letting the model read from data sources you already own (Drive, Dropbox, Notion, Linear, GitHub). Not a substitute for a proper ETL pipeline (OAuth scope, rate limits, and auditability are fundamentally different).
Judgment example: should you build a custom web search wrapper?Before writing a line of code, check:
  1. Does Claude.ai Pro have built-in Web search? Yes.
  2. Can it handle your verification use case? In 90% of scenarios, yes (citations included, recent data covered).
  3. What does your custom wrapper add over the built-in? Probably just “a URL allowlist I control” and “custom output format.”
Conclusion: for most people, use Claude.ai built-in Web search and instruct it in the prompt to “only cite domains from my allowlist.” A custom wrapper only makes sense when allowlist enforcement is a hard compliance requirement or when you need to connect custom back-end logic.

​
6. Anti-patterns

  • Installing plugins to recreate built-in functionality: custom web search wrappers, custom long-context summarizers, custom memory systems. When built-in features already cover 90% of the use case, this wastes maintenance budget. The exception is compliance or customization requirements that built-in features genuinely cannot meet.
  • Paying for features and leaving them off: subscribing to Pro and never enabling Web search, never using Projects, never running Artifacts for front-end prototyping. That is loss, not frugality. Monthly changelog scanning is the prevention.
  • Building custom solutions without checking the changelog: what you spent two weeks building may have been shipped by the vendor last month. The cost of staying current is far lower than the cost of duplicate work.
  • Mixing equivalent features from multiple tools: running web search simultaneously in Claude.ai, ChatGPT, and Gemini produces “same query, different sources, contradictory conclusions” and makes debugging integration behavior almost impossible. Pick one primary tool per workflow; treat the others as fallback only.

​
Hands-on exercise

30-minute practice
1

Inventory the gap (15 minutes)

Open the settings page of your primary AI tool and list every built-in feature currently enabled. Compare that list against what you have actually used in the past month. Where are the gaps? Sort unused features into “worth trying once” and “not relevant.” Write down three you want to try.
2

Subscribe to one changelog (5 minutes)

Pick one official changelog for your primary tool (URL or RSS feed) and add it to your RSS reader or browser bookmarks.
3

Read the recent release notes (10 minutes)

Read the last 90 days of release notes. List three features you did not know about until now and evaluate whether each is worth adopting.

​
Common pitfalls

Anti-pattern list
  • Assuming a feature does not exist when it is just not enabled: many features (Web search, Projects, Memory, Connectors, experimental flags) require manual activation or authorization in settings. Opening the settings page and scanning it once is worth more than any amount of prompt engineering.
  • Mixing built-in features with third-party plugins for the same task, creating inconsistent behavior: if “look up the latest docs” runs through both the built-in Web search and an external wrapper simultaneously, you cannot tell which source produced which result when debugging. Pick one primary tool per workflow.
  • Learning a tool’s capabilities from third-party tutorials rather than official documentation: tutorials go stale; the official changelog is the source of truth. When writing instructional material, always annotate “as of YYYY-MM” with a link to the official URL.
  • Treating Beta / Preview features as Production-ready: Agent mode, Memory, Background Agent, and similar preview features can change model behavior, APIs, and UX at any time. Production environments should be pinned to GA (General Availability) features.
  • Believing that “tracking updates” is only for engineers: researchers, product managers, and students need it equally. The prompts and workflows you write depend on the tool’s current capabilities; not knowing what has been added means you keep working within last year’s constraints.

​
Self-check

The bar for passing this unit
  1. Can you list five built-in features of your primary tool in under five minutes, and for each one describe what it solves and where its limits are?
  2. Do you have a fixed update-tracking routine? Thirty minutes per month, on the calendar.
  3. Is there anywhere in your workflow where a custom component already has a built-in equivalent? Identify at least one and decide whether to retire it.
  4. Has anything shipped in the past month that you did not know about? Open the changelog now and record the most recent entry you find.

​
Sources and further reading

Factual claims are grounded in official documentation; fast-changing items are annotated as of 2026-05.
  • [1] Anthropic, “Claude Code overview & permissions,” code.claude.com, 2026. [Online]. Available: https://code.claude.com/docs/en/permissions (as of 2026-05; covers tool tiers, read-only command list, permission rules)
  • [2] Anthropic, “Connect Claude Code to tools via MCP,” code.claude.com, 2026. [Online]. Available: https://code.claude.com/docs/en/mcp (as of 2026-05; MCP client and .mcp.json configuration)