Familiar for Paseo

One creature. Any brain.

A persistent fantasy companion whose identity, Soul, Memory, Growth, and Bond continue when you change AI providers.

Familiar is a community feature fork of Paseo, kept inside Paseo's existing app, daemon, provider abstraction, and local storage architecture. It is not a separate chatbot and does not depend on one model's proprietary memory.

What Familiar adds

• Per-conversation choice: invite your Familiar into a conversation or leave it as an ordinary Paseo session. Disabled turns receive no Familiar context and do not develop Familiar state.
• Model-agnostic continuity: switch Brain while keeping the same identity, approved memories, working style, project context, and shared history.
• Local, inspectable ownership: Memory includes scope, confidence, source Brain/model, evidence, and revision history. You can edit, reject, supersede, delete, export, import, or reset it.
• Meaningful development: Growth records real state changes. Bond uses deterministic, deduplicated events rather than message spam or manipulative streaks.
• Guarded identity: models cannot silently rewrite Identity, Soul, or operating behavior. Imported and inferred instructions remain untrusted until reviewed.
• Portable workspace: canonical Markdown identity files and a versioned, sanitized export remain independent of provider credentials.

The complete workflow and current limitations are in the Paseo Familiar user guide. The implementation boundary, privacy model, and context compiler are documented in Paseo Continuity.

Run this fork

Official Paseo downloads do not include this community feature unless it is accepted upstream. Run the fork from source:

git clone https://github.com/lxsolutions/Familiar.git
cd Familiar
npm ci

Start the daemon and app in separate terminals:

npm run dev:server
npm run dev:app

Open the app, connect an existing agent provider, open a conversation, and use Invite in the Familiar header. Development prerequisites and desktop/mobile commands are in docs/development.md.

Paseo foundation

Paseo provides one interface for Claude Code, Codex, Copilot, OpenCode, and Pi agents. Familiar preserves that multi-provider architecture.

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.

The prebuilt desktop, npm CLI, and Docker distribution instructions below refer to upstream Paseo and do not include the Familiar feature at this time. Use Run this fork to test Familiar.

Prerequisites

You need at least one agent CLI installed and configured with your credentials:

• Claude Code
• Codex
• GitHub Copilot
• OpenCode
• Pi

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.

CLI / headless

Install the CLI and start Paseo:

npm install -g @getpaseo/cli
paseo

Paseo starts locally, 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. This path is useful for servers and remote machines.

For full setup and configuration, see:

• Docs
• Connectivity guide
• Configuration reference

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
paseo --host workstation.local:6767 run "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: paseo CLI for daemon and agent workflows
• packages/desktop: Electron desktop app
• packages/relay: Relay transport and encryption used by the daemon and clients
• packages/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

Related projects

• getpaseo/paseo — the upstream project this feature fork tracks
• getpaseo/paseo-relay — official distributed relay, written in Elixir
• paseo-skins — community themes and a zero-patch desktop theme loader with an Agent Skill
• paseo-vscode — VS Code extension

License

AGPL-3.0-or-later. This fork preserves Paseo's original copyright and license; see LICENSE and the upstream Paseo repository.