Files
picoclaw/web
Liu Yuan 11207186c8 fix: proxy WebSocket through web server port (#1665)
- Modify buildWsURL to use web server port (18800) instead of gateway port (18790)
- Add WebSocket proxy handler to forward /pico/ws to gateway
- Gateway port is read from config (cfg.Gateway.Port), defaults to 18790
- This allows WebSocket connections through the same port as the web UI,
  avoiding the need to expose extra ports for Tailscale/Docker
2026-03-17 17:36:06 +08:00
..

Picoclaw Web

This directory contains the standalone web service for picoclaw. It provides a complete unified web interface, acting as a dashboard, configuration center, and interactive console (channel client) for the core picoclaw engine.

Architecture

The service is structured as a monorepo containing both the backend and frontend code to ensure high cohesion and simplify deployment.

  • backend/: The Go-based web server. It provides RESTful APIs, manages WebSocket connections for chat, and handles the lifecycle of the picoclaw process. It eventually embeds the compiled frontend assets into a single executable.
  • frontend/: The Vite + React + TanStack Router single-page application (SPA). It provides the interactive user interface.

Getting Started

Prerequisites

  • Go 1.25+
  • Node.js 20+ with pnpm

Development

Run both the frontend dev server and the Go backend simultaneously:

make dev

Or run them separately:

make dev-frontend   # Vite dev server
make dev-backend    # Go backend

Build

Build the frontend and embed it into a single Go binary:

make build

The output binary is backend/picoclaw-web.

Other Commands

make test    # Run backend tests and frontend lint
make lint    # Run go vet and prettier/eslint
make clean   # Remove all build artifacts