co-codex-skill

简体中文说明

co-codex-skill lets Codex return a phone-ready link for the local machine you are working on.

Use it when you want a workflow like:

• "execute co-codex"
• "send me the remote link"
• "let me watch Codex from my phone"

After installation, the skill can:

1. install co-codex-agent on the current machine when needed
2. start or reconnect the local agent inside the current Codex session
3. print a device-scoped mobile URL from worker.aipage.asia as soon as it is ready

Local install

cd /path/to/co-codex-skill
npm run install:local

This installs the co-codex skill, the local agent installer, the local launcher, and a sample config file.

Config

The local agent reads:

~/.codex/co-codex.config.json

Minimum example:

{
  "relayAgentKey": "agent-secret",
  "default_pro_path": "/Users/you/Projects/your-default-project"
}

You can get your own relayAgentKey from https://worker.aipage.asia after signing in with GitHub. Each personal key currently binds one agent.

default_pro_path is the default project path used by the phone page when creating a new thread.

If you want the phone page to send follow-up messages back into the local Codex session, enable:

{
  "relayAgentKey": "agent-secret",
  "default_pro_path": "/Users/you/Projects/your-default-project",
  "allowRemoteInject": true
}

If you only want to monitor progress from the phone, leave allowRemoteInject disabled.

Behavior notes

• Keep the Codex thread that launched co-codex open. That long-running session is what keeps the local agent alive.
• If that thread is interrupted or the agent exits, the phone page will stop syncing.
• If you want phone-originated follow-up messages to control Codex Desktop, macOS must allow the local terminal / launcher process to use Accessibility-style system control permissions. Without that permission, monitoring still works, but remote message injection into the desktop UI can fail.
• The currently active desktop thread uses focused UI interaction.
• Non-active threads use background injection mode. Those messages still work, but Codex Desktop may need a restart before the injected turns appear in that thread's UI.
• The default shared relay key is capacity-limited. If the launcher tells you the shared key is full, open https://worker.aipage.asia and request your own free relay key, then replace relayAgentKey in ~/.codex/co-codex.config.json.
• Each personal relayAgentKey currently supports one agent binding. Reuse the same device, or rotate the key before moving it to a different machine.
• If co-codex behavior seems outdated, reinstall or compare your local copy with the latest instructions in this GitHub repository before debugging further.

In Codex

After installation, ask Codex for the mobile entry in plain language, for example:

• "execute co-codex"
• "send me the remote link"
• "give me the mobile URL for this Mac"

The returned URL is scoped to the current device.