Загрузка видео...

Не удалось загрузить видео

На главную

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 просмотров • 2 месяцев назад •via X (Twitter)

Комментарии: 38

Фото профиля Nick Vasilescu
Nick Vasilescu2 месяцев назад

oh btw give a real computer to your agent here:

Фото профиля Adar
Adar2 месяцев назад

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
Nick Vasilescu2 месяцев назад

astra is good at orchestration

Фото профиля Gavin Basuel
Gavin Basuel2 месяцев назад

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

Фото профиля RICARDO
RICARDO2 месяцев назад

do i need this 👀

Фото профиля Ion Brinzila
Ion Brinzila2 месяцев назад

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

Фото профиля Benno Sawitzki
Benno Sawitzki2 месяцев назад

What did the team get done for you?

Фото профиля Nikita Odintsov
Nikita Odintsov2 месяцев назад

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

Фото профиля ethereagle · building
ethereagle · building2 месяцев назад

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
Nick Vasilescu2 месяцев назад

persistent 24/7

Фото профиля ethereagle · building
ethereagle · building2 месяцев назад

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

Фото профиля Tucker King
Tucker King2 месяцев назад

Each bot getting its own computer is wild.

Фото профиля MONKE2525E
MONKE2525E2 месяцев назад

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

Фото профиля Riley
Riley2 месяцев назад

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
trips2 месяцев назад

Sheeesh

Фото профиля Malhar Ujawane
Malhar Ujawane2 месяцев назад

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

Фото профиля Expansion
Expansion2 месяцев назад

No u didnt

Фото профиля Juan Rios
Juan Rios2 месяцев назад

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

Фото профиля Calvin Tang
Calvin Tang2 месяцев назад

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
Yuri Laguardia2 месяцев назад

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
Adam Killam2 месяцев назад

What's the goal?

Фото профиля Cody Schuldt
Cody Schuldt2 месяцев назад

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

Фото профиля Ishant
Ishant2 месяцев назад

But what will you do with it

Фото профиля Kiran Adimatyam
Kiran Adimatyam2 месяцев назад

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

Фото профиля Walter Goldson
Walter Goldson2 месяцев назад

this has come a long way since efnet bot nets

Фото профиля dawood46
dawood462 месяцев назад

context must be awfully managed no?

Фото профиля The Liberty Lookout
The Liberty Lookout2 месяцев назад

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
Eric - Not doing 9 to 52 месяцев назад

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

Фото профиля The Bentist (Dr. Winters)
The Bentist (Dr. Winters)2 месяцев назад

How do you have them communicate to each other?

Фото профиля Native AI
Native AI2 месяцев назад

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

Фото профиля MelonLeather
MelonLeather2 месяцев назад

@thsottiaux pls make this easier, lol

Фото профиля Michał Archacki
Michał Archacki2 месяцев назад

how did u do that exactly? :)

Фото профиля Benjy Wang
Benjy Wang2 месяцев назад

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
Bob2 месяцев назад

How-to would be nice.

Фото профиля Thomas Hölzl
Thomas Hölzl2 месяцев назад

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

Фото профиля DC
DC2 месяцев назад

Astra's computer use is amazing

Фото профиля Nathan Romano
Nathan Romano2 месяцев назад

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

Фото профиля steve_OpenCreators
steve_OpenCreators2 месяцев назад

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

Похожие видео

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 просмотров • 16 дней назад