AliceLJY

Openclaw Tunnel — Productivity skill for Claude Code

Productivity community

Authenticated task-queue bridge for OpenClaw to run Claude Code and Codex across trusted network boundaries; not a sandbox.

How to install Openclaw Tunnel

This entry records only its repository, not the path inside it, so there is no exact command to give. Open AliceLJY/openclaw-tunnel and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Openclaw Tunnel does

Authenticated task-queue bridge for OpenClaw to run Claude Code and Codex across trusted network boundaries; not a sandbox.

Alternatives in Productivity

  • Octoboss Reorganize Todos — You are the Octoboss — a cross-tentacle orchestrator 1.4k ★
  • Agentlas Network — Staff a task from registered Local, owner Cloud, and public Hub agents 1.1k ★
  • Agentacct — See what your coding agents did and what it cost 665 ★

README

openclaw-tunnel

**Run AI Coding Agents from Anywhere — Docker, Cloud, or Hybrid**

*An authenticated HTTP(S) task-queue bridge that lets OpenClaw dispatch tasks to Claude Code and Codex across container boundaries, network boundaries, or both.*

[![MIT License](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE) [![Node.js](https://img.shields.io/badge/Node.js-≥22.5-339933?logo=node.js)](https://nodejs.org) [![Docker](https://img.shields.io/badge/Docker-Compose-2496ED?logo=docker)](https://docs.docker.com/compose/)

**English** | [简体中文](README_CN.md)


**Status: Maintenance mode.** In the author's own setup the OpenClaw plugin's slash-command path is retired; the live path is now containers calling `task-api` directly over a local/private network (see "Two Ways to Connect" below). The plugin still works and remains the recommended entry point for OpenClaw users.

**On the Gemini path.** Google retired the standalone `gemini` CLI for personal accounts (free, AI Pro, AI Ultra) on 2026-06-18; its successor is the Antigravity CLI (`agy`), which this runner does not spawn. The `/gemini` command family and `GEMINI_PATH` are kept for Code Assist Standard/Enterprise users who still have a working legacy binary — on a personal account that path can no longer authenticate. Claude Code and Codex are unaffected.


Why tunnel?

[acpx](https://github.com/openclaw/acpx) is the official OpenClaw CLI client built on the [Agent Client Protocol](https://agentclientprotocol.com/) (ACP). It spawns the CLI as a local child process over stdio. If OpenClaw and Claude Code are on the same machine, acpx is the right choice.

**The problem:** when OpenClaw runs in Docker or on a remote server, acpx cannot reach a CLI on another machine. ACP is a stdio protocol with no network transport. Remote ACP is still "work in progress" in the spec.

**What tunnel does:** instead of waiting for remote ACP, tunnel bridges the gap wi