jchristn77/arguebot repository overview

⁠ArgueBot

ArgueBot puts AI agents into a moderated debate. A panel of agents (Claude Code, Codex, Gemini CLI, Mux, or REST models served through Ollama or an OpenAI-compatible endpoint) answers an orchestrator's questions, the orchestrator proposes an answer, and every agent votes. Consensus requires every active agent to agree with the same proposal. You can add context while they work, edit the proposal under vote, change the panel, and read the whole debate afterwards as a transcript.

This image runs the ArgueBot service, which owns all execution and storage, together with the React web dashboard, the native CLI and terminal interface, and pinned Claude Code, Codex and Gemini CLIs.

⁠Run it

Use the Compose file from the repository:

git clone https://github.com/jchristn/arguebot.git
cd arguebot
cp docker/.env.example docker/.env      # optional: port and provider settings
docker compose -f docker/compose.yaml up -d

Then open http://127.0.0.1:4317/dashboard.

Or run the image directly:

docker run -d --name arguebot \
  -p 127.0.0.1:4317:4317 \
  -v arguebot-data:/data \
  -v arguebot-keys:/data/secrets \
  -v arguebot-work:/work \
  jchristn77/arguebot:v2.3.0

⁠First steps

1. Sign in, then on the Participants page open the Secrets tab and add a Claude Code token (claude setup-token) or a Codex login. A container has no Claude Code or Codex login of its own, so command-line agents need a stored secret.
2. Add an agent for each program (Claude Code, Codex, Gemini CLI) and pick its secret, or add an HTTP endpoint and model for Ollama or another provider and an agent on that model.
3. Add models and agents, then start a debate from Conversations.

⁠Image details

Resources (v2.2.0), the markdown documents agents read during debates, are stored in the database, so they need no extra configuration or volume. Questions agents ask you during a debate (v2.3.0) are stored there too; the optional maxLiveQuestionHolds service setting limits how many waiting questions are held open at once (default 4).

Keep the three volumes together across updates. The encryption key on arguebot-keys is what makes stored secrets readable; a database backup without it cannot recover them.

⁠Environment

⁠Signing in

Open http://127.0.0.1:4317/dashboard and sign in. A new data volume starts with the default administrator admin@arguebot with password password and the bearer token arguebotadmin; the sign-in page always shows them. Change the password after you first sign in, then add users and tenants under Administration. Scripts send a bearer token as Authorization: Bearer <token>.

⁠Security

Anyone who can reach the port can try the default credentials, so change the password before exposing the service. Compose publishes the port on 127.0.0.1 only. To reach it from another machine, put it behind HTTPS (a TLS-terminating proxy works) and list the host name in ARGUEBOT_ALLOWED_HOSTS; other host names get 403 invalid_host. Agents run commands and edit files inside the container when local execution is enabled, and members can reveal stored secrets, so give accounts only to people you trust with the workspace.

⁠Learn more

• Docker setup⁠
• Debate guide⁠
• README⁠ and CHANGELOG⁠