One thread. Multiple AIs. Deliberation, not polling.
Most people use AI like this: 🤦
- Ask one model → get one answer
- Ask multiple models → compare results
That’s not thinking. That’s polling.
What if the AIs could see each other? 🤔
Not side by side.
Not isolated.
But in sequence — where each one reads what the previous one said before responding.
What This Is
Manual Council is the simplest form of that idea.
No backend.
No orchestration.
No system doing anything for you.
Just you — passing context forward.
How It Works
You act as the router.
- Send your prompt to the first AI
- Take its response
- Paste it into the next AI
- Repeat
Each model inherits the context of the previous one.
Flow
You → Claude → Gemini → GPT → Grok → You
Not parallel.
Not voting.
Sequential awareness.
Coordinated responses
What Changes
- Later models correct earlier ones
- Weak assumptions get exposed
- Ideas evolve instead of resetting
- Disagreement becomes visible
The output starts feeling worked through.
Why This Matters 🧘
Polling gives variation.
Deliberation gives progression.
Manual Council:
- preserves context
- compounds reasoning
- enables interaction between models
The Tradeoff
Yes — it’s manual.
You copy. You paste. You decide the order.
That friction gives:
- control
- visibility
- understanding
Try It
Design a browser-native persistence system that survives tab death without a backend.
Pass responses forward exactly as they are.
What This Could Become
Automation can come later.
This already works.
The Point ✍️
Not which AI is better.
What happens when they think together?
When one model feels off, don’t switch—run a council. 👌
*Live Demo * https://edmundsparrow.github.io/gnoke-council
GitHub: https://github.com/edmundsparrow
Top comments (2)
Good validation just landed.
Open Design dropped a video showing an automated multi-AI council setup. 22k-star project, polished UX — worth watching: m.youtube.com/watch?v=MmTBkDmunk4
The "council of AIs deliberating together" concept is clearly real and people want it.
Gnoke Council is built entirely in the browser — no backend, no CLI, no install. Threads survive tab death via IndexedDB. Files attach and persist. SaveNative writes directly to your filesystem via the File System Access API. I only realised I'd accidentally written a filesystem driver after the council deliberated it into existence.
The browser really is becoming the OS. This is what that looks like before the framework arrives.
Source: github.com/edmundsparrow/gnoke-cou...
The council auto is a planned click-triggered API orchestration layer designed to control when and which AI in the council executes its response, based on user selection.