This project provides a lightweight, browser-based remote tool for interacting with Claude Code (Claude) and Codex CLIs. It targets users needing to manage AI code generation tasks on resource-constrained servers or access them remotely via a web interface. The primary benefit is enabling efficient, background-persistent interaction with powerful CLI agents through an optimized, lightweight web UI, supporting both Linux and Windows environments.

How It Works

The architecture employs a WebSocket connection between the browser frontend and a Node.js backend (server.js). The backend manages CLI agent processes (Claude or Codex) as detached child processes (detached: true, proc.unref()) to ensure they continue running even if the browser or Node.js server restarts. Communication between the Node.js server and the CLI agents occurs via file I/O, with process state and output streamed back to the frontend using a FileTailer. This design minimizes resource overhead and allows for robust background task execution and recovery.

Quick Start & Requirements

• Primary install/run command:
  • Linux/macOS: git clone https://github.com/ZgDaniel/cc-web.git && cd cc-web && npm install && npm start
  • Windows: git clone https://github.com/ZgDaniel/cc-web.git && cd cc-web && npm install && start.bat
• Prerequisites: Node.js >= 18, Claude Code CLI (@anthropic-ai/claude-code) installed globally, Codex CLI (@openai/codex) installed globally.
• Access: http://localhost:8002 (default port).
• Docs: README provides detailed configuration and deployment instructions.

Highlighted Details

• Ultra-lightweight: Minimal backend resource consumption and a streamlined web frontend.
• Background Task Persistence: CLI agents continue running after browser closure, with optional notifications (PushPlus, Telegram, Server酱, Lark, QQ) upon completion.
• Multi-Session Management: Create, switch, rename, and delete sessions, with local history import from ~/.claude/projects or ~/.codex/sessions.
• Multi-API & Config: Supports switching between multiple API configurations and saving SSH host/GitHub token details for remote management.

Maintenance & Community

The project acknowledges contributions and guidance from specific individuals and groups, including @carroxaitech, @YoungHong1992, @123aliez, @lytxsy, and inspiration from linux.do. No explicit links to community channels (Discord, Slack) or a public roadmap are provided in the README.

Licensing & Compatibility

The license type is not explicitly stated in the provided README content. This absence requires clarification for commercial use or integration into closed-source projects.

Limitations & Caveats

The project defaults to listening only on 127.0.0.1 for security, requiring explicit configuration changes (e.g., to 0.0.0.0) or the use of reverse proxies (Nginx, Tailscale, Cloudflare Tunnel) for LAN or remote access, which adds setup complexity. The lack of a stated license is a significant adoption blocker.