I Built an AI Assistant That Doesn't Need the Internet
This video documents building the 'Think Slab' — a portable, battery-powered offline AI computer made from a Raspberry Pi, a $35 touchscreen, and a compact PiSugar battery — motivated by the fact that every mainstream chatbot dies without internet because inference happens in remote data centers.
Built By West14 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 Built By West; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to scope and build a small offline AI device by picking components against explicit constraints (size, power, cost) and honestly evaluating the performance trade-offs of running a local model on $50 hardware.
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.
2,213 cleaned transcript words reviewed across 670 timed caption segments.
Thesis
I Built an AI Assistant That Doesn't Need the Internet teaches a practical creative automation move: This video documents building the 'Think Slab' — a portable, battery-powered offline AI computer made from a Raspberry Pi, a $35 touchscreen, and a compact PiSugar battery — motivated by the fact that every mainstream chatbot dies without internet because inference happens in remote data centers.
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:18
Chatbots' shared weakness
“>> This is what I'm calling the Think Slab. It's a fully portable battery-powered computer designed to run AI models. It's been my passion project for a while, so a lot of work has gone into creating it.”
Every AI chatbot you use shares one critical weakness: your phone can't run the model locally, so a data center performs 100 billion to over a trillion calculations per generated word — which means no Wi-Fi, no assistant, as the creator discovered mid-decision in a Walmart aisle. Explain in two sentences why your phone's chatbot fails offline, naming where the computation actually happens and roughly how much of it one word requires.
4:49
Design under constraints
“possible. I want to keep it smaller than an iPad, but not so small to the point where I can't use a touchscreen keyboard. Next, it needs to be simple. According to my favorite industrial designer, Dieter Rams,...”
The build combines a ~$60 Raspberry Pi, a $35 touchscreen (screen and input in one part, cutting cost and size), and a 20,000 mAh battery, guided by three constraints — compact, simple (Dieter Rams: 'good design is as little design as possible'), and reliable — and the layout deadlock was only broken by discovering PiSugar's tiny battery, which shrank the design by 50% despite a quarter of the capacity. For a project you're planning, write your three hard constraints first, then list one component swap (like the PiSugar battery) that would relax your biggest layout or cost blocker.
12:09
Honest performance audit
“not only increase longevity, but up the performance a lot. I've already looked into using those pre-made heat sinks and coolers with fans attached to them, but the way they were designed would require a larger case. Lastly,...”
Running Gemma 2 2B, the finished Slab processed a prompt in 2.6 seconds at 2.1 tokens/second and idled for 75 minutes with zero power optimization — and the creator's own improvement list is a template for iteration: hide the cables, shrink the case, cool below the 70°C plateau, and replace the stock Raspberry Pi OS with streamlined custom software. Write a four-line 'what could be improved' audit for your last project covering usability, size or performance, thermals or reliability, and software polish.
01
Brief
Start with this video's job: This video documents building the 'Think Slab' — a portable, battery-powered offline AI computer made from a Raspberry Pi, a $35 touchscreen, and a compact PiSugar battery — motivated by the fact that every mainstream chatbot dies without internet because inference happens in remote data centers. Treat "Brief" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:18, where the video says: “>> This is what I'm calling the Think Slab. It's a fully portable battery-powered computer designed to run AI models. It's been my passion project for a while, so a lot of work has gone into creating it.”
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:49, where the video says: “possible. I want to keep it smaller than an iPad, but not so small to the point where I can't use a touchscreen keyboard. Next, it needs to be simple. According to my favorite industrial designer, Dieter Rams,...”
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.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: This video documents building the 'Think Slab' — a portable, battery-powered offline AI computer made from a Raspberry Pi, a $35 touchscreen, and a compact PiSugar battery — motivated by the fact that every mainstream chatbot dies without internet because inference happens in remote data centers.
02
Explain the practical stakes without hype: New playlist item from Built By West; 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: I Built an AI Assistant That Doesn't Need the Internet
- URL: https://www.youtube.com/watch?v=RTtVIW36bd4
- Topic: Creative Automation
- My current learning frame: Spec your own minimal offline AI device on paper — pick a single-board computer, input method, and battery under a $150 budget, state three design constraints, and predict tokens-per-second and runtime before you buy anything.
- Why this matters: New playlist item from Built By West; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:18 / Evidence 1: ">> This is what I'm calling the Think Slab. It's a fully portable battery-powered computer designed to run AI models. It's been my passion project for a while, so a lot of work has gone into creating it."
- 2:14 / Evidence 2: "Earth has been condensed into an AI assistant that fits in the palm of your hand. The AI could help me choose. I poured every thought, every detail, every variable into my prompt, desperate for at least a..."
- 4:49 / Evidence 3: "possible. I want to keep it smaller than an iPad, but not so small to the point where I can't use a touchscreen keyboard. Next, it needs to be simple. According to my favorite industrial designer, Dieter Rams,..."
- 6:35 / Evidence 4: "by a Chinese company called PiSugar, was just what I needed. Even though it only carried a quarter of the power, it wasn't only dirt cheap, but it was also so compact that it could shrink my initial..."
- 8:49 / Evidence 5: "2B, which I found is the best balance of accuracy and speed for this setup. >> I should mention that the performance will not be considered good by today's standards. This is a $50 computer with no dedicated..."
- 10:32 / Evidence 6: "you guys need to know about me is that I procrastinate sometimes, a lot. So, I designed the Think Slab right here back in October of 2025. This was before I knew how to use GPIO and other..."
- 12:09 / Evidence 7: "not only increase longevity, but up the performance a lot. I've already looked into using those pre-made heat sinks and coolers with fans attached to them, but the way they were designed would require a larger case. Lastly,..."
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 "I Built an AI Assistant That Doesn't Need the Internet", 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.
Why does the video say every mainstream AI chatbot becomes useless without internet?
What discovery solved the layout deadlock in the Think Slab's design?
What performance did the finished Think Slab achieve running Gemma 2 2B?
Source shelf
Use the video as a doorway, then verify with primary sources.
