How do you build your own Dots or open-source Grok Bot?
Start as high up the stack as you can. Use the most off-the-shelf layer that still gives you the control you need, and only move down when your agent requires it.
We had
@an_engineer_log , founder of YC F26 startup Agent37, walk us through what he’s seen work across real agent products. A few things that stood out:
- Dots, Muse, Instinct & Grok Bot are finished products. If you want to build your own version, Hermes or OpenClaw give you much of the machinery already. If you need fine-grained control over the agent loop and context, go further down to something like Pi.
- don't automate a workflow before you understand it. do it manually with an agent first, then turn the repeatable parts into skills. One product we discussed ended up with 100+ skills for its workflow.
- same with evals. don't start by designing an eval suite for a process you barely understand. Run it manually a few times, learn what "good" looks like, then encode those signals.
- if you're building for multiple users, don't run them all in the same computer/sandbox to save money. Give each user their own isolated environment.
- humans can be part of the agent architecture too.
@an_engineer_log spent countless hours trying to make browser automation reliable, then realized it was better to have a human handle the brittle browser/form steps while the agent did the rest.
We also walk through a working Dots-like agent built on Hermes , with its own browser, files, memory, and computer per user.
@Agent37HQ is also giving free credits to listeners who want to try running their own agents in an agent sandbox.
First people to reply to this thread will get them.
00:00 Choosing an agent stack
03:29 Products vs. harnesses
04:43 The abstraction ladder
07:21 Memory and scheduling
15:16 When to customize
18:33 Where agents run
24:34 Agent sandbox economics
26:27 One sandbox per user
28:36 From manual work to skills
37:54 Rent humans
42:43 Harness by use case
47:01 Building a Dots-like agent