One important caveat: the provided sources do not publish a separate benchmark declaring “the number-one task for 1M context.” The stronger claim is that large-codebase engineering and agentic coding are the clearest best-fit use cases based on Anthropic’s own product positioning and API documentation .

Why large codebases benefit most

In real software projects, the relevant evidence for a bug or refactor rarely lives in a single function. A serious change may touch multiple modules, tests, configuration files, schemas, build scripts, documentation and previous tool outputs.

That is exactly the kind of setting where a bigger context window matters. If the files are genuinely relevant, Opus 4.7 can keep more of them in the same working session instead of relying on aggressive summarization or repeated retrieval. This lines up with Claude’s documentation around complex codebases and extensive codebases .

The advantage becomes even clearer for agentic coding. In a multi-step workflow, the model may read files, call tools, inspect test failures, patch code, run another check and revise its plan. Claude’s context-window documentation notes that input and output tokens in configurations involving thinking and tool use affect the context-window limit . Anthropic’s migration guide also lists tool use, the Files API, prompt caching and memory among Opus 4.7’s supported features .

In short: the longer the session and the more relevant intermediate evidence there is, the more valuable the 1M-token window becomes.

Best-fit tasks for 1M context

Limits people often misread

1M context is not 1M output

Anthropic’s migration guide lists a 1M-token context window for Opus 4.7, but the maximum output is 128k tokens . If the goal is to generate a very long report, book-length draft or huge code file, the output cap still matters.

Token accounting still matters

“No long-context premium” does not mean “ignore token budgets.” Anthropic says Opus 4.7’s new tokenizer may use roughly 1x to 1.35x as many tokens as earlier models depending on the content, and the count_tokens endpoint may return different counts for Opus 4.7 than for Opus 4.6 .

For long workflows, it is worth rechecking token counts instead of assuming an old prompt will fit—or cost—the same way.

A bigger window is not a reason to dump everything in

The 1M-token window lets you include more relevant material. It does not remove the need to choose files, logs, documents and retrieved passages carefully.

That is especially true when tools are involved, because input, output and tool-related context still contribute to the context-window limit . For RAG-style workflows, the better pattern is usually to include more well-selected evidence, not to push an unfiltered document store into one prompt; discussion of 1M-token context often frames it around RAG pipeline design and long-running agent tasks .

A quick decision checklist

Use Claude Opus 4.7’s 1M context window when at least one of these is true:

1. The model needs to read, compare or modify many related parts of a large codebase, especially across modules, tests or technical documentation .
2. The workflow is agentic: it calls tools, reads files, processes logs or test output, and iterates through several rounds .
3. The task involves long documents, PDFs or multiple selected files that need to be reasoned over together .
4. Summarizing the task history would risk losing details that matter to the final decision.

Use something simpler when the request is short, the task is self-contained, or the model only needs one small file. A million-token context window is best understood as a bigger desk for serious codebase, document and agent work—not the default answer to every prompt.

One important caveat: the provided sources do not publish a separate benchmark declaring “the number-one task for 1M context.” The stronger claim is that large-codebase engineering and agentic coding are the clearest best-fit use cases based on Anthropic’s own product positioning and API documentation .

Why large codebases benefit most

In real software projects, the relevant evidence for a bug or refactor rarely lives in a single function. A serious change may touch multiple modules, tests, configuration files, schemas, build scripts, documentation and previous tool outputs.

That is exactly the kind of setting where a bigger context window matters. If the files are genuinely relevant, Opus 4.7 can keep more of them in the same working session instead of relying on aggressive summarization or repeated retrieval. This lines up with Claude’s documentation around complex codebases and extensive codebases .

The advantage becomes even clearer for agentic coding. In a multi-step workflow, the model may read files, call tools, inspect test failures, patch code, run another check and revise its plan. Claude’s context-window documentation notes that input and output tokens in configurations involving thinking and tool use affect the context-window limit . Anthropic’s migration guide also lists tool use, the Files API, prompt caching and memory among Opus 4.7’s supported features .

In short: the longer the session and the more relevant intermediate evidence there is, the more valuable the 1M-token window becomes.

Best-fit tasks for 1M context

Limits people often misread

1M context is not 1M output

Anthropic’s migration guide lists a 1M-token context window for Opus 4.7, but the maximum output is 128k tokens . If the goal is to generate a very long report, book-length draft or huge code file, the output cap still matters.

Token accounting still matters

“No long-context premium” does not mean “ignore token budgets.” Anthropic says Opus 4.7’s new tokenizer may use roughly 1x to 1.35x as many tokens as earlier models depending on the content, and the count_tokens endpoint may return different counts for Opus 4.7 than for Opus 4.6 .

For long workflows, it is worth rechecking token counts instead of assuming an old prompt will fit—or cost—the same way.

A bigger window is not a reason to dump everything in

The 1M-token window lets you include more relevant material. It does not remove the need to choose files, logs, documents and retrieved passages carefully.

That is especially true when tools are involved, because input, output and tool-related context still contribute to the context-window limit . For RAG-style workflows, the better pattern is usually to include more well-selected evidence, not to push an unfiltered document store into one prompt; discussion of 1M-token context often frames it around RAG pipeline design and long-running agent tasks .

A quick decision checklist

Use Claude Opus 4.7’s 1M context window when at least one of these is true:

1. The model needs to read, compare or modify many related parts of a large codebase, especially across modules, tests or technical documentation .
2. The workflow is agentic: it calls tools, reads files, processes logs or test output, and iterates through several rounds .
3. The task involves long documents, PDFs or multiple selected files that need to be reasoned over together .
4. Summarizing the task history would risk losing details that matter to the final decision.

Use something simpler when the request is short, the task is self-contained, or the model only needs one small file. A million-token context window is best understood as a bigger desk for serious codebase, document and agent work—not the default answer to every prompt.