claudegoodies
CLAUDE.md

paseo CLAUDE.md

From getpaseo

Paseo is a mobile app for monitoring and controlling your local AI coding agents from anywhere. Your dev environment, in your pocket. Connects directly to your actual development environment — your co

Maps the Paseo monorepo's packages and docs directory for agents working on its codebase.

Use it when

  • Contributing code to the Paseo repo itself
  • Need to locate docs on architecture, agent lifecycle, or WebSocket protocol
  • Adding a new agent provider (Claude Code, Codex, Copilot, OpenCode, Pi)
  • Working on forms, hover patterns, or Unistyles theming in packages/app

Skip it if

  • Not developing inside the Paseo repository
  • Looking for a general-purpose tool rather than project-specific instructions
  • Not using npm workspaces, Expo, or Electron stack Paseo is built on

Facts

Repository
getpaseo/paseo
Status
Actively maintained
Last commit
Source file
CLAUDE.md

Source preview

The instructions Claude Code reads when this claude.md runs.

# CLAUDE.md

Paseo is a mobile app for monitoring and controlling your local AI coding agents from anywhere. Your dev environment, in your pocket. Connects directly to your actual development environment — your code stays on your machine.

**Supported agents:** Claude Code, Codex, GitHub Copilot, OpenCode, and Pi.

## Repository map

This is an npm workspace monorepo:

- `packages/server` — Daemon: agent lifecycle, WebSocket API, MCP server
- `packages/app` — Mobile + web client (Expo)
- `packages/cli` — Docker-style CLI (`paseo run/ls/logs/wait`)
- `packages/relay` — E2E encrypted relay for remote access
- `packages/desktop` — Electron desktop wrapper
- `packages/website` — Marketing site (paseo.sh)

## Docs

`docs/` is the source of truth for system-level and process-level knowledge. **"The docs", "check the docs", or "check the X docs" always mean this directory — not the web.** Look here before fetching anything online; the docs capture gotchas and conventions you cannot derive from the code or external sources.

At the start of non-trivial work, list `docs/` and skim anything relevant to the task. When you learn something meta worth preserving — a gotcha, a convention, a workflow, a piece of system context that will outlive the current task — update an existing doc or propose a new one. Code-level facts belong in inline comments next to the code; system, process, and gotch
View full source on GitHub →

Other claude.md files