Hermes + Agent Ops / Foundation

Nemotron 3 Ultra + Hermes Agent = Surprisingly Good

A hands-on test of NVIDIA's Nemotron 3 Ultra (currently free through the Nous portal) driving the Hermes agent on Windows: installing and updating Hermes, selecting the free model, cloning a TTS voice from a repo, scheduling cron jobs, and running the whole agent from Telegram.

Prompt EngineerWatchTranscript found

Quick learning frame

Read this before watching.

Agent ops treats agents like services: observable state, queues, permissions, logs, recovery, and post-run review.

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

Skill you build: The ability to set up the Hermes agent with a free frontier-class model and wire it into real automations — custom TTS integration, scheduled news fetches, and Telegram as a remote control surface.

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.

01Gateway
02Session
03Queue
04Tools
05Logs
06Recovery

Deep lesson

Turn this video into working knowledge.

1,719 cleaned transcript words reviewed across 530 timed caption segments.

Thesis

Nemotron 3 Ultra + Hermes Agent = Surprisingly Good teaches a practical hermes + agent ops move: A hands-on test of NVIDIA's Nemotron 3 Ultra (currently free through the Nous portal) driving the Hermes agent on Windows: installing and updating Hermes, selecting the free model, cloning a TTS voice from a repo, scheduling cron jobs, and running the whole agent from Telegram.

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:27

Free model setup

“can see which model are you using? This is the model by the nose provider. So let's go ahead and test this out. By the way, it works amazing. I feel like I'm working with Haiku. It's amazing.”

Create a free account on the Nous portal, install Hermes via the platform's one-liner in PowerShell (or run 'hermes update' if it's already installed), then run 'hermes model' and select Nvidia Nemotron 3 Ultra from the free models — after which the agent can access your terminal and local folders. Install or update Hermes, run 'hermes model' to pick a free model, and confirm the switch by asking 'which model are you using?' before doing real work.

2:52

Agents do multi-step media work

“>> Nvidia just dropped Nemotron 3 Ultra, a 550 billion parameter mixture of experts model engineered specifically for long-running AI agents. Single-turn chatbots are evolving into long-running agents that reason, maintain context, use tools. >> Okay. >> Simple...”

From one prompt Hermes read a URL, downloaded its assets, wrote a script, and produced a YouTube-style video; when it used the wrong voice, pointing it at a Qwen 3 TTS code folder and asking it to 'understand the code and make this your default TTS' let it integrate and test the new voice entirely on its own. Give your agent a repo or folder and ask it to understand the code and adopt it as a new default tool, then verify the output end to end yourself.

8:08

Telegram plus context headroom

“really beautiful. So, it gives me a the entire list of commands that you can use uh to work with Hermez and it's really great. You can see Hermez model, Hermez chat, Hermez skills, Hermez gateway, cron jobs,...”

Exporting a Telegram bot token and chat ID turns Telegram into a second interface — a cron job pushes recent AI news, you can chat remotely, and TTS output arrives as wave-file attachments; the creator's rule of thumb is agentic work needs 64K+ context, and Nemotron's 256K plus its smarts make it feel like working with Claude Haiku. List the agentic tasks you run and check each against the 64K+ context rule of thumb, flagging which ones need a bigger-context model.

01

Gateway

Start with this video's job: A hands-on test of NVIDIA's Nemotron 3 Ultra (currently free through the Nous portal) driving the Hermes agent on Windows: installing and updating Hermes, selecting the free model, cloning a TTS voice from a repo, scheduling cron jobs, and running the whole agent from Telegram. Treat "Gateway" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:27, where the video says: “can see which model are you using? This is the model by the nose provider. So let's go ahead and test this out. By the way, it works amazing. I feel like I'm working with Haiku. It's amazing.”

02

Session

Use "Session" to locate the part of the hermes + agent ops workflow the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 2:52, where the video says: “>> Nvidia just dropped Nemotron 3 Ultra, a 550 billion parameter mixture of experts model engineered specifically for long-running AI agents. Single-turn chatbots are evolving into long-running agents that reason, maintain context, use tools. >> Okay. >> Simple...”

03

Queue

Turn "Queue" into the reusable artifact for this lesson: An ops checklist for running and recovering local agent work. This is where watching becomes something you can inspect and reuse.

04

Tools

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

Logs

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

Recovery

Use "Recovery" 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 an ops checklist for running and recovering local agent work..

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: A hands-on test of NVIDIA's Nemotron 3 Ultra (currently free through the Nous portal) driving the Hermes agent on Windows: installing and updating Hermes, selecting the free model, cloning a TTS voice from a repo, scheduling cron jobs, and running the whole agent from Telegram.

02

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

03

Map the idea onto the Gateway -> Session -> Queue -> Tools -> Logs -> Recovery sequence and name the weakest link.

04

Produce the artifact and include the evidence that proves it: An ops checklist for running and recovering local agent work.

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: Nemotron 3 Ultra + Hermes Agent = Surprisingly Good
- URL: https://www.youtube.com/watch?v=7RIF3nSVUAQ
- Topic: Hermes + Agent Ops
- My current learning frame: Set up Hermes with the free Nemotron 3 Ultra from the Nous portal, create one cron job that fetches recent AI/LLM news to Telegram every 10 minutes, and verify it fires end to end with your own bot token and chat ID.
- Why this matters: New playlist item from Prompt Engineer; queued for transcript-backed review, topic mapping, and a practical learning artifact.

Transcript anchors from this exact video:
- 0:27 / Evidence 1: "can see which model are you using? This is the model by the nose provider. So let's go ahead and test this out. By the way, it works amazing. I feel like I'm working with Haiku. It's amazing."
- 2:52 / Evidence 2: ">> Nvidia just dropped Nemotron 3 Ultra, a 550 billion parameter mixture of experts model engineered specifically for long-running AI agents. Single-turn chatbots are evolving into long-running agents that reason, maintain context, use tools. >> Okay. >> Simple..."
- 4:51 / Evidence 3: "Hermes. Now I can say which model are you using? So, we have this Nematron 3 Ultra free by the news portal. And then we can say, are there any cron jobs available right now? Let's go ahead..."
- 6:33 / Evidence 4: "token uh in a way I said export the bot token and I pasted in the bot token. Export Telegram chat ID and I pasted the chat ID. And now this is running for me. And it's done."
- 8:08 / Evidence 5: "really beautiful. So, it gives me a the entire list of commands that you can use uh to work with Hermez and it's really great. You can see Hermez model, Hermez chat, Hermez skills, Hermez gateway, cron jobs,..."
- 10:41 / Evidence 6: "Nimotron 3 Ultra. It's free. Go ahead and test this today on Hermes. First, update Hermes and then you'll be able to find that model uh on your free login. Cool. Go ahead and test this out and..."

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: An ops checklist for running and recovering local agent work.
5. Include:
   - a plain-English definition of the core idea
   - a diagram or structured model using this sequence: Gateway -> Session -> Queue -> Tools -> Logs -> Recovery
   - 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 "Nemotron 3 Ultra + Hermes Agent = Surprisingly Good", not a generic Hermes + Agent Ops 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 chat UI is an agent operating system.

A chat UI is only the surface. Ops requires state, logs, permissions, queues, and recovery.

Swarms are automatically more powerful.

Parallel agents help only when work is separable and verifiable.

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 an ops checklist for running and recovering local agent work..

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 do you get Nemotron 3 Ultra for free inside Hermes?

How did the creator replace the agent's default TTS voice?

What context length does the video recommend for agentic work, and how does Nemotron 3 Ultra compare?

Source shelf

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

ReadingOpen WebUI Docsdocs.openwebui.com/ReadingHermes Agent Docshermes-agent.nousresearch.com/docs