Interfaces + Open Design / Foundation

The new Hermes Agent update has me speechless....

Alex Finn walks through eight major Hermes Agent updates — native iMessage support via Photon, automatic background sub-agents with a live agent tree, an Unreal Engine 5.8 MCP for game building, desktop app multitasking, a profile builder, a skills hub, self-improving skill edits, and rich Telegram formatting — with setup prompts for each.

Alex Finn14 minTranscript found

Quick learning frame

Read this before watching.

AI-native interfaces are control surfaces for intent, artifacts, context, preview, inspection, and iteration.

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

Skill you build: The ability to configure a personal AI agent stack across channels and profiles — choosing the right interface (iMessage, Telegram, desktop) per context, delegating long tasks to background sub-agents, and safely sourcing or customizing skills.

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.

01Intent
02Canvas
03Artifact
04Preview
05Feedback
06Iteration

Deep lesson

Turn this video into working knowledge.

2,753 cleaned transcript words reviewed across 766 timed caption segments.

Thesis

The new Hermes Agent update has me speechless.... teaches a practical interfaces + open design move: Alex Finn walks through eight major Hermes Agent updates — native iMessage support via Photon, automatic background sub-agents with a live agent tree, an Unreal Engine 5.8 MCP for game building, desktop app multitasking, a profile builder, a skills hub, self-improving skill edits, and rich Telegram formatting — with setup prompts for each.

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.

1:21

iMessage as agent channel

“file around. Go on my DGX Spark and install this local model." It'll do that for me. And as you can see, boom, a full, nicely formatted investor report on Micron right there. Shout out to me, invested...”

Hermes now works natively in iMessage through a free service called Photon that gives your agent its own phone number, and it stays connected to your computer so you can trigger browser actions, file moves, or even local model installs from your phone; Finn's split is iMessage for quick on-the-go messages, Telegram only when he needs threading for deep work, and the desktop app at his computer. Set up the integration by sending your agent the exact prompt from the video — 'Hook Hermes up to iMessage using Photon according to the best practices from the new update' — then pin the resulting contact and fire off one real task from your phone.

5:38

Background agents by default

“build in Unreal Engine. It is a very complex, big game engine, but now you can use your Hermes agent to actually build your games. While a lot of people build games using 3.js, which is fine. That's...”

Sub-agents that work in the background no longer need a manual flag — any sufficiently complex prompt automatically spawns them, so you can keep chatting (or add 'also include Nvidia' mid-task) instead of waiting hours in silence, and the new sub-agent tree shows every spawned agent and its tool calls, like Finn's five agents running 28 tool calls on investment research; right after, he shows the new Unreal Engine 5.8 MCP that lets Hermes build real 3D games for free. Give your agent one deliberately complex multi-part research task, then while it runs, open the sub-agent tree, count the active agents and tool calls, and send a follow-up message to confirm you can still chat.

11:55

Self-improving skills loop

“Hermes more prompts, more commands to do, and you will find that it updates and builds its skills a ton more. In number eight, Telegram just launched a whole bunch of new features for talking with agents, and...”

Hermes now constantly creates and patches its own skills with 'self-improvement reviews' — Finn's Unreal Engine MCP skill went from struggling to excellent just through repeated use — and the Telegram integration gained tables, bold formatting, and smoother streaming, so the agent can return a fully formatted stock table with prices and market caps in chat. Rather than downloading skills from the hub, try Finn's safety pattern: paste a skill.md into your agent and ask it to 'make your own version of this and make sure it's safe for us', then watch for self-improvement review messages as you use it.

01

Intent

Start with this video's job: Alex Finn walks through eight major Hermes Agent updates — native iMessage support via Photon, automatic background sub-agents with a live agent tree, an Unreal Engine 5.8 MCP for game building, desktop app multitasking, a profile builder, a skills hub, self-improving skill edits, and rich Telegram formatting — with setup prompts for each. Treat "Intent" as the outcome you are trying to make visible, not a topic label. Anchor it to 1:21, where the video says: “file around. Go on my DGX Spark and install this local model." It'll do that for me. And as you can see, boom, a full, nicely formatted investor report on Micron right there. Shout out to me, invested...”

02

Canvas

Use "Canvas" to locate the part of the interfaces + open design workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 5:38, where the video says: “build in Unreal Engine. It is a very complex, big game engine, but now you can use your Hermes agent to actually build your games. While a lot of people build games using 3.js, which is fine. That's...”

03

Artifact

Turn "Artifact" into the reusable artifact for this lesson: A UI critique sheet for judging whether an AI interface improves control. This is where watching becomes something you can inspect and reuse.

04

Preview

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

Feedback

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

Iteration

Use "Iteration" 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 ui critique sheet for judging whether an ai interface improves control..

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: Alex Finn walks through eight major Hermes Agent updates — native iMessage support via Photon, automatic background sub-agents with a live agent tree, an Unreal Engine 5.8 MCP for game building, desktop app multitasking, a profile builder, a skills hub, self-improving skill edits, and rich Telegram formatting — with setup prompts for each.

02

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

03

Map the idea onto the Intent -> Canvas -> Artifact -> Preview -> Feedback -> Iteration sequence and name the weakest link.

04

Produce the artifact and include the evidence that proves it: A UI critique sheet for judging whether an AI interface improves control.

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: The new Hermes Agent update has me speechless....
- URL: https://www.youtube.com/watch?v=bQ1LCFrwj08
- Topic: Interfaces + Open Design
- My current learning frame: Build a two-profile Hermes setup from the dashboard — one default agent and one specialized coder or researcher profile with its own model and skills — then run a complex background-agent task from your phone via iMessage and inspect the sub-agent tree when you're back at your desk.
- Why this matters: New playlist item from Alex Finn; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 1:21 / Evidence 1: "file around. Go on my DGX Spark and install this local model." It'll do that for me. And as you can see, boom, a full, nicely formatted investor report on Micron right there. Shout out to me, invested..."
- 2:52 / Evidence 2: "eight of them here. A little hint, a little preview. Background agents. So, previously in Hermes, background agents needed to be turned on manually. You needed to flip a flag. And what background agents are is Hermes agent..."
- 5:38 / Evidence 3: "build in Unreal Engine. It is a very complex, big game engine, but now you can use your Hermes agent to actually build your games. While a lot of people build games using 3.js, which is fine. That's..."
- 8:29 / Evidence 4: "Codex Hermes agent, which does a lot of my coding for me. I have Librarian, which manages my memory. You can quickly spin up new profiles from here. So, if we do build, we can give it a..."
- 10:21 / Evidence 5: "biggest skills downloader in the world. In fact, what I typically do is I go in, I take the skill.md file, I give it to my agent, I say, "Hey, make your own version of this, and make..."
- 11:55 / Evidence 6: "Hermes more prompts, more commands to do, and you will find that it updates and builds its skills a ton more. In number eight, Telegram just launched a whole bunch of new features for talking with agents, and..."
- 13:32 / Evidence 7: "me. I just love this stuff so much. Thank you for your support. Thank you for everything you do for me and I'll see you in the next video."

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 "The new Hermes Agent update has me speechless....", 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.

Misconceptions

What to stop believing.

A beautiful page is automatically a good learning tool.

Learning requires sequence, active recall, feedback, and application.

Generated UI should be accepted as-is.

Generated UI needs critique, revision, and browser verification.

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 ui critique sheet for judging whether an ai interface improves control..

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 does Hermes Agent connect to iMessage, and when does Finn recommend iMessage versus Telegram versus the desktop app?

What changed about background agents in this update, and what does the new sub-agent tree show?

What is a 'self-improvement review' in Hermes, and what effect did Finn observe from it?

Source shelf

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

ReadingOpen Design Repogithub.com/open-design-dev/open-designReadingReact Docsreact.dev/