Jay Rathod

← The lab

Multi-agent AI · Real-time systems

AI Council

A brainstorming room where GPT, Gemini and Claude take turns discussing a problem with you, and remember past discussions.

Status
In development
Type
Personal project · 2026
My role
Solo: design, backend, frontend, hosting

Source on GitHub

3
AI members from three providers
1
writer per discussion: no crossed turns
Self-hosted
on my own server, behind auth

Overview

Asking one model for an answer gives you one perspective. AI Council puts three independent members, GPT, Gemini and Claude, in a room with you. They take strict turns, respond to each other, remember past discussions and keep their own private notes. You can interject by text or microphone at any time, and you always outrank a queued AI turn.

Architecture
  1. 01 · Client React + SSE Live stream; snapshot on reconnect
  2. 02 · API FastAPI Discussion service
  3. 03 · Run Discussion runner Turn state machine; Redis lock
  4. 04 · Context Transcript + memory PostgreSQL as source of truth
  5. 05 · Recall ChromaDB One collection per agent, plus shared
  6. 06 · Speak OpenAI · Gemini · Anthropic Provider adapters

Where it's heading

The goal is structured stages: agents analyse a problem from different angles, challenge assumptions, check feasibility, and end with a written plan covering architecture, constraints, costs and risks. Today it runs as a live discussion room with memory and internet access; the staged workflow is still being built.

Engineering decisions

  1. The backend owns the floor

    Each discussion has exactly one runner loop, the only code that writes its messages. Turn numbers stay sequential, and a Redis lock stops two processes running the same discussion.

  2. The human always outranks the AI

    A message sent mid-turn is queued and recorded before any other agent starts. Pressing the mic holds the floor after the current speaker finishes.

  3. Fail without losing work

    A failing member is skipped and its partial text kept. Retries happen only before text has streamed, so nothing is duplicated. A server restart pauses active discussions so nothing spends credits unattended.

Stack

  • FastAPI
  • React
  • TypeScript
  • Tailwind
  • PostgreSQL
  • ChromaDB
  • Redis
  • SSE
  • Docker
  • Nginx