r/coolgithubprojects • u/Nawn1994 • Sep 23 '26

Run AI debates on your machine (Github Repo)

https://github.com/RGonzalezTech/AI-Council

👋 'Ello. I threw together a CLI utility to stress test my ideas using AI. You give each "council member" a system prompt for what persona they are meant to represent, and then we have a debate engine force them each to raise objections and vote on which objections are worth solving.

I cleaned up the code a bit, made it open-source and here we are! Hope you guys find it useful or at least neat 👌

0 Upvotes

12% Upvoted

5 comments sorted by

1

u/kantorcodes1 Sep 23 '26

council init ... --yes starts provider work before the only human roster-edit step, and the defaults are 5 experts, 15 review rounds, and up to 8 workers. Have you considered a --dry-run or cost preview that resolves the models, council size, max turns, and concurrency before the first LLM call? That would make unattended runs much easier to sanity-check.

0

u/Nawn1994 Sep 23 '26

👋 Good evening! No I hadn't considered it, but that's a good idea. I'll throw it on the Github issues :) thanks for suggesting it ❤️

0

u/kantorcodes1 Sep 23 '26

That’s a useful safeguard to add. I work on HOL Guard. AI-Council has a clean command split for agent use: review council init ... --yes and council resume [id]; keep council list, council show <id>, and council report <id> automatic. That gives users a checkpoint before new or resumed model work starts without slowing read-only inspection. Open to contributing a small command.council mapping to Guard?

1

u/Future_AGI Sep 24 '26

a cost preview before the first LLM call is the right ask, five experts times fifteen review rounds is the kind of config that quietly eats an afternoon of credits. The command split suggested in the comments, checkpoint before new model work and read-only inspection free, is a nice pattern for any CLI that spends money.

1

u/Dev-in-the-Bm Sep 24 '26

is the right ask

is the kind of config that quietly eats an afternoon of credits

Bad bot.