GoldieBench Blog · 10 min read
How To Learn More About AI Agents: Where To Keep Learning, And How To Test Every Launch Yourself
How to learn more about AI agents in 2026: 9 sources ranked by format, a 30-minutes-a-day plan, and the launch-day test I run on every new model.

How to learn more about AI agents once you know the basics comes down to testing more and scrolling less.
I am Julian Goldie, and I run this leaderboard by testing new AI models on the same prompts almost every day.
Here is the short path.
- You follow the release notes of the one agent you use most.
- You watch one build video a day and copy one thing from it.
- You join one community so you can ask when you get stuck.
- You test every new tool and model with the same fixed prompts.
- You turn each thing you learn into a small build within 48 hours.
The first part of this post shows where to keep learning, ranked by format.
The second part gives you a weekly plan and my launch-day test.
The last part covers how to follow models, with real scores from this board.
Where to learn more about AI agents, ranked by format
This is my own list, so my own channels come first, and I am saying so plainly.
| Rank | Format | Where to go | Best for |
|---|---|---|---|
| 1 | Daily videos | My YouTube channel and my podcast channel, AI News Today | You see a new tool running on a real screen. |
| 2 | Communities | AI Profit Boardroom (paid) and AI Money Lab (free) | You get answers when a setup breaks. |
| 3 | Written guides | agentos.guide | You follow a build step by step. |
| 4 | A model leaderboard | This site | You choose which model to try next. |
| 5 | Official docs and changelogs | Hermes, Anthropic, OpenAI and Google | You learn exactly what changed. |
| 6 | GitHub repos | The repos behind your tools | You see real activity before any announcement. |
| 7 | Newsletters and blogs | One or two long-running ones | You get a weekly summary with context. |
| 8 | X accounts | The official lab accounts | You get launch alerts on the day. |
| 9 | Papers | Three or four classics | You understand why agents work as they do. |
Videos come first because watching a tool run is the fastest way to judge it.
Papers come last because they rarely change what you build this week.
Three sources are enough to start, which means one video channel, one community and one changelog.
The 30-minutes-a-day plan
Each day has one job, and the whole week takes three and a half hours.
| Day | Your 30 minutes | What you keep |
|---|---|---|
| Monday | You read the release notes for your main agent. | One new feature to try |
| Tuesday | You watch one build video and copy the steps. | One working copy |
| Wednesday | You build with Monday's feature. | One small thing that runs |
| Thursday | You read one docs page on a feature you have never used. | One short note |
| Friday | You test one new tool or model with your fixed prompts. | One new row in your score sheet |
| Saturday | You share your build in a community and ask one question. | One piece of feedback |
| Sunday | You review your notes and choose next week's build. | A plan for Monday |
Only two of those days are about new information.
The other five are about building, testing, asking and reviewing, because that is where learning sticks.
Friday is the day this site is built around, so I will spend the most time on it.
Official docs and changelogs
Docs and release notes are written by the people who shipped the change, so they are the most accurate source you have.
| Source | What you will find there |
|---|---|
| Hermes Agent docs | The docs include a Learning Path page with beginner, intermediate and advanced reading orders. |
| Hermes Agent releases | Every version is listed with its notes. |
| Claude release notes | Anthropic records changes to the Claude platform here. |
| Anthropic Academy | Anthropic lists courses such as Claude Code 101 and Building with the Claude API. |
| OpenAI API changelog | OpenAI records changes to its API here. |
| OpenAI Agents SDK docs | OpenAI documents its framework for multi-agent workflows here. |
| Google Agent Development Kit docs | Google documents its open-source agent toolkit here. |
| Model Context Protocol | This is the home of the standard that connects agents to tools. |
These pages move quickly.
When I checked the Hermes Agent releases page on 13 October 2026, it listed four releases in about three weeks.
Version 0.21.4 came out on 21 September, version 0.21.5 on 24 September, version 0.21.6 on 8 October and version 0.21.7 on 12 October.
One feature a week from your main tool's release notes is enough to keep you current.
GitHub repos, newsletters and X accounts
A repo shows you when a project was last updated, and every repo below had commits in October 2026 when I checked.
| Repo | What it is |
|---|---|
| NousResearch/hermes-agent | This is Hermes Agent, which calls itself the agent that grows with you. |
| anthropics/claude-code | This is Anthropic's agentic coding tool for the terminal. |
| openai/codex | This is OpenAI's coding agent that runs in your terminal. |
| openai/openai-agents-python | This is OpenAI's framework for multi-agent workflows. |
| google/adk-python | This is Google's code-first Python toolkit for building agents. |
| ollama/ollama | This runs open models on your own machine. |
You set Watch to Releases only on three or four of them, and GitHub tells you when a new version ships.
For reading, I would pick one of these, and each had published in the week before 13 October 2026.
| Source | What it is |
|---|---|
| Simon Willison's Weblog | This is a personal blog on AI tools and models that is updated often. |
| Latent Space | This is a technical newsletter and podcast for AI engineers. |
| Import AI | This is Jack Clark's weekly AI newsletter. |
| The Batch | This is the weekly AI news email from DeepLearning.AI. |
On X, I would follow official accounts that each organisation links from its own website, such as @NousResearch, @AnthropicAI and @GoogleDeepMind.
I post model launches and screenshots from this bench on my own X account.
X tells you that something launched, and the docs tell you what it actually is.
How I test a new tool the day it launches
Reading about a launch teaches you very little, and running it teaches you a lot.
My routine is on my about page, and it has three steps.
- I wire the new model into my Agent OS, so I can send it work from the same board my other agents use.
- I run my fixed prompt set through it with one shot each, no second tries and no hints.
- I score each result from 0 to 10 on camera.
I score on whether it ran, how close it came to the brief and how good it looks.
Every cell on this leaderboard is one of those one-shot builds, and the methodology page explains the rules.
Each result has to be a single HTML file that runs in a browser, so anyone can open it and judge it.
How to run your own launch-day test
You do not need my setup to copy the method.
- You save three to five prompts in a text file, and each one is a real job you care about.
- You add the new tool or model next to the one you already use.
- You run every prompt once and save what comes out.
- You score each result from 0 to 10 and write one line about why.
- You compare the scores with your current tool before you change anything.
The prompts must stay the same every time.
Fixed prompts are what turn an opinion into a comparison.
One shot matters too, because a tool that needs five retries will cost you five times the attention in real work.
After a few months you will have a small score sheet of your own, and it will know your work better than any public board does.
How to avoid hype
I use three checks, and they take about ten minutes together.
The first check is the repo and the README.
A real tool has install steps you can follow and recent updates you can see.
The second check is the date.
Anthropic's engineering post, Building effective agents, was published on 19 December 2024.
Anthropic has since added a note at the top saying much of the tooling it describes has changed.
The ideas are still worth reading, and the note is a good reminder to check the date on everything.
The third check is your own test.
A launch post will always show the tasks a model is best at.
Your prompts show the tasks you actually need.
How to turn learning into a build
My rule is that one thing learned becomes one thing built within 48 hours.
I teach the same order every time.
- You start with one agent doing one job.
- You keep one profile per model, so you can swap the brain without breaking the job.
- You use free models first and pay only when a job needs it.
- You connect the jobs into an Agent OS once two or three of them run well.
My own example is a radar.
It is an agent on a schedule that reads live posts on X at six each morning and scores every story.
When I published the guide to it, it had logged 49 mornings and scored 294 trends.
Your version can be an agent that checks three release pages each morning and sends you a summary.
If you want the full dashboard, my Agent OS build guide walks through it in five steps.
Papers for the curious
You can skip papers and still become very good with agents.
If you like knowing why things work, these well-known papers are free on arXiv.
| Paper | Year | The idea |
|---|---|---|
| ReAct: Synergizing Reasoning and Acting in Language Models | 2022 | The model reasons and then acts in a loop. |
| Toolformer: Language Models Can Teach Themselves to Use Tools | 2023 | The model learns when to call a tool. |
| Generative Agents: Interactive Simulacra of Human Behavior | 2023 | The agents use memory, reflection and planning. |
| SWE-bench: Can Language Models Resolve Real-World GitHub Issues? | 2023 | The paper introduced a widely cited coding benchmark. |
You read the abstract and the introduction first, and you stop if it will not change a build.
How to follow AI models with a leaderboard
An agent is a model plus tools, memory and a loop, so the model you choose matters.
New models now arrive faster than anyone can read about them.
A leaderboard lets you follow them in five minutes.
GoldieBench measures one thing, which is whether a model can ship a finished build from one prompt.
It does not measure every skill an agent needs, such as long tool-calling sessions or memory.
Here are averages for some of the models on the live board on 13 October 2026.
| Model | Average out of 10 | Page |
|---|---|---|
| Fusion | 8.59 | Fusion |
| Claude Opus 5 | 8.27 | Claude Opus 5 |
| Hermes MoA | 8.17 | Hermes MoA |
| GPT-5.6 Sol | 8.16 | GPT-5.6 Sol |
| Claude Fable 5 | 8.10 | Claude Fable 5 |
| Qwen 3.8 | 8.10 | Qwen 3.8 |
| Kimi K3 | 7.89 | Kimi K3 |
| GLM-5.2 | 7.77 | GLM-5.2 |
| Claude Opus 5.5 | 7.57 | Claude Opus 5.5 |
| Gemini 3.6 Flash | 7.08 | Gemini 3.6 Flash |
Scores change as I add tasks, so the live pages are always the source of truth.
Three lessons the board teaches about learning
The first lesson is that newer is not automatically better.
Claude Opus 5.5 is the newer model, and it averages 7.57 here while Claude Opus 5 averages 8.27 on the same prompts.
Opus 5.5 was scored in a separate, stricter run than Opus 5, so I treat that gap as a reason to test, not as proof.
That does not make it a worse model overall, because this bench tests one kind of work.
It does mean you should test before you switch.
The second lesson is that a system can beat a single model.
Fusion and Hermes MoA both combine several models, and both sit near the top of the board.
That is a good reason to learn about orchestration and not only about models.
The third lesson is that the best-known labs are not your only option.
Qwen 3.8, Kimi K3 and GLM-5.2 all average above 7.7 here.
You can see models that run on your own machine on the local models page.
Free models first is a sensible rule for learning, because your mistakes cost nothing.
How to use this board in your Friday slot
- You open the leaderboard and look for a model you have not tried.
- You open its page and click two or three of the live demos.
- You compare it with the model you use now on the compare page.
- You add it as a new profile in your agent if it looks promising.
- You run your own fixed prompts and write the scores down.
My scores tell you where to look.
Your scores tell you what to use.
Where to go next
If you want the path from the start, read my how to learn AI agents guide.
If you want structured lessons, my best AI agent courses online list and my best AI agent course for 2026 compare the options.
If you want to compare communities, my best Skool courses list ranks them.
If you want to know who runs this board, my Julian Goldie page covers my background.
Also On Our Network
- Agent Operatorsthe operator's weekly routine for learning more about AI agents
- AI Income Deskhow to turn AI agent learning into real builds for a business
- AI Tool Verdictnine kinds of AI agent learning source, ranked and scored
- agentos.guidethe 30-minutes-a-day learning loop inside an Agent OS
- agentos.guideJulian's full Hermes crash course on agentos.guide
Pick three sources, test one new model every Friday, write your scores down, and you will have your own answer to how to learn more about AI agents.
FAQ
How do I learn more about AI agents after the basics?
Follow the release notes of the one agent you use most, watch one build video a day, join one community, test new tools with the same fixed prompts, and turn each thing you learn into a small build within 48 hours.
How does Julian Goldie test a new AI model on launch day?
He wires the model into his Agent OS, runs his fixed prompt set through it with one shot each and no hints, and scores each result from 0 to 10 on camera. Those one-shot builds are the cells on GoldieBench.
Does GoldieBench measure how good a model is for AI agents?
Not directly. GoldieBench measures whether a model can ship a finished build from one prompt. It does not test long tool-calling sessions or memory, so you should also run your own prompts.
Is a newer AI model always better?
No. On the live board, Claude Opus 5 averages 8.27 and the newer Claude Opus 5.5 averages 7.57 on the same one-shot prompts. Opus 5.5 was scored in a separate, stricter run than Opus 5, so I treat that gap as a reason to test, not as proof. That is one kind of test, which is why you should try a model on your own work before switching.
How much time do I need each day to stay current with AI agents?
Thirty minutes a day is enough if each day has one job: changelogs, a video, a build, a docs page, a test, a community post and a weekly review.
How do I avoid AI agent hype?
Check that the repo and README exist and are active, check the date on what you are reading, and run the tool on your own fixed prompts before you repeat a claim about it.


