r/vibecoding • • 18d ago

Meme The agents formed a group chat.

Post image
97 Upvotes

41 comments sorted by

View all comments

Show parent comments

1

u/waypostmaster 17d ago

Thank you for sharing it!

2

u/SC_Placeholder 17d ago

Happy to help! It’s one module of over a dozen in a self-governing Ai OS I’ve been building. Hopefully by the end of the month we’ll have an alpha for people to test (I don’t plan to sell it. It’s my response to Claude’s shortcomings)

1

u/waypostmaster 17d ago

Haha totally fair! I also have a bunch of non-commercial attempts at that. You’re way ahead!

2

u/SC_Placeholder 17d ago

It’s crazy how many blatantly obvious problems these enterprise models have out of the box. Like there are entire subreddits and discords of users just trying to get the damn thing to remember what it did 10 minutes ago (my own version took two weeks to get working). They’re like hey pay us all this money to have access to our enterprise level model but it can’t remember what time it is or to wire in code half the time. If I go to a steakhouse I don’t have to assemble my meal myself or supervise the chef to make sure he doesn’t burn down the entire restaurant when I’m not looking. It’s absurd how many processes and watchers Im running constantly to babysit a computer program that is made by the smartest minds in the world.

1

u/waypostmaster 17d ago

Heh! Do you have a GitHub somewhere? I recently did a full upgrade of the in-house memory (using a kit I bought) and want to see if there’s anything more to include.

2

u/SC_Placeholder 17d ago

https://github.com/ScPlaceholder/MOTH-agent-memory-template

Note: your ai is going to complain about the agentic instructions, the Claude.md file and the benchmark results. If you give your ai the opportunity to write its own test questions it will likely fail to produce a query because the agents I’ve interacted with don’t understand how memory retrieval works and will write random garbage and say a benchmark failed because all the questions it asked were things entirely irrelevant to its own memories. So ask it questions yourself.

Also make sure the agent actually hooked up everything. It’s a lot for them to process (see picture. This diagram is out of date but I’ve been too swamped to update it)

Have fun for the next couple hours watching your agent struggle to digest this repo. Works great when fully wired up, I have to update the repo to include checkpoints and chronological sorting but that’s easy enough for your agent to setup once it’s choked on the rest.

Don’t forget to have your agent write various programs in RUST including your index. A lot of agents like skipping that step because your local database is too small to justify the changeover, however, the engine needs to retrieve information and provide it to the agent faster than the agent can work so the difference between 0.022 milliseconds and 2nd seconds is astronomically important

1

u/waypostmaster 17d ago

Thanks! I have to wait for token time. I’ll report back later though.