openclaw-cli-bridge-elvatis

What This Skill Does

The openclaw-cli-bridge-elvatis skill serves as a sophisticated middleware layer that integrates your locally installed AI CLI tools directly into the OpenClaw environment. By acting as an OpenAI-compatible HTTP proxy on 127.0.0.1:31337, it allows OpenClaw to treat external CLI-based models (such as those from Gemini and Claude) as first-class vllm model providers. This eliminates the need for redundant API configurations or custom web integrations. It specifically utilizes an E2BIG-safe spawn methodology, passing prompts via stdin or temporary files rather than command-line arguments, ensuring that even complex, multi-turn conversational sessions do not trigger system limit errors.

Installation

1. Ensure you have the required local CLI clients (Codex, Gemini, and Claude Code) configured and authenticated on your system.
2. Open your OpenClaw terminal and run the installation command: clawhub install openclaw/skills/skills/homeofe/openclaw-cli-bridge-elvatis.
3. Restart your OpenClaw gateway to initialize the proxy service.
4. If you utilize Codex, run openclaw models auth login --provider openai-codex to register your existing ~/.codex/auth.json credentials without re-authenticating.

Use Cases

• Unified Development Workflow: Switch between Claude Sonnet for complex refactoring and Gemini 3-Pro for deep logic analysis without leaving the OpenClaw UI.
• Large Payload Management: Leverage the E2BIG-safe stdin transport to pipe massive codebases or long documentation files into high-performance CLI models without command-line buffer overflows.
• Rapid Prototyping: Test different model behaviors during an active session using the atomic slash command interface for instant A/B testing of responses.

Example Prompts

1. "/cli-sonnet Refactor this React component to use functional hooks and improve memoization."
2. "/cli-gemini-flash Analyze these logs and identify the root cause of the connection timeout."
3. "/cli-opus Explain how this architectural pattern fits into our existing microservices deployment."

Tips & Limitations

• Permissions: Slash commands are restricted to authorized senders; ensure your environment is correctly scoped if working in a team workspace.
• Performance: The proxy adds a negligible overhead compared to raw CLI usage but ensures seamless synchronization with OpenClaw state management.
• Recovery: Use /cli-back to return to your previous model after a quick test run.
• Security: Because this tool proxies local CLI requests, ensure your local authentication tokens are stored with appropriate system permissions.