Claude

Also known as: Claude AI

On this page 7

Claude is a family of large language models developed by Anthropic, and also the name of the AI assistant built on those models. Among AI models & assistants, Claude is known for long context windows, strong performance in writing, analysis and software engineering, and a safety approach based on an explicit set of principles known as Constitutional AI.

Claude is offered in several ways: as a chat assistant in web, desktop and mobile apps, as a developer API, through major cloud platforms such as Amazon Bedrock and Google Cloud Vertex AI, and inside agentic tools such as Claude Code. The informal name Claude AI usually refers to the consumer assistant rather than to a specific model version.

How Claude models are built and trained

Claude models are decoder-only transformer networks trained in two broad phases. Pretraining on a large corpus of public web data, licensed data and other text teaches next-token prediction, which gives the model general language and reasoning ability. Post-training then shapes the raw model into a helpful assistant that follows instructions and declines harmful requests.

Post-training combines reinforcement learning from human feedback (RLHF) with Constitutional AI, a method Anthropic introduced in which the model critiques and revises its own outputs against a written set of principles. AI-generated feedback based on that constitution partly replaces human labels, which makes the intended values explicit and auditable rather than implicit in thousands of rater judgments.

The table below lists the training elements that most influence how Claude behaves.

ElementPurposeEffect on behavior
PretrainingLearn language, facts and patternsBroad knowledge up to a training cutoff
Supervised fine-tuningImitate high-quality demonstrationsConsistent assistant style
RLHFOptimize for human-preferred answersHelpfulness and better tone
Constitutional AISelf-critique against written principlesHarmlessness with stated reasons
Reasoning trainingReward correct multi-step solutionsStronger math, code and planning
Main training elements behind Claude

Claude model tiers and generations

Since the Claude 3 family in 2024, Anthropic has released models in three tiers that trade capability against speed and cost. The names describe relative size and remain stable across generations, while version numbers mark successive releases.

TierPositioningTypical uses
HaikuSmallest, fastest and cheapestClassification, extraction, high-volume chat
SonnetBalance of capability and costCoding, analysis, most production workloads
OpusMost capable and most expensiveHard reasoning, long agentic tasks, research
Claude model tiers

The first Claude was released in March 2023, followed by Claude 2, the Claude 3 family, Claude 3.5 Sonnet and later generations from Claude 4 onward. Newer releases added image input, extended thinking that lets the model reason step by step before answering, and context windows of about 200,000 tokens, with larger windows available for selected models. Because versions change frequently, applications should pin an exact model identifier rather than rely on an alias.

Capabilities and developer features

Claude is a text-in, text-out model with vision input: it reads text, images and documents such as PDFs, and produces text, including code and structured data. It does not natively generate images or audio. Its strengths are most visible in long-document analysis, careful writing and software engineering tasks.

  • Tool use: the model calls developer-defined functions with JSON arguments.
  • Computer use: the model operates a desktop through screenshots, mouse and keyboard actions.
  • Model Context Protocol (MCP): an open standard from Anthropic for connecting assistants to data sources and tools.
  • Prompt caching: reuse of a long, stable prompt prefix to cut cost and latency.
  • Batch processing: asynchronous jobs at lower price for non-urgent workloads.
  • Agentic coding: Claude Code works in a terminal or IDE, editing files and running commands.

These features make Claude a common choice as the reasoning engine in AI agents, where the model plans steps, calls tools, reads results and continues until a task is complete. Reliability in such loops depends as much on tool design and guardrails as on the model itself.

Claude compared with other assistants

Claude competes with other frontier assistant families that differ in openness, modality coverage and ecosystem. The comparison below is deliberately qualitative, because benchmark rankings shift with every release.

FamilyDeveloperWeightsNotable emphasis
ClaudeAnthropicClosedSafety research, coding, long context
GPT-5OpenAIClosedBroad consumer reach, multimodal output
GeminiGoogleClosedNative multimodality, Google services
LlamaMetaOpen weightsSelf-hosting and customization
MistralMistral AIMixedEfficient models, European hosting
Claude and other model families in general terms

Choosing between them is usually a matter of task-specific evaluation, data-handling requirements and price per token. Organizations that need on-premises deployment typically pick open-weight models, while those that want managed frontier capability compare the closed families on their own test sets.

Limitations and responsible use

Like every language model, Claude can produce confident but false statements, known as hallucinations, especially about niche facts, recent events after its training cutoff and precise citations. Its outputs therefore need verification proportional to the stakes.

RiskWhy it occursRecommended control
Hallucinated factsPrediction fills gaps plausiblyProvide sources, require quotes, verify
Outdated knowledgeFixed training cutoffSupply current data through retrieval or tools
Over-refusalConservative safety trainingGive legitimate context in the prompt
Prompt injectionUntrusted text in documents or web pagesSeparate data from instructions, limit permissions
Unchecked agent actionsAutonomous tool loopsHuman approval for irreversible steps
Practical risks and recommended controls

Anthropic publishes a Responsible Scaling Policy that ties stronger safeguards to higher capability levels. For deployers, the decisive practice is simpler: keep a human accountable for consequential decisions, and never send sensitive data to a provider without checking its retention terms.

The simple explanation

Claude is an AI assistant you can talk to in ordinary language. You type a question, paste a document or upload a picture, and it answers, summarizes, writes or helps with code.

It learned by reading enormous amounts of text and was then trained to be helpful and to follow a written set of values. It is a bit like a very well-read assistant who works quickly but sometimes misremembers details, so important answers should be double-checked.

How it is used in practice

A mid-sized software company keeps a backlog of about 300 small bug reports that its engineers rarely have time for. The team connects Claude Code to its repository and continuous integration pipeline, granting permission to edit files and run tests but not to merge changes.

For each report, the agent reads the relevant code, reproduces the failure with a new test, proposes a fix and opens a pull request with an explanation. An engineer reviews every pull request before it is merged, and changes touching authentication or billing require a second reviewer.

Over several weeks, a large share of the routine reports are closed through reviewed agent-written fixes, while engineers focus on design work. The team found that clear task descriptions and good test coverage mattered most for success, and that the agent struggled when bugs depended on undocumented production behavior.