This video demos Planetator, a plan-mode extension for the Pi coding agent that surfaces the agent's generated plan in a visual UI where you annotate, correct assumptions, share a fully-local plan via URL, and approve before implementation.
Michael3 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 Michael; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: Running an annotate-correct-approve plan-review loop with a coding agent before letting it write any code, plus sharing plans without leaking data.
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.
476 cleaned transcript words reviewed across 132 timed caption segments.
Thesis
Pi Coding Agent - Visual Plan Mode Extension teaches a practical codex + claude workflows move: This video demos Planetator, a plan-mode extension for the Pi coding agent that surfaces the agent's generated plan in a visual UI where you annotate, correct assumptions, share a fully-local plan via URL, and approve before implementation.
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:00
Why visual plan mode
“planetator which creates a planning a plan mode like extension for pi and the plan mode works very similarly to cloud code except you benefit from the ability to annotate plans in the UI which will show you...”
Planetator mirrors Claude Code's plan mode (investigate repo, search, ask questions, write plan to file) but adds a UI layer so you can annotate and share the plan and its annotations instead of only reading terminal text. Run the planitator command to enter plan mode and have Pi generate a plan to a file, then compare the UI review experience against reviewing a plain terminal plan.
0:32
Annotate the plan
“repo, try to search and explore. It'll ask you questions and then it will write the plan to a file. Um, similar to clock code, there's a there's a question um answer period, but I'll just tell it...”
After the agent exits plan mode, hooks pipe the terminal plan into the UI where you correct its assumptions with targeted comments (e.g. 'use Flask not FastAPI', 'use UV not VM') and global comments or image annotations, then send feedback so the agent auto-revises and re-emits the plan for approval. Deliberately let Pi make a wrong assumption, then add a specific comment correcting it and confirm the next plan version reflects your annotation.
1:48
Share without leaking
“know, current implementations of the UI as well. Um, what we can now do is send that feedback. It'll auto close and the agent will correct the plan based on my feedback. It's a very simple UX. Once...”
Because Planetator is fully local, sharing works by compressing the plan into the URL itself (hosted on a static site you or the author can host); a recipient inherits the plan, adds their own annotations, and shares it back, all before you hit approve to let the agent implement. Copy a plan's share link, open it as a second reviewer, add an annotation, and trace how the round-trip ends in an approve-then-implement step.
01
Inspect
Start with this video's job: This video demos Planetator, a plan-mode extension for the Pi coding agent that surfaces the agent's generated plan in a visual UI where you annotate, correct assumptions, share a fully-local plan via URL, and approve before implementation. Treat "Inspect" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:00, where the video says: “planetator which creates a planning a plan mode like extension for pi and the plan mode works very similarly to cloud code except you benefit from the ability to annotate plans in the UI which will show you...”
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 0:32, where the video says: “repo, try to search and explore. It'll ask you questions and then it will write the plan to a file. Um, similar to clock code, there's a there's a question um answer period, but I'll just tell it...”
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 video demos Planetator, a plan-mode extension for the Pi coding agent that surfaces the agent's generated plan in a visual UI where you annotate, correct assumptions, share a fully-local plan via URL, and approve before implementation.
02
Explain the practical stakes without hype: New playlist item from Michael; 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: Pi Coding Agent - Visual Plan Mode Extension
- URL: https://www.youtube.com/watch?v=XqFun9XCXPw
- Topic: Codex + Claude Workflows
- My current learning frame: Drive Planetator through one full loop on a small real repo: enter plan mode, annotate at least two corrected assumptions, share the URL for outside feedback, then approve and let Pi implement.
- Why this matters: New playlist item from Michael; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:00 / Evidence 1: "planetator which creates a planning a plan mode like extension for pi and the plan mode works very similarly to cloud code except you benefit from the ability to annotate plans in the UI which will show you..."
- 0:32 / Evidence 2: "repo, try to search and explore. It'll ask you questions and then it will write the plan to a file. Um, similar to clock code, there's a there's a question um answer period, but I'll just tell it..."
- 1:48 / Evidence 3: "know, current implementations of the UI as well. Um, what we can now do is send that feedback. It'll auto close and the agent will correct the plan based on my feedback. It's a very simple UX. Once..."
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 "Pi Coding Agent - Visual Plan Mode Extension", 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.
Planetator's plan-generation flow mirrors Claude Code's plan mode (investigate repo, search, ask questions, write the plan to a file). What single capability does Planetator add on top that the plain terminal plan-mode lacks?
After the agent exits plan mode, how does Planetator get the plan into the UI for review, and what three kinds of feedback can you attach before sending it back to the agent?
Planetator is described as a completely local app, yet it supports sharing a plan privately. What is the specific mechanism it uses to share without leaking data, and what can a recipient do with the shared plan?
Source shelf
Use the video as a doorway, then verify with primary sources.
