Grok Bot

>with, I assume, more guardrails

with Grok, that's a tremendous assumption

I've been using it for the last month or so. IMO in the same way we went from tab complete -> prompts -> agents, this feels like a next step on that evolution. I highly suspect others will be following suit. I was surprised with how much it felt natural to interact with agents in this way.

Biggest advantage is each one owns its own routines, context, and domain, and they can communicate between each other. Similar to hermes they build out their own skills, but by keeping the bots separated by domains, you end up getting better results out of them.

Additionally though each one has their own computer, which means async work feels like it actually works. I haven't had to juggle worktrees for the last month.

Biggest downsides are token expenditure. I've used more tokens this month than not this month. That's not a typo - I've used less tokens in the last 5 years prior to this month than I have this month. Always on perpetual agents use a LOT of tokens. IMO this is building for the future state where tokens are vastly cheaper, ie in a post-ASIC world.

The coolest thing I had it do for me was sourcing fabric for swag: https://image.non.io/d83664c1-5807-4a18-abe4-41928c198410.we...

I wanted to make something that didn't feel like just my logo on a shirt, so I had one of my bots reach out to ~40 fabric suppliers in vietnam, negotiate prices, lock one in, and get samples made. First samples should be finished today. It's been something I've wanted to do for ages, so it was cool seeing it actually happen. The fabric supplier bot worked with one of my prototyper bots to create a randomly generated pattern using my logo, which it then sent as a .ai file to the supplier.

Dupe of https://news.ycombinator.com/item?id=49261532#49263241.

Dang - might be worth merging these two.

The very first thing in their demo shows Grok logging in with the user's username and password to a website, presumably so it can perform actions and the human can get the blame for them. Apparently this is marketing and not terrifying to people.

Neat. I haven't had access to Grok Bot but I rolled my own async agent a while ago using systemd, Codex and old school UNIX stuff like sendmail/postfix/Maildirs. The model gets a rolling and continuously compacted context window in which mail arriving or timed wakeups cause Codex to resume a session with a prompt telling it to do stuff.

As it's linked to an SMTP gateway I interact with it entirely by email. It also has API keys for my internal bug tracker, it has its own git forks of my repos and so on.

Over time it's improved itself so it has adaptive wakeups, a nice monitoring dashboard so I can see what it's doing if I want, a bunch of skills, a nightly wakeup to reorganize its home directories and so on. It keeps a private knowledge base in its home dir and writes its own skills, and it has a persistent todo list. When the todo list is populated it wakes up more frequently so it can break work up into chunks, a kind of basic Ralph loop.

I've found this email-centric paradigm works pretty nicely for me compared to just running a local CLI agent. For instance, I can assign a bug to "Axiom" (it named itself) in YouTrack and the email notification causes it to wake up and start work on the bug. If it gets blocked, it uses its API key to post a comment back to the ticket. If I think of something I just quickly email it, so I'm using Gmail instead of dealing with finicky ChatGPT style UIs that don't have good support for labelling, compact UI and other nice things.

On older models its judgement about what to work on wasn't that good, but with the latest GPTs it's doing much better. I just got back from holiday and it had triaged and resolved over 25 different bugs, a nice selection too.

Because the whole thing runs in a dedicated UNIX user account it is able to modify its own configuration, which has helped as I developed this setup.

However, based on the blog post, Grok Bot sounds a fair bit more sophisticated. I haven't felt a need for more than one bot as I can't easily saturate even a single bot.

Cost: just uses my regular ChatGPT Plus subscription, $20/month, plus of course the server it runs on (which is shared with lots of other stuff). I'm not working with it heavily, perhaps if I did I'd need the $200/month sub.