Mohamed BoudraandGitHub
617cf8a7bf
* refactor(server): extract voice mode subsystem into VoiceSession session.ts was a 10.5k-line god object and the most-churned file in the repo. ~1,100 of those lines were an entire voice/audio subsystem — the STT/TTS/dictation managers, the barge-in audio-buffering state machine, voice-turn orchestration, and the MCP voice bridge — interleaved field by field and method by method with workspace/git/agent/provider concerns. Move the whole subsystem into a new VoiceSession deep module. Session now holds one `voiceSession` field, constructs it once, and delegates the voice/dictation/abort message types, the permission auto-allow gate, and cleanup to it. VoiceSession owns all 18 voice fields and ~25 methods and reaches back into the agent run only through a narrow VoiceSessionHost seam (emit, loadAgent, reloadAgentSession, sendSpokenInput, interruptAgentIfRunning, hasActiveAgentRun). Behavior is preserved (verbatim method moves); deleting voice-session.ts now removes the feature mechanically. The voice unit tests drive the VoiceSession boundary instead of reaching into Session internals, so future voice tests can construct a VoiceSession with a fake host. session.ts: 10,468 -> 9,272 lines. * refactor(server): move VoiceSession into voice/ and test it at the boundary Address Greptile review on #1640: - Move voice-session.ts into the existing voice/ subdirectory, alongside voice-turn-controller.ts, instead of adding another peer to the 30+ file server/ directory. The directory now carries the domain. - Add voice/voice-session.test.ts beside the module: it constructs a VoiceSession with a fake VoiceSessionHost and drives it through the public API (handleSetVoiceMode, then turn-detection/STT events), asserting on the host seam (sendSpokenInput) and emitted messages. No Session, no private field/method access. - Remove the voice tests from session.test.ts that reached through Session's private voiceSession field into VoiceSession internals. Same three behaviors are covered (streaming final -> agent, finalization timeout empty path, low-confidence filtering); driving handleSetVoiceMode additionally exercises the enable path the old tests bypassed.
Paseo
One interface for Claude Code, Codex, Copilot, OpenCode, and Pi agents.
Note
I'm a solo maintainer and don't always keep up with GitHub Issues daily. If something is urgent or blocking you, Discord is the fastest place to reach me.
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, Copilot, OpenCode, and Pi 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.
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-loop— loop an agent against clear acceptance criteria (aka Ralph loops), optionally with a verifier./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 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 server stack
npm run build:server
# repo-wide checks
npm run typecheck
Community
- paseo-relay — self-hosted relay in Go
License
AGPL-3.0