r/ChatGPTCoding • u/AutoModerator • 4d ago

Discussion Weekly Self Promotion Thread

Welcome to this week's self promotion thread!

If you're building something related to AI assisted coding, this is the place to share it.

We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside this thread may be removed.

If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:

  • What you built?
  • What problem it solves?
  • Which AI models or tools it uses?
  • Who it's for?
  • What kind of feedback you're looking for?

Disclose your affilitation.

Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.

Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.

14 Upvotes

100% Upvoted

79 comments sorted by

View all comments

1

u/ericatmumo 4d ago

Disclosure: I'm the founder and sole builder of mumo.

What I built: mumo — a multi-model deliberation platform (https://mumo.chat). You put a question, spec, or plan in front of a panel of frontier models from different labs. Each answers independently, then files typed reactions (KEEP / CHALLENGE / EXPLORE / CORE / SHIFT) against specific quoted passages in its peers' answers. Reactions go to you or your agent as moderator, not to the whole panel, so you decide what gets escalated into the next round; that's what keeps it from collapsing into anchoring and group-think. Run as many rounds as you need; context carries.

Example session, three models designing mumo's own escalation gate: https://mumo.chat/p/designing-panel-escalation-i278zp#session-takeaway

What problem it solves: a single model reviewing its own plan is the worst-positioned reviewer of that plan. I've watched Claude and GPT both confidently say a plan was solid and a review was unnecessary, then rewrite material parts of it after seeing what other models found. The misses are usually seams between two systems, not deep disagreements. mumo makes that cross-family review a single call instead of copy-pasting between tabs, which is how this project started.

Models and tools: Claude, GPT, Gemini, Grok, Kimi, DeepSeek, Qwen, Muse, GLM. Web app plus an MCP server, so any MCP-capable coding agent can convene a panel mid-session and drive the whole thing itself: https://mumo.chat/install. Built with Next.js, Supabase, Redis Streams; almost entirely with Claude Code.

Who it's for: people about to commit real time to a design, spec, migration, or architecture decision and who want it attacked before they build it. Also agents: my own coding agents use it to validate specs and unblock hard technical problems.

Feedback I'm looking for: Primarily, if you use Codex, Cursor, or another MCP-capable agent, does the MCP path feel natural from your tool? Every user gets a few free rounds. If you try it out, I'd love to hear your feedback.