fix: Codex/Claude tools target user machines, not the Grok Bot box - #112
Conversation
When the Grok Bot sandbox has no local Codex socket, errors and plugin docs now explain that sessions live on the user's registered computers and how to target them via CODEX_APP_SERVER_SOCK or a local bridge. Co-authored-by: Zack Jackson <ScriptedAlchemy@users.noreply.github.com>
🦋 Changeset detectedLatest commit: 81a4981 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
gbot only dials a local Codex/Claude Unix socket. On HOME=/home/box, tell agents not to call those tools — run gbot on the user's machine via Grok Bot Shell with a machineId after daemon start/bootstrap. Drop SSH/remote guidance. Co-authored-by: Zack Jackson <ScriptedAlchemy@users.noreply.github.com>
Co-authored-by: Zack Jackson <ScriptedAlchemy@users.noreply.github.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 81a49818e6
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "gbot connects only to a local Unix socket ($CODEX_HOME/app-server-control/app-server-control.sock, or CODEX_APP_SERVER_SOCK). There is no remote transport.", | ||
| "When running on the box (HOME=/home/box), do not call codex_* or claude_send there. Run the gbot CLI on the user's machine through Grok Bot Shell with a machineId (the host's machine-targeted shell).", | ||
| "On that machine, provide the socket with `codex app-server daemon start` (or bootstrap). Auth stays with each machine's native Codex or Claude login; gbot does not store or export credentials.", |
There was a problem hiding this comment.
When sendToClaude finds no socket on /home/box, absentClaudeChannelMessage appends this block, which identifies only the Codex socket and tells the caller to start the Codex daemon. Claude actually uses ~/.grok-bot-cli/claude/<name>.sock, created by an opted-in Claude Code session launched with GROK_BOT_CLAUDE_CHANNEL; starting Codex cannot create it. An agent following this error therefore remains unable to use claude_send, so the guidance should provide separate Claude startup instructions.
Useful? React with 👍 / 👎.
2 participants
Summary
Codex and Claude MCP/CLI tools use local Unix sockets only. gbot has no remote transport.
For Grok Bot agents on the box (
HOME=/home/box): do not callcodex_*/claude_send. Run thegbotCLI on the user's registered machine through Grok Bot Shell with a machineId, aftercodex app-server daemon start(or bootstrap) there.Changes
HOME=/home/box(and/home/box/...paths)No remote transport was added.
Test plan
npm run checklocally