Samuel KandGitHub
b2229a28b9
* fix(server): reset session ID on query restart to prevent overwrite crash When ensureQuery() restarts a query, the old claudeSessionId was retained. If the new query landed on a different Claude session (e.g. after a hook or reconnect), captureSessionIdFromMessage() would detect the mismatch and throw a fatal "session ID overwrite" error, killing the agent mid-turn. Reset claudeSessionId and persistence during query restart so the new session can establish its own identity cleanly. Closes #200 * fix(server): recover from session ID overwrite and load projects instantly - Reset claudeSessionId unconditionally before every new query creation, not just on explicit restarts. Fixes unrecoverable crash loop where a pump failure left stale session ID, causing every subsequent query to immediately throw the overwrite error again. - Decouple fetch_workspaces_request from reconciliation: serve registry snapshot immediately instead of awaiting git operations on all workspaces. Background reconciliation runs after response is sent and pushes workspace_update events for any changed workspaces (e.g. stale worktrees getting archived). * fix(server): auto-resume Claude session after overwrite error to preserve history When the query pump dies (e.g. after a session ID overwrite error), preserve claudeSessionId so the next query automatically passes resume: sessionId to the Claude SDK. Claude responds with the same session ID, the overwrite check passes, and the conversation history is intact. Previously claudeSessionId was reset unconditionally before every new query, causing the next query to start a fresh session and lose the conversation. Now it is only reset for explicit restarts (queryRestartNeeded), where a fresh session is the intended behavior. * fix(server): reset session ID before throwing overwrite error to break retry loop When the overwrite error fired, claudeSessionId was left set to the old value. Our auto-resume fix then passed resume: oldSessionId on every retry, Claude returned yet another new session ID each time, and the overwrite error looped indefinitely (same "Existing" UUID across all failures in the log). Fix: reset claudeSessionId = null in both captureSessionIdFromMessage and handleSystemMessage before throwing, so the next query starts a fresh session instead of looping on a dead resume target. Auto-resume still works for legitimate pump failures (network drops etc.) since those exit without throwing, leaving claudeSessionId intact. * fix(server): accept session ID change mid-stream instead of failing the turn Hooks can cause Claude to restart with a new session ID mid-turn. Previously both captureSessionIdFromMessage and handleSystemMessage threw a CRITICAL error when the session ID changed, failing the turn and leaving the user with an error message on what should have been a transparent hook execution. Now both paths log a warning and accept the new session ID, allowing the turn to continue uninterrupted through hook-triggered subprocess restarts.
Paseo
One interface for all your Claude Code, Codex and OpenCode agents.
Run agents in parallel on your own machines. Ship from your phone or your desk.
- Self-hosted: Agents run on your machine with your full dev environment. Use your tools, your configs, and your skills.
- Multi-provider: Claude Code, Codex, and OpenCode through the same interface. Pick the right model for each job.
- Voice control: Dictate tasks or talk through problems in voice mode. Hands-free when you need it.
- Cross-device: iOS, Android, desktop, web, and CLI. Start work at your desk, check in from your phone, script it from the terminal.
- Privacy-first: Paseo doesn't have any telemetry, tracking, or forced log-ins.
Getting Started
Paseo runs a local server called the daemon that manages your coding agents. Clients like the desktop app, mobile app, web app, and CLI connect to it.
Prerequisites
You need at least one agent CLI installed and configured with your credentials:
Desktop app (recommended)
Download it from paseo.sh/download or the GitHub releases page. Open the app and the daemon starts automatically. Nothing else to install.
To connect from your phone, scan the QR code shown in Settings.
CLI / headless
Install the CLI and start Paseo:
npm install -g @getpaseo/cli
paseo
This shows a QR code in the terminal. Connect from any client. This path is useful for servers and remote machines.
For full setup and configuration, see:
CLI
Everything you can do in the app, you can do from the terminal.
paseo run --provider claude/opus-4.6 "implement user authentication"
paseo run --provider codex/gpt-5.4 --worktree feature-x "implement feature X"
paseo ls # list running agents
paseo attach abc123 # stream live output
paseo send abc123 "also add tests" # follow-up task
# run on a remote daemon
paseo --host workstation.local:6767 run "run the full test suite"
See the full CLI reference for more.
Orchestration skills (Unstable)
Experimental skills that teach agents how to use the Paseo CLI to orchestrate other agents. I am updating these very frequently as I learn new things, expect changes without notice, might be coupled to my own setup, use at your own risk.
npx skills add getpaseo/paseo
Then use them in any agent conversation:
# Use handoff when you discuss something with an agent but want another one to implement.
# I use this to plan with Claude and then handoff to Codex to implement.
/paseo-handoff hand off the authentication fix to codex 5.4 in a worktree
# Use loops when you have clear acceptance criteria (aka Ralph loops).
/paseo-loop loop a codex agent to fix the backend tests, use sonnet to verify, max 10 iterations
# Orchestrator teaches the agent how to create teams and manage them via a chat room.
# Very opinionated and expects both Codex and Claude to work.
/paseo-orchestrator spin up a team to implement the database refactor, use chat to coordinate. use claude to plan and codex to implement and review
Development
Quick monorepo package map:
packages/server: Paseo daemon (agent process orchestration, WebSocket API, MCP server)packages/app: Expo client (iOS, Android, web)packages/cli:paseoCLI for daemon and agent workflowspackages/desktop: Electron desktop apppackages/relay: Relay package for remote connectivitypackages/website: Marketing site and documentation (paseo.sh)
Common commands:
# run all local dev services
npm run dev
# run individual surfaces
npm run dev:server
npm run dev:app
npm run dev:desktop
npm run dev:website
# build the daemon
npm run build:daemon
# repo-wide checks
npm run typecheck
License
AGPL-3.0