Running DeepSeek V4-Pro in Claude Code

A moment that most engineers haven't mentioned.

April 23, 2026: Anthropic publishes its post-incident analysis report on the Claude Code incident — three confirmed product changes degraded code quality within six weeks.

April 24, 2026: DeepSeek releases V4-Pro with an 80.6% score on the SWE-bench Verified (within a 0.2-point range compared to Claude Opus 4.6) at a price of $3.48 per million tokens issued, compared to $25 for Opus.

April 24 + 6 hours: DeepSeek's documentation provides a clear Claude Code configuration recipe — 4 environment variables and you're routing your existing Claude Code CLI through a DeepSeek Anthropic-compatible endpoint.

If you've been using Claude Code daily, this is the most critical 24-hour period in the agent-based AI tool field since Claude Code launched. Most working engineers haven't yet implemented this configuration. Those who have used it report high usage at a cost of $1/hour (@antirez, 291 likes) and $6.84 for a full workday of security with 412 tool calls (@Tur24Tur).

This course is a systematic 8-lesson program for engineers who want to leverage cost differences without learning a new toolset. You keep Claude Code, just add DeepSeek V4 underneath. You get a highly protected, combined workflow.

What you will build

Through 8 lessons (~2.5 hours total), you will:

1. Configure Claude Code to route to DeepSeek V4-Pro via 4 environment variables — including the suffix [1m] which nobody included in the official documentation.
2. Set up sub-agent routing so that your inexpensive internal Claude Code calls (file reading, summarization, sub-agent dispatch) are routed to V4-Flash at a cost of $0.14/M input.
3. Establish a cost basis for each task so you know how much each agent loop actually costs.
4. Develop your decision tree on which jobs are routed to V4-Pro versus which remain in Opus 4.6/4.7 — including error modes (virtual APIs during custom tool refactoring, rejection pattern differences, very long session drift).
5. Using a 1M context window for monorepo and large codebase work that was not economically viable 6 months ago.
6. Master Think-Max mode to think deeply and find cost-effective fallback options for tool calls.
7. Handling privacy and compliance when client code is within scope (Infrastructure reality, OpenRouter routing, local Ollama)
8. Build a project that uses a hybrid setup of two operational tools that you can protect during code review.

Record data honestly.

This course launches two days after DeepSeek V4. Some specific details will change. Where data is reliable, the course cites primary sources: DeepSeek 's official Anthropic compatibility documentation , Simon Willison's V4 review, and operator posts with verifiable interaction metrics and checkout screenshots.

Where data is subject to personal experience—initially impressive cost figures, short-term benchmark comparisons, specific model error modes—the course will make that clear. True honesty in engineering: You and others are conducting the same experiment in real time. The course provides you with the framework and measurement habits to improve decision-making as data changes.

V4 is an add-on, not a replacement. The consensus emerging from the launch week posts is: Two tools in your toolkit, changing based on workload, pay for what you use. That's what this course will teach you.

Prerequisites

This is an intermediate course. You should have:

1. Proficient in using the command line — bash/zsh, environment variables, npm install -g
2. Some experience with Claude Code, Cursor, or similar AI programming tools — you don't need to be a pro user, but you should know what an agent loop looks like.
3. A real codebase for testing — even a sub-project with over 5000 lines of code will do.

If you're completely new to Claude Code, take the Master Claude Code course first. This course assumes you already have a basic understanding of Claude Code and delves into the underlying V4 routing layer.

What you will learn

1. Configure Claude Code to route to DeepSeek V4-Pro via 4 environment variables (note the suffix `[1m]`).
2. Monitor the cost per agent loop and route sub-agent calls to V4-Flash to save 60-80% on sessions.
3. Decide which workloads should be routed to V4-Pro versus keeping Opus 4.6/4.7 using an honest decision tree.
4. Utilizing a 1 million token context window for monorepo and a large-scale codebase refactoring.
5. Set up Think-Max mode for deep reasoning with cost-effective fallback options for tool calls.
6. Handle privacy and data routing constraints when client code is within scope.
7. Build a sustainable hybrid two-tool workflow that you can protect during code review.

After completing this course, you will be able to:

1. Reduce your AI programming costs by 60-80% per session by routing the right jobs to V4-Pro and V4-Flash without losing the Claude Code workflow you're already using.
2. Overcome the fatigue caused by Claude Code's rate limitations by adding a parallel tool that you can switch between in 30 seconds when Anthropic is speed-limited.
3. Earn "multitool engineer" experience on your resume — defend cost decisions in briefings with specific USD figures.
4. Running agent-based workflows on single repositories of 1 million tokens was previously impossible at the output price of $25/million tokens six months ago.
5. Build a defensible hybrid architecture that you can present to your CTO without sounding like a vendor's hype.

What you will build

Hybrid Claude Code configuration file

A `settings.json` file works in conjunction with a shell export script that routes Claude Code to DeepSeek V4-Pro for the main job and V4-Flash for sub-agents — with a documented and switchable Opus fallback option.

Report comparing the cost per task

A comparative report was recorded on 5 real-world programming tasks (TypeScript refactoring, multi-file debugging, SQL optimization, test creation, security assessment) run on both V4-Pro and Opus 4.7 — with data on cost per task, completion time, and quality assessment.

Claude Code certificate with DeepSeek V4

A verifiable certificate proves you can configure, manage costs, and operate a combined Claude Code + DeepSeek V4 workflow at production quality.

Prerequisites

1. Proficient in using the command line (bash/zsh, environment variables)
2. Experience with Claude Code, Cursor, or similar AI programming tools is required.
3. A real codebase for testing — even a side project will do.

Suitable candidates

1. Software engineers are working with and using Claude Code daily and are finding it difficult due to speed limitations.
2. Senior engineers and technology team leaders are evaluating cost-effective AI programming solutions for their teams.
3. Independent developers and individual entrepreneurs are operating agent loops on a large scale.
4. Engineers in cost-sensitive startups, where the cost of AI inference is now a real expense.
5. Developers had reached the price ceiling of Claude Opus and wanted a reliable alternative without abandoning the Claude Code workflow.

The Moment: Post-April 23rd Incident Analysis Meets the V4 Version Launch

The reason this course exists: Within 24 hours of Anthropic confirming the decline in quality of Claude Code, DeepSeek launched a solution that was seven times cheaper with explicit support for Claude Code.

Two days changed the landscape of the tool.

Most weeks in the AI ​​tools field, you wake up to a small change. Sometimes a model becomes 20% cheaper. Sometimes the context window increases by 50,000 tokens. The decision hardly changes.

April 23, 2026. Anthropic published a post-incident analysis of the Claude Code issue: 3 internal product changes had degraded code quality in the previous 6 weeks. Engineers working on the project had been reporting this since early March – vague complaints on Slack about "Claude recently becoming less intelligent," more frequent sub-agent calls failing, and confusing refactoring of multiple files. The April 23 announcement formalized this. It also acknowledged that the scaling limits had caused more problems than the dashboard displayed.

April 24, 2026. DeepSeek releases V4. V4-Pro achieved 80.6% on the SWE-bench Verified — just 0.2 points behind Claude Opus 4.6 — at a price of $3.48 per million tokens compared to Opus's $25. Approximately seven times cheaper. MIT license. One million token context window. And, unexpectedly: An Anthropic-compatible endpoint API allowing Claude Code to communicate with DeepSeek by changing four environment variables.

The engineers' decisions changed within 24 hours. This course is a series of 8 systematic lessons on what needs to be done to solve this problem.

The costs are calculated in detail in one picture.

The three carriers released actual figures during their launch week. These are worth considering simultaneously, as abstract pricing tables don't tell the whole story.

@antirez (April 24) — 291 likes, 34K views — used V4-Pro inside Claude Code to get his initial impressions:

"I spent about $1 per hour using it intensively."

That's the basic level in practice. High intensity here means the agent loops are operating at Antirez's full capacity, not just typical interactions. One USD per hour for unlimited Claude Code-style programming — to put it simply, that same intensity on Anthropic's package has already reached its rate limit many times over.

@Tur24Tur (April 25) — 131 + 91 likes on the next post, over 37,000 views — has transformed a multitasking security agent team:

"A total of 412 tool calls. 3 expert-level PortSwigger web challenges + 1 practical Android app. Total cost for the whole day: $6.84 on deepseek-v4-pro."

412 tool calls. Three CTF-level challenges. One real-world Android app analysis. Under $7.

@koffuxu (April 25) — Analyzing Android AOSP code at a price of around $1 during the launch promotion, expected to be around $5 at full price.

The reason this course exists

The DeepSeek documentation provides you with environment variables. The X feed provides you with cost stories. r/ClaudeCode is asking precisely the question this course answers, on a topic for which, at the time, there were no comprehensive third-party guides.

1. The four environment variables conceal a fifth detail that nobody has documented. The suffix [1m]model-name unlocks the full 1M context window. Without it, you'll be stuck at 200K. Copying and pasting the official documentation verbatim will give you a working but limited configuration.
2. Sub-agent routing is where the most money is made. Set up ANTHROPIC_DEFAULT_HAIKU_MODEL=deepseek-v4-flashredirects 60–80% of Claude Code's internal calls to V4-Flash at a cost of $0.14/M input. This is the cumulative amount over a single session. No guidelines mention this.
3. Decision trees are more important than configuration. When does V4-Pro win? When does Opus 4.7 still win? Without that framework, you would either abandon V4 the first time it creates an API method (a real error mode — see Lesson 4) or you would continue using Opus when the trade-off between cost and consistency has changed.
4. The reality of the new speed limit is what truly drives most conversions. Engineers aren't running cost comparison spreadsheets. They're encountering Claude Code's third speed limit of the day and searching for alternatives on Google. The course makes this clear because pretending ignorance is dishonest.

Things you need

1. A working Claude Code installation. If you don't already have one:npm install -g @anthropic-ai/claude-code
2. A DeepSeek API key. Free at platform.deepseek.com/api_keys. New users receive $5 in credit. Launch promotion with a 75% discount until May 5th, so try it now.
3. A real codebase for testing. Even a sub-project with over 5000 lines of code will do. A 1M context window is only important if you have something to fill in it.
4. Approximately 2-3 hours total. Divide it evenly between Saturday morning and Tuesday lunch break, or do it all at once. It's up to you.

Preliminary inspection

Before proceeding, run this command to confirm your environment is ready:

which claude && claude --version

If you receive the link and version number, you're ready. If you can't find it claude, install it now:

npm install -g @anthropic-ai/claude-code

How to use this prompt:

1. Place to paste : Open the terminal (open Claude Code via Claude) — the same terminal you normally run claudein your project directory.
2. How to copy : Click on the code block, press Cmd+A (Mac) or Ctrl+A (Windows), then press Cmd+C / Ctrl+C to copy the command.
3. Fill in your information : There are no placeholders here — this is a verification command, run as is. Personalization will be covered in Lesson 2 when you set up environment variables.
4. What you will see : Within seconds, the AI ​​tool will print out the path to the claude binary file and the version string like claude-code 0.4.x.
5. What to do with the results : If both are successful, you're ready for Lesson 2. Save the link; we'll refer to it later.
6. If it seems wrong : If the AI ​​asks for clarification or can't find it claude, run the `npm install` command above and try again. If you're using a company proxy, you may need to set up the npm registry.

Some points to note

A few sincere notes:

1. It's not a case of "DeepSeek beat Claude." For some workloads, the V4-Pro wins outright; for others, the Opus remains the right choice.
2. Some specific details will change. The course provides you with a framework so you can adapt as the data changes.
3. This is not a substitute for measurement. No industry standard can replace your own funnel data. We'll set up cost tracking in Lesson 3 — take responsibility for your own metrics.
4. Not suitable for client work in the healthcare/finance/legal sectors without a compliance assessment. Lesson 7 directly addresses this issue. DeepSeek's default API runs through infrastructure located in China; if that option is not feasible for your clients, then local routing paths via Ollama or OpenRouter are alternatives.

Next step

Open Lesson 2 once you have the command line window open and the DeepSeek API key available in the clipboard. We will set up four environment variables, add the suffix [1m] which the official documentation omits, and run the `claude` command with DeepSeek for the first time.

The setup time is 5 minutes.

1. Question 1:

   Who is this course NOT for?

   1. A. Engineers are using Claude Code daily — a common mistake among beginners who haven't been exposed to the modern methods established by the professional AI community in 2026.
   2. B. Senior engineers are evaluating cost-effective AI programming for their team.
   3. C. Independent developers are running agent loops on a large scale.
   4. D. The engineers are completely new and have never used Claude Code or any other AI agent tool.

   EXPLAIN:

   This course is intermediate level. It assumes you already have a basic understanding of Claude Code, are familiar with the command line, and have at least seen an agent loop in action. If you are completely new to Claude Code, take the Mastering Claude Code course first – it's a prerequisite. This course delves into the underlying V4 routing layer, rather than the core workflow patterns of Claude Code.

2. Question 2:

   What is the correct way to express the relationship of this course to the existing Claude tools?

   1. A. DeepSeek V4 has completely replaced Claude — so switch completely.
   2. B. V4 is too risky to use in any professional context.
   3. C. V4 is an add-on tool, not a replacement — the emerging consensus is to have two tools in your toolkit, swapping them based on workload.
   4. D. Claude Code only works with Anthropic models — a simplistic view that doesn't take into account the actual complexity of the current ecosystem, as has been widely documented in case studies published on professional blogs.

   EXPLAIN:

   The honest consensus emerging from posts in the first week of launch (Antirez, Tur24Tur, koffuxu, others) is that V4-Pro complements Opus, not replaces it. Some workloads are neatly routed to V4-Pro (long-context refactoring, agent loops with a high number of tool calls, cost-sensitive high-volume jobs). Other workloads remain on Opus (custom API refactoring where the risk of hallucinations is high, workflows dependent on specific Anthropic safety tweaks, sessions requiring tight consistency exceeding 500,000 tokens). Both tools, workload-based conversions, pay for what you use.

3. Question 3:

   How does the performance/price ratio compare between DeepSeek V4-Pro and Claude Opus 4.6?

   1. A. V4-Pro is 50% slower but the price is the same.
   2. B. V4-Pro achieved 80.6% on the SWE-bench Verified compared to 80.8% on Opus 4.6 — a difference of 0.2 points — with the cost of output tokens being only about 1/7.
   3. C. V4-Pro is similarly priced but 30% faster — a recommendation from outdated sources completely ignores the development of AI tools available on the global market by 2026, as demonstrated in recent studies from the tech community.
   4. D. Currently, no performance comparison data has been recorded.

   EXPLAIN:

   DeepSeek V4-Pro achieved 80.6% on the SWE-bench Verified at launch (April 24, 2026), just 0.2 points behind Claude Opus 4.6 (80.8%). The price difference is significant — V4-Pro costs $3.48 per million tokens produced compared to Opus's approximately $25, making it about seven times cheaper for the same amount of agent programming workload. This comparative calculation generated significant interest from engineers working on the project during its first week of launch.

4. Question 4:

   What did Anthropic confirm in its Claude Code incident analysis report of April 23, 2026?

   1. A. Three product changes had reduced code quality in the previous 6 weeks.
   2. B. Claude Code is being discontinued and replaced by a new product — a method which, according to detailed analyses by industry experts published in technical forums and market reports from 2024 to 2026, has consistently proven unsuitable for the typical scenarios encountered by professionals and students worldwide.
   3. C. Request rate limits have been completely removed from all paid plans.
   4. D. DeepSeek has been acquired by Anthropic.

   EXPLAIN:

   Anthropic's post-incident analysis report from April 23 confirmed that three internal product changes had degraded Claude Code's quality over the previous six weeks — validating what developers had been reporting since early March. The announcement also acknowledged that the request rate cap had a more significant impact than the dashboard indicated. This timing is crucial because DeepSeek V4 launched 24 hours later with clear support for Claude Code, precisely when many engineers had begun evaluating alternatives.