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.
Isn't this one of the problems foreseen with this? For you, it was a single prompt - for 40 companies, this probably took up some time.
What happens when fifty people fire off a 15-second "get me a shirt" prompt? When five hundred, five thousand, five million do?
So using a bot is almost like having an employee, but instead of a fixed salary, or even an hourly rate, they will just invoice you for whatever they think is necessary to do the tasks you give them? And agents can be very creative when coming up with ways to spend tokens...
> The coolest thing I had it do for me was sourcing fabric for swag
That seems like something codex could just have done on my laptop. Am I wrong?
There is
though currently much worse
If someone solves this part of continual effective compaction + selective resetting at cache expiry, they're going to make a ton of money. Right now, only the token insensitive can use these sweet features.
Or in a world where tokens do not fuel AI, which is the more likely longer term outcome.
I hope that Dario Amodei fails in his quest to regulate open models out of existence to line his pocket under the guise of safety. Amodei/anthropic will end up being the most harmful force in the next few decades where progress in AI is concerned.
I hope people realize sooner than later that this is a replay of early Microsoft vs open source situation and Amodei is the new Gates on a crusade against open source/Linux.
The difference now is that big companies themselves promote/offer bots, but they also don't like to be scraped and use captchas.
What do we do now? Is it allowed to use automated tools to interact with any system? Is it allowed to scrape data? Are there any laws for this?
If we do things manually it is ok, but not if we use a bot?
Confusing (legal) times...
Tell me one reason why I would use this at my company? I basically have to bet on Grok being the best models for this.
Or I can use an open source version and use whatever model I want.
You see this with coding agents, everyone used Claude Code and then realized holy shit this is expensive and now use open source agents and they can use open source models and cut costs.
How does it work with login-walled sites like LinkedIn then? And what does "own computer" mean? X provisions a "private cloud" a'la Apple for your Bot?
One thing that this highlights for me even more than before is that having accounts for my bots is what I really want. I want SaaS providers to catch up to bot use. They need their own accounts on a lot of these services and per-seat pricing works against this.
I almost wonder if this is a place where SpaceX, as an internet provider through starlink, has a unique advantage because websites are unable to block their networking as it could be residential starlink consumers.
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.
Either way, I still don't think that computer use is solved. It worked horribly on Codex and Antigravity the last time I tried. Maybe I was doing something wrong.
Otherwise, I think this would still go into my "I don't get it" folder. It seems like the flavor of the day is "agents can talk to each other" and Grok Bot is selling that point along with Claude Code. But I think Pi has had this for a while? Or it was easy to wire it in.
Although I'll probably never use Grok, this is an interesting release. I always thought GPT work and Claude Cowork are a bit awkward in their positioning. I'm still not sure what the real difference is with standard chat. This looks like the same thing with seamless memory and skills creation.
This seems like the middle ground between work mode and OpenClaw/Hermes (which I've never tried, too scared to mess something up). I think the humanization of the agents is cute and makes sense UX wise. I hope to see alternatives soon.
This is an interesting idea although I'm not sure how many companies are comfortable with giving SpaceXAI access to all your files and data. Outside of America this is, most likely, not going to fly.
* "Anyone who opposes remigration is a traitor"
* "She is a traitor to the West, plain and simple" (in reference to his recent interviewer)
* "Deal with traitors before invaders. They are committing high treason."
* "First the traitors, then the invaders" (screenshot from Citizen Vigilante pointing gun at camera)
Yes sirree: just a completely normal tech product without any asterisks.
48% weekly usage left after 3 hours of experimenting, tough.
It's not trivial to do, and I never managed to get bot-to-bot communication working. Even with my janky setup, the experience is honestly pretty great. Grok Bot simplifies the setup for this about as far as I imagine is possible, and frankly it's a pretty slick experience.
I fully expect this paradigm to catch on quickly.