claude-opus-4-6
Deep work
Complex architecture, long-horizon planning, and difficult reasoning.
Recorded chat entry
Claude models: Opus 5.5, Sonnet 5.5, and earlier versions.
Explore the Claude 5.5 names shown on Floatboat’s pricing page alongside earlier Opus, Sonnet, and Fable records. Check the client menu before treating a listed version as selectable.
Floatboat · Claude
Current model
Claude
What do you want to finish?
Review this architecturePlan a repository-wide refactorTrace this failure across files
Describe the outcome or add project files…
- Inventory scope
- Recorded routes + current pricing listings
- Access
- Main client picker
- Configured next family
- Claude 5 · 1M / 128k budget
- API key
- Not required
A deliberate collaborator for work with many dependencies.
Claude is strongest when the job benefits from understanding constraints before making broad changes. Opus leans into depth; Sonnet keeps that discipline with a faster everyday cadence.
Plans before broad action
Initiative
Useful when a change can affect several modules or decisions.
Long-horizon
Work span
Maintains intent across research, implementation, and revision.
Opus for depth, Sonnet for cadence
Best rhythm
Choose within the family instead of treating both as interchangeable.
Depth can add latency
Watch for
Routine edits rarely need the most deliberate option.
Pick depth or throughput without leaving the project.
The Claude lineup combines recorded chat routes with names added to Floatboat's public pricing list. Compare the entry and status attached to each item, then confirm the current client menu and plan before relying on a particular version.
claude-sonnet-4-6
Daily workhorse
High-performance coding and general agent execution.
Recorded chat entry
claude-opus-5 / claude-sonnet-5 / claude-fable-5
Capacity ready
Evaluation profiles with 1M context and 128k output budgets.
Configuration record
Claude Sonnet 5.5
Pricing-page listing
Named on the official pricing page. The older Sonnet 4.6 picker record does not establish which 5.5 entry is available to a particular account.
Listed on pricing page
Official pricing page · 2026-11-02
Claude Opus 5.5
Pricing-page listing
Listed alongside earlier Claude generations on Floatboat’s pricing page. Confirm the visible entry and plan eligibility before replacing an existing Opus workflow.
Listed on pricing page
Official pricing page · 2026-11-02
Use Cases for Claude Models
Cross-file refactors, architecture choices, and failure traces depend on relationships that isolated snippets cannot explain. Explore tasks that need preserved interfaces, explicit tradeoffs, and verification of the original behavior through an available Claude route.
Repository-wide refactor
A repository-wide refactor begins with the shared subsystem, its callers, and interfaces that must remain compatible. Trace those dependencies and bound the migration before editing. Deliver the cross-file changes with migration notes and test results so reviewers can check both the new implementation and the preserved contracts.
Architecture decision
An architecture choice should account for real constraints, downstream dependencies, and the migration budget. Compare candidate designs by their tradeoffs and failure consequences, keeping unverified assumptions visible. A useful decision record explains the selected direction and the risks the team still needs to address.
Cross-file failure trace
When a failure crosses module boundaries, start with symptoms, reproduction steps, and the relevant logs. Trace calls and state transitions to test a root-cause hypothesis before making a fix. Rerun the original failing path afterward and retain the evidence that connects the change to the observed problem.
Check implementation against a specification
A feature can look complete while missing a condition spread across several requirements. Supply the specification, changed files, and relevant tests, then map each expected behavior to implementation evidence. Review gaps and ambiguous interpretations separately so the result is a source-grounded implementation assessment, rather than a general judgment that the code seems reasonable.
Reasoning connected to the project, not isolated in a chat box.
Repository reasoning, code changes, and longer tasks depend on the files and rules supplied with them. Explore how Claude's recorded capabilities fit Floatboat's project workflow, with managed access kept distinct from evidence that a particular task has succeeded.
Complex reasoning
Opus 4.6 is the deliberate option for architecture and difficult multi-step decisions.
High-performance coding
Sonnet 4.6 is the everyday option for implementation and general agent work.
Long-running coherence
Keeps constraints in view while work moves from analysis to revision.
Managed access
Both live 4.6 models are selectable without a separate Anthropic API key.
Pick Claude by the cost of getting the reasoning wrong.
Choose Opus 4.6 when
- The task spans architecture, dependencies, and several rounds of execution.
- A weak early assumption would create expensive rework later.
- You need a careful technical plan before changing the project.
Choose Sonnet 4.6 or another route when
- The work is well-scoped and benefits from faster iteration.
- You are handling frequent everyday coding tasks.
- Very large mixed-media input is the main bottleneck; consider Gemini Pro.
Explore Other Model Families
Compare model families by the kind of work they support. Availability differs by model and entry point.
Claude FAQ
When should I choose Opus instead of Sonnet?
Choose Opus when reasoning depth and architectural consistency outweigh latency. Sonnet is the stronger default for everyday coding and agent work.
Is Claude Sonnet 4.6 good for coding?
Yes. Sonnet 4.6 is positioned as the high-performance daily model for coding, implementation, and general agent work.
What kind of work benefits most from Claude?
Claude is best suited to work that must preserve constraints across several steps, such as architecture decisions, repository-wide refactors, and cross-file failure analysis.
Is Claude Opus 4.6 better for complex reasoning?
Opus 4.6 is the deeper option for architecture, difficult reasoning, and long-horizon work where consistency matters more than response speed.
What are Claude Opus 5, Sonnet 5, and Fable 5?
They are evaluation and capacity profiles with configured 1M context and 128k output budgets. That is a configuration snapshot, not a live client inventory; the pricing page now also lists Opus 5 and Fable 5.
How should I test Claude on a long document review?
Choose a document with known cross-references and important exceptions. Ask for claims tied to passages, then check whether the review preserves those exceptions and distinguishes missing evidence from a negative finding.
Does the Claude 5.5 pricing listing establish client access?
The official pricing page names Opus 5.5 and Sonnet 5.5. That listing does not establish account-specific menu access or the exact model IDs; check the client before choosing a version.
Choose Opus depth or Sonnet pace for this project
Use Opus 4.6 for difficult architecture and Sonnet 4.6 for everyday coding or agent work, with the same project files in view.