@dougvk/askcodexrpc

OpenClaw plugin that runs one Codex app-server JSON-RPC runtime per chat session, hosted inside a dedicated tmux session, and posts completed turns back to chat.

Commands

• /askcodexrpc help
• /askcodexrpc status
• /askcodexrpc new [abs path]
• /askcodexrpc <prompt>
• /askcodexrpc stop
• /askcodexrpc reset
• /askcodexrpc handoff
• /askcodexrpc resume

Feature parity scope

• Per-chat Codex app-server bridge process in tmux (clawd-codexrpc-*)
• JSON-RPC over Unix socket between plugin and tmux-hosted bridge
• Thread creation/resume
• Turn start + steer while active
• Immediate prompt ack delivery to Discord on submit
• Native /askcodexrpc ... plugin command path that bypasses LLM rephrasing
• Live streaming progress snapshots to Discord while the turn is active (thinking, plan, tool calls, command output tail)
• Async completion delivery to Discord with completion dedupe guard
• Startup/background recovery loop for in-flight turns after gateway restarts
• Session lifecycle commands (new/send/status/stop/reset/resume/handoff)

Requirements

• codex CLI with app-server support on PATH (or configure codexBin)
• Dedicated codexHome and defaultCwd configured in plugins.entries.askcodexrpc.config

Config

See openclaw.plugin.json for schema.

Typical config:

{
  "plugins": {
    "entries": {
      "askcodexrpc": {
        "enabled": true,
        "config": {
          "codexHome": "/home/user/.askcodexrpc-home",
          "defaultCwd": "/home/user",
          "codexBin": "codex",
          "approvalPolicy": "on-request",
          "sandbox": "workspace-write",
          "tmuxPrefix": "clawd-codexrpc"
        }
      }
    }
  }
}

/askcodexrpc status returns tmux diagnostics, bridge socket/log diagnostics, recovery health, and an attach command.

Tests

npm test