* fix(server): name an imported Claude agent after its /rename Importing a Claude session named the agent after its first prompt even when the session had been renamed in the CLI, so the name had to be set again by hand. #4216 fixed the Import Session listing; the imported agent still kept the prompt. Read the last usable `custom-title` from the transcript and pass it as the imported config title. The record is re-emitted on every save, so searching backwards from the end of the file finds the current name without walking a transcript that can reach tens of megabytes. Only an explicit rename is carried over. Agents are named after their first prompt line since #1563, so adopting the generated `ai-title` here would put that LLM summary back. Refs #2513 * refactor(server): drop unused generality from the Claude title reader readLastClaudeTitle took content, type and field so it could read both custom-title and ai-title records, which the listing needed before #4216 took that over. Only the custom-title read is left, so the two extra parameters are dead flexibility that also broke the single-object-parameter rule in packages/server/CLAUDE.md. Collapse it to readLastClaudeCustomTitle(content) and pull the record type into a constant so the needle and the type check share one literal. Hooks skipped: the repo-wide typecheck fails on two pre-existing Electron typing errors in packages/desktop/src/main.ts that reproduce with this change stashed. packages/server typecheck, lint and format all pass. * test(server): drive the real resume path in the import title tests The tests assigned an inline arrow function to client.resumeSession to keep Claude Code from spawning. Importing replays the transcript from disk and never starts a process, so the stub was never needed. Dropping it runs the real resume path, which is what docs/testing.md asks for, and removes the arrow assignment that docs/coding-standards.md rules out. Hooks skipped: the repo-wide typecheck fails on two pre-existing Electron typing errors in packages/desktop/src/main.ts that reproduce with this change stashed. packages/server typecheck, lint, format and the 83 claude tests pass. * fix(server): narrow the transcript read error instead of asserting it The ENOENT check cast the caught value to NodeJS.ErrnoException to reach `code`, which is the kind of assertion docs/coding-standards.md rules out: narrow with `if`, do not silence the compiler. Add the same local type guard pid-lock.ts already uses and test through it. Behaviour is unchanged. A value that is not an Error still falls through to the rethrow, exactly as reading `code` off the assertion did. Hooks skipped: the repo-wide typecheck fails on two pre-existing Electron typing errors in packages/desktop/src/main.ts that reproduce with this change stashed. packages/server typecheck, lint, format and the 83 claude tests pass. * fix(server): let claudeProjectDirSync resolve the Claude config dir The import title reader built the config dir itself through os.homedir(), but os is no longer imported here, so the fallback threw a ReferenceError whenever CLAUDE_CONFIG_DIR was unset. claudeProjectDirSync already resolves the same default. * test(server): give the import title helpers object parameters * fix(server): preserve imported session renames across history locations The import title reader must use the same provider environment and transcript lookup as history replay. Otherwise an imported session has its history but loses its explicit name when its configuration directory or project changed. Co-authored-by: platanus-kr <platanus.kr@gmail.com> --------- Co-authored-by: platanus-kr <platanus.kr@gmail.com> Co-authored-by: paseo-bot[bot] <266920839+paseo-bot[bot]@users.noreply.github.com>
Paseo
One interface for Claude Code, Codex, Copilot, OpenCode, Pi, Antigravity, and Muse Code agents.
Paseo is an open source agentic development environment for desktop, mobile, web, and CLI. Open the desktop app and work: agents, editor, terminals, diffs, pull requests, and a browser in one window. Run many agents at once, each in its own worktree, on one machine or several. The mobile app is the full app, native on iOS and Android.
- Parallel agents: Run many agents at once, each in its own worktree.
- Built-in orchestration: Agents in Paseo can create worktrees, launch other agents, and talk to them, across providers.
- Complete development workflow: Edit files, review diffs, open pull requests, and run terminals, in split panes you arrange how you want.
- 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, Copilot, OpenCode, Pi, Antigravity, and Muse Code 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.
Run parallel tasks in Paseo: start agents in separate worktrees, review their diffs, run each app, and check it in the built-in browser.
Sponsors
Cloud coding agents |
Become a sponsor | Become a sponsor |
Plugins
Plugins run on the daemon and show up in every client you connect, with the same UI on desktop, web, iOS, and Android. Write a plugin once and it is on your phone.
- UI: screens, sidebar items, workspace panels, Command Center items, slash commands, composer pills, attachment sources, timeline items, themes.
- Agent lifecycle: change configuration, environment, and MCP servers, answer permissions, follow up when a turn ends.
- Providers: add a coding agent as a provider.
Install from the registry with paseo plugin add owner/slug, or from Git or a local directory.
Plugins run with access to your daemon machine and inside connected clients; install only code you trust.
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, open Settings → your host → Pair Device.
Server
For a server, a VM, or any machine without the desktop app. Install the CLI and start the daemon:
npm install -g @getpaseo/cli
paseo
Paseo starts, then asks whether to enable the end-to-end encrypted relay for device pairing. If you decline, connect directly over TCP, Tailscale, or another VPN. The desktop, mobile, and web apps connect to this daemon like any other host.
For full setup and configuration, see:
Docker
Run the Paseo daemon and self-hosted web UI in Docker:
docker run -d --name paseo \
-p 6767:6767 \
-e PASEO_PASSWORD=change-me \
-v "$PWD/paseo-home:/home/paseo" \
-v "$PWD:/workspace" \
ghcr.io/getpaseo/paseo:latest
Open http://localhost:6767 after it starts. Extend the base image with the agent CLIs you use, then provide credentials through environment variables or the persistent /home/paseo volume. See the Docker documentation for full setup details.
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.5 --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; --cwd is a path on that host
paseo run --host workstation.local:6767 --cwd /workspace "run the full test suite"
See the full CLI reference for more.
TypeScript SDK
Build issue integrations, dashboards, and orchestration services with @getpaseo/client:
import { createPaseoClient } from "@getpaseo/client";
const client = createPaseoClient({ url: "ws://127.0.0.1:6767/ws" });
await client.connect();
const agent = await client.agents.create({
config: { provider: "codex/gpt-5.5" },
cwd: "/Users/me/dev/storefront",
prompt: "Review the current diff and name the riskiest change.",
});
const result = await agent.waitForFinish();
console.log(result.lastMessage);
await client.close();
See the SDK quickstart, recipes, and API reference.
Skills
Skills teach your agent to use Paseo to orchestrate other agents.
npx skills add getpaseo/paseo
Then use them in any agent conversation:
/paseo-handoff— hand off work between agents. I use this to plan with Claude and then handoff to Codex to implement./paseo-advisor— spin up a single agent as an advisor for a second opinion, without delegating the work itself./paseo-committee— form a committee of two contrasting agents to step back, do root cause analysis, and produce a plan.
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 transport and encryption used by the daemon and clientspackages/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 server stack
npm run build:server
# repo-wide checks
npm run typecheck
Support Paseo
Paseo is an independent project used by tens of thousands of developers daily, built by one person and funded by the people who use it. Support the work on GitHub Sponsors. Companies can sponsor Paseo monthly and have their logo shown at the top of this README and on the paseo.sh homepage and docs.
Related projects
- getpaseo/paseo-relay — official distributed relay, written in Elixir
- paseo-vscode — VS Code extension
License
Apache-2.0

