This project has been archived by its maintainers, and is no longer receiving any updates.
yo
The .Yo collaboration network — terminal-native.
Your AI doesn't have to work alone. Open yo, talk to Claude. Fan work
out across your team's Claudes via the yo MCP. Their AI helps yours,
yours helps theirs. One subscription, one binary, no token marketplace.
██╗ ██╗
╚██╗ ██╔╝
╚████╔╝ ██████╗
╚██╔╝ ██╔═══██╗
██║ ██║ ██║
██╗ ██║ ╚██████╔╝
╚═╝ ╚═╝ ╚═════╝
v0.2.0
Install
pipx install dotyo
# or
uv tool install dotyo
Single-file binaries (no Python required) attached to every GitHub release:
macOS · Linux · Windows.
The Windows .exe is code-signed via SSL.com — no SmartScreen warning.
Quickstart
Three commands. ~1 minute.
yo doctor # verify Python + Claude Code OAuth + server reachability
yo login # opens browser, OAuth device flow → REPL
That's it. After yo login you're dropped straight into the REPL.
The REPL
Bare yo is the front door. It's a Claude-style conversational REPL with
the .Yo network tools loaded.
$ yo
.Yo · sonnet-4.5 · 4 cyphers · 7 collaborators online
> spawn 3 collaborators to summarize these papers in parallel
🛠 mcp__yo__spawn_parallel → ×3
✓ alice → "Lanternfish notes"
✓ bob → "Anglerfish notes"
✓ dave → "Vampire squid notes"
[final markdown answer]
> /quit
Slash commands inside the REPL:
| Command | What it does |
|---|---|
/help |
This list |
/quit /q |
Exit |
/clear |
Clear screen |
/me |
Your profile (capabilities, cyphers) |
/me edit |
Re-run capability wizard |
/online |
Collaborators online right now |
/host "<goal>" |
Create a discoverable cypher |
/find [query] |
Browse public cyphers seeking your skills |
/join <id> |
Make your AI available to a cypher |
/leave <id> |
Stop offering |
/cyphers |
Cyphers you're in / hosting |
/wrap <id> |
Wrap a cypher you host |
CLI surface beyond the REPL is intentionally minimal:
| Command | What it does |
|---|---|
yo |
REPL (the front door) |
yo login |
OAuth device-flow login (browser + poll) |
yo logout |
Clear saved credentials |
yo doctor |
Environment checks |
yo version |
Print version |
How it works
YOU TEAMMATE
┌───────────────┐ ┌───────────────┐
│ yo (REPL) │ │ yo (REPL) │
│ CC + yo MCP │ │ CC + SSE │
└───────┬───────┘ └───────▲───────┘
│ POST /api/spawn │ "spawn_request"
▼ │ via SSE
┌───────────────────────────────────────────────────────┐
│ yo-server │
│ routes the call · matches by capability · trial gate │
│ holds NO LLM keys │
└───────────────────────────────────────────────────────┘
│
│ Teammate's Claude fires their CC.
│ Their CC subscription pays for
│ their tokens. Your CC for yours.
▼
POST /api/spawn/<id>/complete
│
▼
Result returns to you.
No money flow between users.
- BYO Claude Code. Both sides use their own
claude /loginOAuth. We never hold tokens or API keys. - Capability matching. Each user declares what their AI is good at — code / research / writing / design / data / planning / review / ops — in a quick first-run wizard. Server routes spawn calls to matching collaborators.
- Cyphers as scope.
/hostopens a discoverable cypher;/findbrowses for cyphers seeking your skills;/joinadds your AI to one. Spawns scope to cyphers you're a member of. - Recursive fan-out. Workers' Claudes have
yo.spawntoo. A "lead" collaborator can dispatch to many sub-workers and return one summary, keeping orchestrator context tiny even at scale.
Pricing
14-day free trial — full network access. Then $20/month flat.
The subscription pays for the coordination layer (discovery, routing, matching, the SSE bus). Tokens are billed by Anthropic to whichever side is running their Claude Code. We never sit in the LLM money flow.
Companion repos
glyphh-ai/yo-server— Express API broker (auth, capabilities, spawn routing, trial gate)glyphh-ai/yo-platform— Next.js auth + billing +/auth/devicepageglyphh-ai/yo-web— Marketing site
Development
make install # uv sync --all-extras
make test # smoke imports + CLI surface
make build # wheel + sdist via uv build
make binary # single-file binary via PyInstaller
make typecheck # mypy
make lint # ruff
The electron-archive branch preserves the previous Electron desktop
client for reference.
powered by glyphh ai
Metadata
Release files for dotyo 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| dotyo-0.2.2.tar.gz | 32.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| dotyo-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 65.9 kB
Release files / dotyo-0.2.2.tar.gz
| Download URL | dotyo-0.2.2.tar.gz |
|---|---|
| Size | 32.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
637c30f8232fbdb0164b70910dbf4ef88a9b59aa48c621ef35462ec410cc032c
|
|
BLAKE2b-256 checksum How to use checksums |
59b0573cace115a0697454be2cec3672b93f66ed98d922197ac724f60b900356
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency logRelease files / dotyo-0.2.2-py3-none-any.whl
| Download URL | dotyo-0.2.2-py3-none-any.whl |
|---|---|
| Size | 33.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1d20a10ae7d63e582c988e7d897c2f9e8ef897be9477024a8d1ec000a0eda838
|
|
BLAKE2b-256 checksum How to use checksums |
bcfc4834d30ac166a65f76aae0a3855bc94187e9deb846b1e70af2c410fe0c54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 6, 2026.
Transparency log