Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

I turned codex (with gpt-6 astra) into a grok bot alternative. each session in codex is its own bot identity, and each bot has its own computer on orgo. this is absolutely insane and this feels like the hive mind that opens up the world of agi

35,651 görüntüleme • 2 ay önce •via X (Twitter)

38 Yorum

Nick Vasilescu profil fotoğrafı
Nick Vasilescu2 ay önce

oh btw give a real computer to your agent here:

Adar profil fotoğrafı
Adar2 ay önce

spinning them up is the easy part for me, telling which session is stuck vs still working is what kills it. how do you handle that across a bunch of them?

Nick Vasilescu profil fotoğrafı
Nick Vasilescu2 ay önce

astra is good at orchestration

Gavin Basuel profil fotoğrafı
Gavin Basuel2 ay önce

Codex as a harness plus Orgo is insane. No need to get anymore hardware lol

RICARDO profil fotoğrafı
RICARDO2 ay önce

do i need this 👀

Ion Brinzila profil fotoğrafı
Ion Brinzila2 ay önce

Wait a week or so an OpenAI will publish something along the lines of:)

Benno Sawitzki profil fotoğrafı
Benno Sawitzki2 ay önce

What did the team get done for you?

Nikita Odintsov profil fotoğrafı
Nikita Odintsov2 ay önce

Интересно. Скорость расхода лимитов какая?

ethereagle · building profil fotoğrafı
ethereagle · building2 ay önce

each session as its own bot only sticks if the orgo disk survives a restart. is that a persistent VM per identity, or a fresh machine every time you open the session?

Nick Vasilescu profil fotoğrafı
Nick Vasilescu2 ay önce

persistent 24/7

ethereagle · building profil fotoğrafı
ethereagle · building2 ay önce

so the identity survives a restart. does the disk survive a crash too, or only a clean shutdown?

Tucker King profil fotoğrafı
Tucker King2 ay önce

Each bot getting its own computer is wild.

MONKE2525E profil fotoğrafı
MONKE2525E2 ay önce

I knew someone would do this! Great work I really hope OAI adds this soon...

Riley profil fotoğrafı
Riley2 ay önce

This is dope! I just want to say though that grok bots sharing one computer was a very intentional choice.. like that’s the point haha so just sounds funny being framed as a negative when they purposely went that direction. I’m sure there are use cases for both

trips profil fotoğrafı
trips2 ay önce

Sheeesh

Malhar Ujawane profil fotoğrafı
Malhar Ujawane2 ay önce

What does the cost look like for a week of usage?

Expansion profil fotoğrafı
Expansion2 ay önce

No u didnt

Juan Rios profil fotoğrafı
Juan Rios2 ay önce

why each bot need a computer? what are you building? hehe

Calvin Tang profil fotoğrafı
Calvin Tang2 ay önce

Separate identity plus its own computer is a strong setup — the harder test is whether one session's conclusion can hand off to the next without you re-pasting context.

Yuri Laguardia profil fotoğrafı
Yuri Laguardia2 ay önce

I’m experimenting with something similar to this, but as plugin in @sawyerhood’s so bots get then own tab Very nice potential for customization there!

Adam Killam profil fotoğrafı
Adam Killam2 ay önce

What's the goal?

Cody Schuldt profil fotoğrafı
Cody Schuldt2 ay önce

How are you handling credentials and logins when a bot is using something that needs a login

Ishant profil fotoğrafı
Ishant2 ay önce

But what will you do with it

Kiran Adimatyam profil fotoğrafı
Kiran Adimatyam2 ay önce

You have not seen how grok bot is done. That is very clever engineering.

Walter Goldson profil fotoğrafı
Walter Goldson2 ay önce

this has come a long way since efnet bot nets

dawood46 profil fotoğrafı
dawood462 ay önce

context must be awfully managed no?

The Liberty Lookout profil fotoğrafı
The Liberty Lookout2 ay önce

The useful part isn't the AGI label. It's the leverage: one person can coordinate a fleet of agents and test ideas that once needed a much larger team.

Eric - Not doing 9 to 5 profil fotoğrafı
Eric - Not doing 9 to 52 ay önce

What power does it take for each bot to have its own computer.? 🤔

The Bentist (Dr. Winters) profil fotoğrafı
The Bentist (Dr. Winters)2 ay önce

How do you have them communicate to each other?

Native AI profil fotoğrafı
Native AI2 ay önce

How many subscriptions do you burn trough per day with this setup? I would need at least 3 for this.

MelonLeather profil fotoğrafı
MelonLeather2 ay önce

@thsottiaux pls make this easier, lol

Michał Archacki profil fotoğrafı
Michał Archacki2 ay önce

how did u do that exactly? :)

Benjy Wang profil fotoğrafı
Benjy Wang2 ay önce

They can do the same without their own computer sandbox.. way less CPU and RAM overhead. If it's got a good custom harness do you even need the visibility? Why be the bottleneck?

Bob profil fotoğrafı
Bob2 ay önce

How-to would be nice.

Thomas Hölzl profil fotoğrafı
Thomas Hölzl2 ay önce

Cool stuff @nickvasiles what is the recogniseable difference to Running on one Maschine with various threads? Besides resource power.

DC profil fotoğrafı
DC2 ay önce

Astra's computer use is amazing

Nathan Romano profil fotoğrafı
Nathan Romano2 ay önce

the price though must go through the roof. But yea that is one way I guess.

steve_OpenCreators profil fotoğrafı
steve_OpenCreators2 ay önce

API/implementation crumbs are the good stuff. Especially the bit about "turned codex (with gpt-6".

Benzer Videolar

Insane Grok Grok Bot upgrade! Finally, you can connect Grok Bot to different agent harnesses and run tasks through their native runtimes. Devs just open-sourced HarnessRouter, the infrastructure layer that lets Grok Bot run tasks across: - Codex - Hermes - Claude Code - DeepSeek Harness - System One, powered by Jev - Pi, and 20 more GitHub repo: (don’t forget to star it ⭐) With HarnessRouter, each external specialist gets to use its own harness, model, tools, skills, and agent loop while Grok coordinates the project from one conversation. I tested this by asking Grok Bot to turn a support-ticket CSV into an interactive dashboard. Grok Bot assigned the analysis to DeepSeek Harness with Claude Sonnet 5.5, passed the output to Codex with GPT-5.5, and checked the finished dashboard in its browser. This differs from simply creating more Bots. These workers are not additional Grok Bots, and Grok Bot itself does not switch harnesses. Instead, it remains the coordinator while the delegated tasks run inside separate HarnessRouter sessions with the harness of your choice. So for another task, you can use Claude Code, Hermes, Pi, etc., without requiring a separate integration for task execution, sessions, streaming, and generated files. HarnessRouter standardizes all those operations through the Unified Harness Protocol (UHP). UHP handles sessions, streaming, files, cancellation, and failures through the same interface, regardless of which harness runs the task. I shared the GitHub repo above. And if you want to dive deeper into Grok Bot, I wrote about it in full in a masterclass, including the shared computer, memory, skills, routines, and the macOS setup. Read it below.

Avi Chawla

137,409 görüntüleme • 17 gün önce