I'm using this tool a lot today and yesterday and a lot of people don't understand how useful it is. Most people are using it a certain way. It has limitations but this isn't li…

I'm using this tool a lot today and yesterday and a lot of people don't understand how useful it is. Most people are using it a certain way. It has limitations but this isn't like voice chat. It's not built to necessarily just generate and manage threads in Codex or chats or work. It's its own separate entity, for lack of a better word, its own separate construct entity, whatever you want to call it. My point is when you tell it to do stuff, it does it itself and it delegates to itself, which means it's not going to go create a ChatGPT chat, a ChatGPT work chat, or a Codex thread. It's going to do most of the stuff itself using its own computer. It can do multiple things at one time using the computers and the connectors on its own. It can access your laptop via files and CLI and stuff through the connector. 90% of the stuff you tell it to do, it will do on its own. That doesn't mean it's going to be like voice chat, where you're generating a bunch of Codex threads and they're all working simultaneously and then it reports back. That's not how this works. It's its own separate self-contained entity that pretty much single-handedly handles all the various different things you ask it to handle. There are exceptions and there are limitations too. A few people pointed out limitations: - You can't currently attach it to more than one computer. You can only attach it to one laptop or one computer at a time. It won't let you connect multiple. I believe they'll fix that. - Right now it can create Codex threads to do work, but most of the time you don't need to create threads. Most of the time it can handle it on its own unless there's a reason why it needs to do it in a thread format. If it does create a threading Codex, those threads that it creates don't currently have access to browser controls or computer use. I've had it do multiple things through multiple plugins over the last few days and so far the only time it's tried to or needed to create a Codex thread is when I told it to. It doesn't work like the old voice chat, where it's just creating a bunch of Codex threads and then doing the work for you and managing it. It actually proactively does the work itself. It actually goes through and does all the work internally and then keeps you updated as stuff's done. If you give it too much work at some point, it may start outsourcing certain things to Codex but it's interesting how deeply integrated it is already.