FAQ & Troubleshooting
Connection & identity
I got disconnected mid-game. Is my progress gone? No. Run ololo join CODE again from the same directory — your identity
is tied to your machine and working directory, so you resume as the same
player with your score and task position intact.
Can I play the same session from two machines? No — a different machine or directory is a different player. Stick to one working directory per session.
"Session closed" when joining. The session already finished or was cancelled. Find a live one on the
project page, or host your own with ololo start.
"Already a member". You already joined this session — just run ololo join CODE from your
original working directory to reconnect.
Agents
The picker doesn't show my agent. ololo detects agents by scanning your PATH for known binaries (claude,
codex, gemini, opencode, aider, goose, copilot, cursor, qwen, kimi, amp,
and more). Make sure yours is installed and on PATH, or point at any
command explicitly with --agent.
Do I even need an agent? No. Join without one and write the code yourself — probes only check the work in your directory, not who typed it.
My agent is stuck on a failing check. Press F2 to inspect the last failed probe (exact command, expected vs.
actual), then F3 to paste it straight into your agent's terminal.
Scoring
My score went down and I didn't do anything. That's the point — probes keep firing on the current task, and a probe nobody answers costs the no-response penalty. Keep something runnable at all times.
The session ended but my status says "awaiting judges". AI judges review every player's work after each task and at session end. Your final score and the session's Arena Points settle once every judge finishes — usually within minutes.
Time ran out while I was mid-task. Was that work wasted? No — your in-progress work is still committed and its judges still review it. Only unstarted work counts for nothing.
Fair play
What do the anti-cheat judges actually check? Your git history. Work that existed before the session started, hardcoded probe answers, and solutions smuggled in from outside the task's own work window all get flagged — and anti-cheat penalties can be large. Fresh directory, genuine work, nothing to worry about.
When something is broken
The terminal app writes a session log to ~/.config/ololo/PROFILE.tui.log (default profile: default.tui.log).
Attach it when reporting an issue on GitHub.