AlphaClaw fixes Codex OAuth and gateway restarts for self-hosted OpenClaw

Less rescue work for an OpenClaw deployment

AlphaClaw 0.9.37 addresses two practical failure points in running OpenClaw: provider authentication and gateway replacement. The October 16 release says GPT-6.1 Sol now supports Codex OAuth throughout onboarding and server-side validation. Gateway restarts now wait for shutdown before starting a replacement and preserve process ownership across restarts.

The same release promotes OpenClaw 2026.10.2, which the maintainer says was tested in the Railway beta, and makes watchdog errors and warnings easier to read across themes. These are documented fixes and maintainer testing claims, not a guarantee of uninterrupted operation.

AlphaClaw is a management harness around OpenClaw. Its browser dashboard handles setup, provider credentials, agent navigation and channel pairing, while its watchdog monitors the gateway, detects crash loops and can run OpenClaw’s repair command before relaunching it. Git-backed workspace sync and rollback provide another recovery route. It is neither a new model nor a plugin installed into a coding editor.

Installation still brings hosting and account requirements

The tagged README targets Docker/Linux deployments, with Render and Railway templates or the npm route npm install @chrysb/alphaclaw followed by npx alphaclaw start. It explicitly says macOS local development is not yet supported, despite also showing a macOS download link.

Users set a setup password, connect model-provider credentials or the supported Codex OAuth flow, and supply a GitHub token and repository for workspace sync. Railway instructions call for the Hobby plan with at least 8 GB of RAM. The MIT license covers the software; it does not make cloud hosting or model usage free.

The updated picker recommends Claude 5.5, GPT-6.1 Sol, GPT-6 Astra/Luna and Gemini 3.8 Flash while retaining older choices. That is an application recommendation list, not a model launch or a comparative performance result.

The dashboard is an administrative surface

The documentation says AlphaClaw trades some default OpenClaw hardening for easier setup, including automatic approval of the first CLI pairing. Its optional OpenAI-compatible proxy is disabled by default. When enabled, the gateway bearer token grants operator access to whatever tools the configured agent allows, so the project says to keep it with trusted backend callers rather than distribute it to end-user clients.

Those boundaries matter for the workflow being sold: a browser can manage files, integrations and agent execution, not just display a chat. The release makes that administrative workflow easier to authenticate and restart; it does not establish a new security isolation boundary.