@a-t-h-i/bot-lobby

Structured multi-agent software engineering orchestrator for Pi

Packages

Package details

extension

Install @a-t-h-i/bot-lobby from npm and Pi will load the resources declared by the package manifest.

npm repo home report

$ pi install npm:@a-t-h-i/bot-lobby

Package: @a-t-h-i/bot-lobby
Version: 0.6.47
Published: Oct 14, 2026
Downloads: 8,297/mo · 2,607/wk
Author: a-t-h-i
License: Apache-2.0
Types: extension
Size: 2.9 MB
Dependencies: 0 dependencies · 4 peers

Pi manifest JSON

{
  "image": "https://raw.githubusercontent.com/a-t-h-i/bot-lobby/main/.github/screenshots/lobby.png",
  "extensions": [
    "./src/index.ts"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

Bot-Lobby

A Pi extension for multi-agent software development. Describe a change, agree on a plan with the oracle, and follow the agents in a local browser lobby. Approvals, domain boundaries and QA are enforced before anything is called done.

Install

pi install npm:@a-t-h-i/bot-lobby

Try it first with pi -e npm:@a-t-h-i/bot-lobby, or from a checkout with pi -e ./src/index.ts. The questionnaire and web tools are built in, so don't also install extensions with the same tool names. Requires Pi 1.0.x (1.0.1 or later).

Use

In Pi, run /bot-lobby add a login page. The lobby opens in your browser. Ctrl+Shift+M or /bot-lobby on|off switches bot-lobby on or off; a new Pi session starts with it off.
Answer the oracle's questions and approve its plan, or agree on one with the panel in Plan first.
Follow the agents in Lobby and Tasks. Their steps fold into one line in the conversation and open in place.

Small changes go to Quick fix. --task forces a full task, --fast / --full picks the workflow, and --branch / --worktree isolates it in git. Workers never commit: the oracle commits only the files the task changed, after the project's linter and a QA pass sized to the change's risk.

The lobby

Lobby: the conversation with the oracle, each run of agent steps inline, and Thinking for their reasoning.
Plan: plan with a panel of agents. View plan (V) opens the draft in a slide-out, where any line takes a comment.
Tasks: every task across sessions as a list or a board, with its steps, timings and Resume.
Git: use the Pull requests / Issues switch to review pull requests or browse open issues through gh. Issues retain descriptions, existing comments, File issue and Plan it; pull-request reviews remain read-only and post nothing.
Knowledge: what each agent has learned about the project, which you can edit, annotate or ask about.

The rail on the left holds settings, the key list, the theme and sounds. The project switcher (P) opens any folder on the machine running bot-lobby. Background sessions still run tasks; follow their progress and use Resume in Tasks, without a separate Sessions conversation page.

Git opens pull requests at #/git and #/git/<number>, and issues at #/git/issues and #/git/issues/<number>. Old #/issues bookmarks redirect to Git. Former Sessions and Excalidraw addresses fall back to Lobby; Excalidraw integration is removed without deleting saved room links or external boards.

The composer appears only on Lobby, Tasks, Plan, Quick fix and Knowledge, including supported detail routes and Knowledge's Docs/Chat views. On Git, Metrics and Settings it stays mounted but hidden and inert, preserving drafts and attachments (including uploads that finish while hidden) without taking space. Phone navigation remains available.

Agent	Does
Oracle	Your Pi session: questions, plan, delegation and approvals
DESIGN	UI, frontend logic, styling and accessibility
DEV	Backend, APIs, data, security and integrations
QA	The final quality gate, at the depth the change's risk calls for
RESEARCH	External facts, with sources

Keys

Every action button shows its key. Alt+1…Alt+9 switch tabs, j / k move through lists, / focuses search or the message box, p switches project, d flips the theme and ? lists every key.

Configuration

Settings live in ~/.pi/bot-lobby/config.json (BOT_LOBBY_CONFIG_DIR moves them), and /bot-lobby config shows what is in effect. Most are also in the lobby's Settings. Tasks and project knowledge stay in .pi/bot-lobby/ inside your project.

The guide covers the rest: delivery and commits, crash recovery, knowledge and shared scripts, the classifier, delegation, time limits, compaction and MCP tools.