My new terminal daily driver: Supacode for macOS

You are helping me turn one specific YouTube video into real, durable learning.

Source video:
- Title: My new terminal daily driver: Supacode for macOS
- URL: https://www.youtube.com/watch?v=98CM_Yq867c
- Topic: Interfaces + Open Design
- My current learning frame: Install Supacode (or a comparable libghostty session manager), migrate your five active projects into its sidebar, enable hooks for one agent harness, and run a two-branch worktree experiment to see whether it beats your current tab-per-session workflow.
- Why this matters: New playlist item from Bret Fisher; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:53 / Evidence 1: "harnesses, agent harnesses like cloud code and codeex and co-pilot and all the other wonderful ones, the pies, the open codes, the Hermes, the open clause, these are all primarily right now at least TUIs first or TUI..."
- 5:40 / Evidence 2: "So there's many agents that you can put into cloud code. They all do a little bit different things. And to me, an agent is four things. It is the combination of permissions of what it can do,..."
- 7:45 / Evidence 3: "different sessions. But it did have a web preview which is pretty slick although I don't really tend to use that. But somewhere in the early first quarter of this year I learned about Superode and Superode is..."
- 9:53 / Evidence 4: "is a new layer of abstraction on top of that. So for each one of these projects, and it doesn't have to be a Git project, which is key. There's lots of other apps out there that use..."
- 15:32 / Evidence 5: "running in the app is managing the app itself. And the thing that I use it the most for is when I'm already in an agent and I just tell it, hey, could you open up this directory..."
- 18:13 / Evidence 6: "that it does that. So when I'm ever in a cloud code session, it rises to the top so I can focus the top of the list rather than all the other projects that are maybe something that..."
- 20:30 / Evidence 7: "recently learned about. It's a pretty sexy looking app. I admit it looks really good and it's only for Open Code. So, if you're someone who's into the Open Code, I've got videos on this channel about Open..."

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 UI critique sheet for judging whether an AI interface improves control.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Intent -> Canvas -> Artifact -> Preview -> Feedback -> Iteration
   - 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 "My new terminal daily driver: Supacode for macOS", not a generic Interfaces + Open Design 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.