Inkling: Why Thinky's Open Model May Change "Everything"
Thinking Machines' first open-weight model, Inkling, is examined as the biggest open-weight release from a Western lab, trained from scratch and multimodal from the ground up, then put through hands-on tests of its playground, web-generation, and coding output.
Prompt Engineering11 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 Engineering; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to evaluate a new open-weight model release by checking its licensing, architecture, and playground behavior firsthand rather than relying on headline benchmark claims alone.
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,774 cleaned transcript words reviewed across 598 timed caption segments.
Thesis
Inkling: Why Thinky's Open Model May Change "Everything" teaches a practical creative automation move: Thinking Machines' first open-weight model, Inkling, is examined as the biggest open-weight release from a Western lab, trained from scratch and multimodal from the ground up, then put through hands-on tests of its playground, web-generation, and coding output.
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
First Western Open Frontier
“the biggest model released from a Western lab by far. And it's built multimodal from the ground up. Now, so far when it comes to model releases, you can just divide them into two different parts. Western labs...”
Inkling is Thinking Machines' first open-weight release, licensed Apache 2.0 and trained fully from scratch with no reused architecture, multimodal from the ground up on text, image, and audio, making it by far the biggest open-weight model out of a Western lab and filling a gap where open weights had mostly come from Chinese labs and been text-first. Compare Inkling's Apache 2.0 licensing and from-scratch training claim to two other open-weight models you know of and note what's actually novel here.
5:54
Reasoning Effort in Practice
“its sources if the user ask it to. Right, so a relatively simple system prompt, but if you want to use it through the API, you need to follow this format. Okay, the model itself is extremely fast.”
Inkling is a reasoning model whose "thinking effort" setting materially changes output quality, and its playground exposes reasoning effort from none to extra high, a token cap of 256k (the full 1 million context isn't exposed), a web search toggle, and a system prompt whose capability list reveals that image, audio, and video inputs aren't yet enabled in the playground despite the model being trained multimodally. Run the same prompt at two different reasoning-effort settings in the Inkling playground and compare output quality and speed.
9:18
Fast but Formulaic
“design web pages in. And um I would say it definitely needs some work in terms of taste. Now, when it comes to coding, uh this is not state-of-the-art, but still it's a very reasonable and capable model.”
In testing, Inkling generated websites and a real-time ISS tracker quickly with visible reasoning traces and interleaved web search tool calls, but it kept defaulting to the same visual design template across unrelated prompts unless given explicit direction, and its API pricing runs toward the pricier side, with output costing close to $4.70 per token tier despite the model being downloadable and self-hostable. If you try Inkling for web generation, give it an explicit design reference up front rather than a generic prompt, then compare the result to its default template output.
01
Brief
Start with this video's job: Thinking Machines' first open-weight model, Inkling, is examined as the biggest open-weight release from a Western lab, trained from scratch and multimodal from the ground up, then put through hands-on tests of its playground, web-generation, and coding output. Treat "Brief" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:18, where the video says: “the biggest model released from a Western lab by far. And it's built multimodal from the ground up. Now, so far when it comes to model releases, you can just divide them into two different parts. Western labs...”
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 5:54, where the video says: “its sources if the user ask it to. Right, so a relatively simple system prompt, but if you want to use it through the API, you need to follow this format. Okay, the model itself is extremely fast.”
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: Thinking Machines' first open-weight model, Inkling, is examined as the biggest open-weight release from a Western lab, trained from scratch and multimodal from the ground up, then put through hands-on tests of its playground, web-generation, and coding output.
02
Explain the practical stakes without hype: New playlist item from Prompt Engineering; 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: Inkling: Why Thinky's Open Model May Change "Everything"
- URL: https://www.youtube.com/watch?v=IB53DUrnYgI
- Topic: Creative Automation
- My current learning frame: Try the free Inkling playground with a research-plus-build prompt, such as having it web-search a topic and generate a page about it, then rerun it with an explicit design reference to see whether it breaks from its default template.
- Why this matters: New playlist item from Prompt Engineering; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:18 / Evidence 1: "the biggest model released from a Western lab by far. And it's built multimodal from the ground up. Now, so far when it comes to model releases, you can just divide them into two different parts. Western labs..."
- 3:17 / Evidence 2: "Now, right now, self-evolution is a big hot area. So, in one of the studies, they asked the model itself to fine-tune itself using the Tinker framework. And right now, it's using the open code harness to actually..."
- 5:54 / Evidence 3: "its sources if the user ask it to. Right, so a relatively simple system prompt, but if you want to use it through the API, you need to follow this format. Okay, the model itself is extremely fast."
- 7:42 / Evidence 4: "just created. So, you actually have information about when this was released. We can click on the architecture. Shows that it's an MOE, although I think it could use some work. Capabilities, text, image, audio, and uh the..."
- 9:18 / Evidence 5: "design web pages in. And um I would say it definitely needs some work in terms of taste. Now, when it comes to coding, uh this is not state-of-the-art, but still it's a very reasonable and capable model."
- 10:55 / Evidence 6: "because we have yet another option when it comes to Frontier Labs. And as I said, this is just the first iteration of the model. The next ones, hopefully, are going to be much more stronger. Especially if..."
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 "Inkling: Why Thinky's Open Model May Change "Everything"", 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.
What makes Inkling notable as an open-weight release, according to the video?
What does Inkling's system prompt reveal about its multimodal capabilities in the playground?
What recurring issue did the presenter notice when asking Inkling to design websites for different prompts?
Source shelf
Use the video as a doorway, then verify with primary sources.
