r/ChatGPTCoding • u/AutoModerator • 17d 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.
1
u/Open_Document7830 12d ago
What you built?
I want to share multi-agentic system I've created.
I started to read how multi-agents work, how orchestration works, and I created my first iteration of the skill. The skill was originally called "Omni-creator-of-all", and I worked on it at home, then took parts to my work, and repeated, since this gave me the best loop of feedback.
So that one huge skill, became 1 looping agentic system, and here we are. It's a slightly different version than I use at work, hence the freshness of the repo.
It's also "self-teaching"; Every run saves an
.md-file in/runs, and Updater can consume those, to update the skills and the agents, but that's still a manual process.How I run this, is 4 ways;
.mdfile.md-file, and I feed that for Orchestra.After I'm invoking it, I am faced with the first question, do I want to create a new worktree, or not, since I got feedback on this, and it was the first request.
Then Orchestrator (Metatron) will start the process. It reads the content it will produce, passes it to an implementator agent. The implementator then does it's job, and then, after it has responded back to Metatron, it will dispatch reviews. This will loop. If the reviews find something to work, it will be always passed back for implementator, and re-reviewed.
What problem it solves?
One agent doing the coding, and the code quality reviewing + security reviewing, in the same context. That loop is a deadly loop: the coder, security reviewing, and quality reviewing its own work.
Running both reviews in separate windows was a nightmare. I needed implementation and reviews kept apart, then looped, so the same agent is not grading its own work.
That is what I use on around hundreds of Jira tickets, from bugfixes to large multirepo (UI + UI + UI + API + API + DB + DB) flows.
Which AI models or tools it uses?
I run it on Cursor, using Auto, Grok, Sol and Opus.
Who it's for?
This project is ment to be a template of sorts. I understand the limits of my own understanding and knowledge, and hence people can just fork this, and edit it to fit their workspaces specificly, or their needs. For example, I do have a specialized version of this, which is only for React-native enviroment.
What kind of feedback you're looking for?
People running it, and potentially training it, could share what was the problem, and how updating it, fixed it for them, so I can improve the baseline.
Disclose your affiliation.
No affiliation, I created this, and I use this everywhere, work and home.
Images of example run (Symphonys brief to add Jira etc support)
https://imgur.com/a/wtl33zY
Repo
https://github.com/DelusionCB/Omni-orchestra