Qwen 3.8 Max FREE in VS Code 🤯 (No API, No Subscription)
This walkthrough shows how to use Alibaba's newly launched Qwen 3.8 Max model directly inside VS Code through Qwen's official extension, no API key or external website required, then demonstrates it by generating a full image-to-PDF converter web app. It stresses that this is a browser-style chat panel inside the editor, not an agent mode.
AI For You6 minTranscript found
Quick learning frame
Read this before watching.
Coding-agent workflow is the loop of inspect, plan, edit, verify, summarize, and route the next task to the right tool.
New playlist item from AI For You; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to install and drive a frontier chat model from within VS Code via a vendor's official extension and turn a detailed plain-English spec into working single-file code you can copy out and run.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Inspect
02Plan
03Edit
04Verify
05Review
06Route
Deep lesson
Turn this video into working knowledge.
996 cleaned transcript words reviewed across 282 timed caption segments.
Thesis
Qwen 3.8 Max FREE in VS Code 🤯 (No API, No Subscription) teaches a practical codex + claude workflows move: This walkthrough shows how to use Alibaba's newly launched Qwen 3.8 Max model directly inside VS Code through Qwen's official extension, no API key or external website required, then demonstrates it by generating a full image-to-PDF converter web app. It stresses that this is a browser-style chat panel inside the editor, not an agent mode.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:31
Free frontier access
“will show you how you can use it inside the Visual Studio Code in officially way, not from any API or using any external website. During launching Coin, it will mention that with a massive 2.4 trillion parameters,...”
Alibaba released Qwen 3.8 Max (a ~2.4 trillion parameter model the vendor bills as near-frontier, second only to the top model) with a free preview at chat.qwen.ai; the point of the video is using it inside VS Code officially rather than through the browser, an API, or a third-party site. Open chat.qwen.ai and run the same coding prompt against Qwen 3.8 Max preview so you have a browser baseline before moving the workflow into your editor.
1:38
Install and log in
“form. You can use it inside Visual Studio Code like as browser form, not in agent mode, but it will be easy to use inside Visual Studio Code. You can use it in one tab here. Then how...”
Go to the Extensions panel, search for the official Qwen extension and install it; an 'open Qwen' entry then appears in the bottom-left corner, and on first use a popup asks you to log in with any email (or Facebook/Google/Alibaba auth) before you can pick Qwen 3.8 Max. Crucially it runs as a browser-style chat tab, not in agent mode. Install the official Qwen extension in VS Code, complete the email login, select Qwen 3.8 Max, and confirm the panel opens in a single tab.
4:30
Spec to running app
“here and import it here. This is the only way that you can get access Coin 3.8 max currently. There is no any way that you can use in authentic form. Currently, it will return nearly 1,300 line...”
Given a detailed one-shot brief (single HTML file, no backend, multi-image select, drag-and-drop, previews, per-image removal, auto A4 fit, portrait/landscape, generate/download PDF), Qwen 3.8 Max plans then emits roughly 1,300 lines in one HTML file; high traffic makes it slow to start, but the copied-and-run output works with hover effects, previews, mode switching, and PDF download. Write your own tightly-scoped single-file app brief with explicit constraints, paste it in, then copy the result into a file and run it to verify every listed requirement.
01
Inspect
Start with this video's job: This walkthrough shows how to use Alibaba's newly launched Qwen 3.8 Max model directly inside VS Code through Qwen's official extension, no API key or external website required, then demonstrates it by generating a full image-to-PDF converter web app. It stresses that this is a browser-style chat panel inside the editor, not an agent mode. Treat "Inspect" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:31, where the video says: “will show you how you can use it inside the Visual Studio Code in officially way, not from any API or using any external website. During launching Coin, it will mention that with a massive 2.4 trillion parameters,...”
02
Plan
Use "Plan" to locate the part of the codex + claude workflows workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 1:38, where the video says: “form. You can use it inside Visual Studio Code like as browser form, not in agent mode, but it will be easy to use inside Visual Studio Code. You can use it in one tab here. Then how...”
03
Edit
Turn "Edit" into the reusable artifact for this lesson: A routing matrix for when to use Codex, Claude, browser checks, or manual review. This is where watching becomes something you can inspect and reuse.
04
Verify
Use "Verify" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Review
Use "Review" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Route
Use "Route" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed work packet
Convert the video into a scoped task that includes the transcript claim, target workflow, acceptance criteria, and proof. The output should be a routing matrix for when to use codex, claude, browser checks, or manual review..
Example
Claim vs. demo brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the workflow.
Example
Teach-back module
Transform the lesson into a definition, a mechanism diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
Letting the prompt drift into generic advice that could apply to any video in the playlist.
Copying the tool setup without identifying the operating principle that transfers to your own stack.
Skipping the artifact, which means the learning never becomes operational or inspectable.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: This walkthrough shows how to use Alibaba's newly launched Qwen 3.8 Max model directly inside VS Code through Qwen's official extension, no API key or external website required, then demonstrates it by generating a full image-to-PDF converter web app. It stresses that this is a browser-style chat panel inside the editor, not an agent mode.
02
Explain the practical stakes without hype: New playlist item from AI For You; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Inspect -> Plan -> Edit -> Verify -> Review -> Route sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A routing matrix for when to use Codex, Claude, browser checks, or manual review.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: Qwen 3.8 Max FREE in VS Code 🤯 (No API, No Subscription)
- URL: https://www.youtube.com/watch?v=AIGwYLxelpw
- Topic: Codex + Claude Workflows
- My current learning frame: Install the official Qwen extension in VS Code, log in, and use Qwen 3.8 Max to build a single-file HTML utility from a precise constraint list, then copy the code out and run it to confirm each requirement works.
- Why this matters: New playlist item from AI For You; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:31 / Evidence 1: "will show you how you can use it inside the Visual Studio Code in officially way, not from any API or using any external website. During launching Coin, it will mention that with a massive 2.4 trillion parameters,..."
- 1:38 / Evidence 2: "form. You can use it inside Visual Studio Code like as browser form, not in agent mode, but it will be easy to use inside Visual Studio Code. You can use it in one tab here. Then how..."
- 4:30 / Evidence 3: "here and import it here. This is the only way that you can get access Coin 3.8 max currently. There is no any way that you can use in authentic form. Currently, it will return nearly 1,300 line..."
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable claims from the video. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A routing matrix for when to use Codex, Claude, browser checks, or manual review.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Inspect -> Plan -> Edit -> Verify -> Review -> Route
- 3 concrete examples that apply the video idea to real agentic work
- 2 failure modes the video helps prevent
- a checklist I can use the next time I run Codex or Claude
- one practical exercise with a clear done signal
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "Qwen 3.8 Max FREE in VS Code 🤯 (No API, No Subscription)", not a generic Codex + Claude Workflows essay.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- If evidence is weak, say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
One agent should do every task.
Different tools have different strengths. Routing is part of the workflow.
More context is always better.
Relevant context helps; stale context causes drift and cost.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a routing matrix for when to use codex, claude, browser checks, or manual review..
A reusable artifact with a done signal and one verification step.03
Teach-back card
Explain the lesson to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
Where can you access Qwen 3.8 Max for free in the browser, and what does this video demonstrate instead?
What are the steps to enable Qwen 3.8 Max in VS Code, and is it an agent?
What did Qwen 3.8 Max produce for the image-to-PDF converter task?
Source shelf
Use the video as a doorway, then verify with primary sources.
