Creative Automation / Foundation

Claude Code + Unsloth API -- LLM Finetuning Setup (100% FREE)

This video walks through pointing Claude Code at Unsloth's OpenAI-compatible API endpoint so it runs a self-hosted Qwen3 GGUF model (served via Unsloth Studio on a RunPod GPU) instead of Anthropic's models.

Prompt Engineer9 minTranscript found

Quick learning frame

Read this before watching.

Creative automation uses agents to accelerate production while keeping human taste in story, pacing, selection, and critique.

New playlist item from Prompt Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Skill you build: Configuring Claude Code to drive a locally-served open LLM by spinning up Unsloth Studio on a rented GPU and wiring it through three environment variables.

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.

01Brief
02Source
03Generation
04Selection
05Edit
06Taste Review

Deep lesson

Turn this video into working knowledge.

1,714 cleaned transcript words reviewed across 450 timed caption segments.

Thesis

Claude Code + Unsloth API -- LLM Finetuning Setup (100% FREE) teaches a practical creative automation move: This video walks through pointing Claude Code at Unsloth's OpenAI-compatible API endpoint so it runs a self-hosted Qwen3 GGUF model (served via Unsloth Studio on a RunPod GPU) instead of Anthropic's models.

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:13

Swap the backend

β€œlet's go ahead and do this. So for this entire procedure, what I'm going to follow is this anslot.ai docs basic API. So how to use as an API endpoint? So now you can use local LLMs with...”

Claude Code is not locked to Anthropic models; because Unsloth exposes an OpenAI-compatible API endpoint, the same client can be redirected to a self-hosted model with no code changes. Note that the swap happens purely at the API/endpoint layer, then locate Unsloth's 'basic API' docs the presenter follows to confirm the compatibility claim.

4:25

Serve the model

β€œand you can go to the API section here and then you can see that once you create an API you can use these APIs on your local systems or anywhere you want. You can use curl and...”

You provision a GPU (here an RTX Pro 4500 on RunPod with exported ports 8005/8006), install Unsloth via the curl script which sets up UV and Torch, launch Unsloth Studio on port 8005, and download a GGUF model like Qwen3 (UD-Q4_K_XL, ~21GB). Write out the exact sequence: deploy GPU, expose ports, run the install curl, start unsloth studio on your chosen port, then pull a GGUF quant in the web UI.

7:11

Wire the env vars

β€œcan go ahead and use this API on your local system as well. I mean you can run cloud code on your local system as well. just set the environment variables that we have seen here. Another thing...”

Connecting Claude Code requires creating an Unsloth API token and setting three environment variables: the Anthropic base URL (the Unsloth endpoint ID), the auth token, and the model name, after which 'claude' and /model select the unsloth Qwen3.5 model. List the three env vars (base URL, token, model) and practice editing settings.json to tune speed as shown, so you can reproduce the connection on your own machine.

01

Brief

Start with this video's job: This video walks through pointing Claude Code at Unsloth's OpenAI-compatible API endpoint so it runs a self-hosted Qwen3 GGUF model (served via Unsloth Studio on a RunPod GPU) instead of Anthropic's models. Treat "Brief" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:13, where the video says: β€œlet's go ahead and do this. So for this entire procedure, what I'm going to follow is this anslot.ai docs basic API. So how to use as an API endpoint? So now you can use local LLMs with...”

02

Source

Use "Source" to locate the part of the creative automation workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 4:25, where the video says: β€œand you can go to the API section here and then you can see that once you create an API you can use these APIs on your local systems or anywhere you want. You can use curl and...”

03

Generation

Turn "Generation" into the reusable artifact for this lesson: A creative workflow board with critique criteria and review checkpoints. This is where watching becomes something you can inspect and reuse.

04

Selection

Use "Selection" 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

Edit

Use "Edit" 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

Taste Review

Use "Taste Review" 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 creative workflow board with critique criteria and review checkpoints..

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.

Transcript-derived moments

Use timestamps to study the actual video.

Quality check

Do not count this as learned until these are true.

01

State the transcript-backed claim in your own words: This video walks through pointing Claude Code at Unsloth's OpenAI-compatible API endpoint so it runs a self-hosted Qwen3 GGUF model (served via Unsloth Studio on a RunPod GPU) instead of Anthropic's models.

02

Explain the practical stakes without hype: New playlist item from Prompt Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.

03

Map the idea onto the Brief -> Source -> Generation -> Selection -> Edit -> Taste Review sequence and name the weakest link.

04

Produce the artifact and include the evidence that proves it: A creative workflow board with critique criteria and review checkpoints.

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: Claude Code + Unsloth API -- LLM Finetuning Setup (100% FREE)
- URL: https://www.youtube.com/watch?v=XujmGCiiviM
- Topic: Creative Automation
- My current learning frame: Provision a GPU pod, serve a Qwen3 GGUF through Unsloth Studio, and set the three environment variables so a /model command inside Claude Code lists and responds from your self-hosted Unsloth model.
- Why this matters: New playlist item from Prompt Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:13 / Evidence 1: "let's go ahead and do this. So for this entire procedure, what I'm going to follow is this anslot.ai docs basic API. So how to use as an API endpoint? So now you can use local LLMs with..."
- 2:53 / Evidence 2: "a Linux need to install UV package manager creating the Python 3.13 version installing torch. Basically getting everything ready here. So that's a simple command and for launching we need to write this. Now instead of the port..."
- 4:25 / Evidence 3: "and you can go to the API section here and then you can see that once you create an API you can use these APIs on your local systems or anywhere you want. You can use curl and..."
- 7:11 / Evidence 4: "can go ahead and use this API on your local system as well. I mean you can run cloud code on your local system as well. just set the environment variables that we have seen here. Another thing..."

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 creative workflow board with critique criteria and review checkpoints.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Brief -> Source -> Generation -> Selection -> Edit -> Taste Review
   - 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 "Claude Code + Unsloth API -- LLM Finetuning Setup (100% FREE)", not a generic Creative Automation 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.

Creative AI removes the need for taste.

It increases the need for taste because output volume explodes.

The best prompt is enough.

References, critique, iteration, and post-production matter just as much.

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 creative workflow board with critique criteria and review checkpoints..

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.

How is Claude Code pointed at Unsloth models instead of Anthropic's, and why does this require no code changes to the client?

Walk through the server-side sequence to serve a model with Unsloth as shown (GPU, ports, install, launch, model).

Which three environment variables must be set to connect Claude Code to the Unsloth endpoint, and what does each hold?

Source shelf

Use the video as a doorway, then verify with primary sources.

ReadingComfyUIwww.comfy.org/ReadingAffinityaffinity.serif.com/