karpathy/llm-council

LLM Council works together to answer your hardest questions

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 1st, 2026
Created on November 22nd, 2025
Open Issues & Pull Requests: 146 (+0)
GitHub issues: Enabled
Number of forks: 4,330
Total Stargazers: 24,654 (+2)
Total Subscribers: 296 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 70
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 207 days
Stale 30+ days: 62
Stale 90+ days: 32

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

LLM Council is a local web application that queries multiple large language models simultaneously and synthesizes their responses through a structured deliberation process.

The tool addresses the problem of choosing between different LLM providers by eliminating that choice entirely. Instead of picking a single model, users submit queries to a council of LLMs running in parallel. The workflow unfolds in three stages: first, all models generate independent responses to the user's question; second, each model reviews and ranks the others' answers with anonymized identities to prevent bias; third, a designated Chairman model synthesizes all responses and rankings into a final consolidated answer. Users can inspect individual model outputs in a tabbed interface before seeing the chairman's synthesis.

The project suits developers and researchers who want to evaluate multiple LLM providers side by side or who value diverse perspectives on complex questions. It works best for exploratory use cases where seeing multiple viewpoints and their cross-evaluations provides value, rather than for production systems requiring single-model consistency. The tool uses OpenRouter as its LLM provider, so access depends on having an OpenRouter account with sufficient credits. The tech stack is straightforward: FastAPI and async httpx on the backend, React with Vite on the frontend, and JSON file storage for conversations.

The project was built as an experimental weekend exploration rather than a production system. The creator explicitly states it was vibe coded for personal use and is provided as-is without ongoing support or maintenance plans. The codebase is intentionally left in an exploratory state, with the expectation that users will modify it themselves or ask LLMs to adapt it to their needs rather than relying on upstream improvements.