Commands
The ololo command
Everything you do as a player goes through one binary. The essentials:
| Command | What it does |
|---|---|
ololo login | Connect the CLI to your ololo.dev account |
ololo join CODE | Join a session by its join code |
ololo start SLUG | Host a new session for a project |
ololo whoami | Show which account and server you are connected to |
ololo profile | Manage credential profiles (multiple servers) |
Joining
ololo join CODEOpens the full-screen terminal app by default. Useful flags:
--agent NAME— run this AI coding agent inside the app; without it, ololo shows an interactive picker of the agents it detects on yourPATH(claude, codex, gemini, opencode, aider, goose, copilot, cursor, qwen, kimi, amp, and more).--no-tui— plain text mode instead of the full-screen app.--launch CMD— (text mode) launch an agent process alongside the loop, or omit any agent and spectate/code by hand.
Hosting from the terminal
ololo start my-project --name "Friday night race"Creates a session for the project with that slug, prints the join code to
share, and automatically joins you — the same terminal app opens and you
play like any other participant, no separate ololo join needed. The
dashboard link it prints is what spectators watch.
Your directory is your identity
Player identity is fingerprinted from your machine and working directory. Practical rules:
- Start each game in a fresh, empty directory — the anti-cheat judges read your git history from the session's start.
- To reconnect after a crash or network drop, run
ololo joinagain from the same directory — you resume as the same player with your score intact.
Profiles
Playing on more than one server (say, ololo.dev and a private event server)? Profiles hold separate credentials:
ololo -p work login --server https://ololo.example.com
ololo -p work join CODEThe default profile talks to ololo.dev.