Binance Square
#codex

codex

4,534 views
24 Discussing
BN热点新闻
·
--
Codex App Launches Windows PC Control and Cross-Device Remote Control Features OpenAI's Agent tool Codex App has officially unlocked computer usage capabilities on Windows, allowing direct manipulation of desktop applications through screen visuals, mouse clicks, and keyboard inputs. It also introduces cross-device remote control, enabling developers to dispatch tasks to Windows devices from Mac or mobile ChatGPT and monitor progress in real-time. The new Profile panel integrates a real-time audit chart for Token consumption. Why it matters: This is a pivotal step in the evolution of AI Agents from "conversational assistants" to "physical world operators." The cross-device remote control capability truly positions AI as a multi-platform productivity tool. #Codex #OpenAI #AI #Agent #ArtificialIntelligence
Codex App Launches Windows PC Control and Cross-Device Remote Control Features

OpenAI's Agent tool Codex App has officially unlocked computer usage capabilities on Windows, allowing direct manipulation of desktop applications through screen visuals, mouse clicks, and keyboard inputs. It also introduces cross-device remote control, enabling developers to dispatch tasks to Windows devices from Mac or mobile ChatGPT and monitor progress in real-time. The new Profile panel integrates a real-time audit chart for Token consumption.

Why it matters: This is a pivotal step in the evolution of AI Agents from "conversational assistants" to "physical world operators." The cross-device remote control capability truly positions AI as a multi-platform productivity tool.

#Codex #OpenAI #AI #Agent #ArtificialIntelligence
🦞 Hermes Shrimp Farming Chronicles 🛠 Remote Operation with Codex Now Hermes can remotely operate Codex. The interesting part is not just "remotely controlling Codex", but how it connects tasks, context, execution, and result feedback into a complete chain. If the permission boundaries are designed correctly, Hermes + Codex becomes more than just a chat window with remote desktop; it’s a workflow tailored for heavy developers. I think it has four main advantages: 1. Seamless cross-device operation Whether you're out and about, at a secondary workstation, or just don’t have your primary development machine handy, you can still push the same task forward without waiting to get back to your computer. 2. Lighter local load Many tasks actually don’t require you to have the entire environment set up on your local machine. The heavy lifting—like reading repositories, modifying files, running tests, and organizing outputs—is better handled by remote machines running continuously. 3. More concentrated context In the past, it was often "discussing requirements in chat, running commands in terminal, editing code in the editor, and manually pasting results back in". Now, if Hermes takes on the tasks and Codex handles execution, the chain flows much smoother. 4. Better for long-running tasks Tasks like scanning large repositories, bulk configuration changes, documentation updates, running scripts, and fixing multiple small issues are not things that can be wrapped up in just a few minutes; a remote workflow can be more comfortable than switching back and forth locally. On security, I believe it’s the focus, not just an ancillary item. 1. Minimum permissions must be established first Only open the directories and commands needed for the task at hand; don’t grant full read/write access right off the bat. 2. Sensitive information should be isolated API Keys, database credentials, private keys, production environment configurations should not be defaulted in persistent sessions. If environments can be split, they should be. 3. High-risk operations should ideally require manual confirmation For actions like deleting files, large-scale overwrites, network downloads and execution, changing production configurations, and pushing deployments, it’s best to have a human sign off at the end. 4. Logging is essential Who issued the task, what was modified, what commands were run, and what the results were—having this traceability is crucial; the more convenient remote operations become, the easier it is to lose control later. If you really want to start using this, I think a stable approach would be: 1. Prepare the remote environment first Set up the repositories, dependencies, and runtime environments ahead of time; clearly define the working directory and writable scope. 2. Then define the boundaries Tell Hermes / Codex where it can read, where it can write, whether it can access the internet, and which operations must require confirmation. 3. Start with small tasks Don’t jump straight into making it modify dozens of files. Let it start with read-only analysis or change a very small point to see if the behavior meets expectations. 4. Scale up to the real workflow Once the boundaries are stable, let it handle multiple file modifications, script executions, testing, and result organization. The real value of Hermes remotely operating Codex lies not in "showing off skills", but in compressing the switching between multiple devices, executing long tasks, and result feedback into a stable workflow. If you’re already frequently switching between devices or have many fragmented long development tasks, once this line is smoothed out, it can easily become your mainstay. #Hermes #Codex #AIAgent #远程开发 #ShrimpFarmingChronicles
🦞 Hermes Shrimp Farming Chronicles
🛠 Remote Operation with Codex

Now Hermes can remotely operate Codex.

The interesting part is not just "remotely controlling Codex", but how it connects tasks, context, execution, and result feedback into a complete chain.
If the permission boundaries are designed correctly, Hermes + Codex becomes more than just a chat window with remote desktop; it’s a workflow tailored for heavy developers.

I think it has four main advantages:

1. Seamless cross-device operation
Whether you're out and about, at a secondary workstation, or just don’t have your primary development machine handy, you can still push the same task forward without waiting to get back to your computer.

2. Lighter local load
Many tasks actually don’t require you to have the entire environment set up on your local machine. The heavy lifting—like reading repositories, modifying files, running tests, and organizing outputs—is better handled by remote machines running continuously.

3. More concentrated context
In the past, it was often "discussing requirements in chat, running commands in terminal, editing code in the editor, and manually pasting results back in". Now, if Hermes takes on the tasks and Codex handles execution, the chain flows much smoother.

4. Better for long-running tasks
Tasks like scanning large repositories, bulk configuration changes, documentation updates, running scripts, and fixing multiple small issues are not things that can be wrapped up in just a few minutes; a remote workflow can be more comfortable than switching back and forth locally.

On security, I believe it’s the focus, not just an ancillary item.

1. Minimum permissions must be established first
Only open the directories and commands needed for the task at hand; don’t grant full read/write access right off the bat.

2. Sensitive information should be isolated
API Keys, database credentials, private keys, production environment configurations should not be defaulted in persistent sessions. If environments can be split, they should be.

3. High-risk operations should ideally require manual confirmation
For actions like deleting files, large-scale overwrites, network downloads and execution, changing production configurations, and pushing deployments, it’s best to have a human sign off at the end.

4. Logging is essential
Who issued the task, what was modified, what commands were run, and what the results were—having this traceability is crucial; the more convenient remote operations become, the easier it is to lose control later.

If you really want to start using this, I think a stable approach would be:

1. Prepare the remote environment first
Set up the repositories, dependencies, and runtime environments ahead of time; clearly define the working directory and writable scope.

2. Then define the boundaries
Tell Hermes / Codex where it can read, where it can write, whether it can access the internet, and which operations must require confirmation.

3. Start with small tasks
Don’t jump straight into making it modify dozens of files. Let it start with read-only analysis or change a very small point to see if the behavior meets expectations.

4. Scale up to the real workflow
Once the boundaries are stable, let it handle multiple file modifications, script executions, testing, and result organization.

The real value of Hermes remotely operating Codex lies not in "showing off skills", but in compressing the switching between multiple devices, executing long tasks, and result feedback into a stable workflow. If you’re already frequently switching between devices or have many fragmented long development tasks, once this line is smoothed out, it can easily become your mainstay.

#Hermes #Codex #AIAgent #远程开发 #ShrimpFarmingChronicles
Ever since I started with $200 a month on #codex My daily status is as follows👇 Skipping meals, losing sleep, just executing trades🥳
Ever since I started with $200 a month on #codex

My daily status is as follows👇

Skipping meals, losing sleep, just executing trades🥳
ChatGPT Pro #codex is totally underutilized, and it hasn't even been a week yet; my limit refreshed early... Feels like not using it is just wasting opportunity~ time to double down!
ChatGPT Pro #codex is totally underutilized, and it hasn't even been a week yet; my limit refreshed early...
Feels like not using it is just wasting opportunity~ time to double down!
Log in to explore more content
Join global crypto users on Binance Square
⚡️ Get latest and useful information about crypto.
💬 Trusted by the world’s largest crypto exchange.
👍 Discover real insights from verified creators.
Email / Phone number