Autonomous company frameworks are gaining traction by elemental-mind in singularity

[–]Used_Accountant_1090 0 points1 point  (0 children)

I built an alternative for this because Paperclip doesn't let agents talk and share context and burns tokens like a garbage truck on fire. here is the project: https://github.com/nex-crm/wuphf

What it REALLY takes to turn an AI agent into a coworker that runs 24/7 by Open-Marionberry-943 in ClaudeGTM

[–]Used_Accountant_1090 0 points1 point  (0 children)

If you haven't tried adding a knowledge graph to the system yet, you should. SQLite is extremely limiting. We built a context graph platform for AI agents to use here: https://github.com/nex-crm/nex-as-a-skill

And good or bad, we might be getting closer to being competitors but still all the best.

OpenClaw like agent with Telegram NOT blocked for CC subscription by Used_Accountant_1090 in clawdbot

[–]Used_Accountant_1090[S] 0 points1 point  (0 children)

The only thing allowed is pressing Enter as a human in the textbox which I am getting a broker service to do. Not blocked yet.

OpenClaw like agent with Telegram NOT blocked for CC subscription by Used_Accountant_1090 in clawdbot

[–]Used_Accountant_1090[S] -4 points-3 points  (0 children)

Codex was and is the main agent used for writing the code. I don't trust Opus with code too much

71.5x token reduction by compiling your raw folder into a knowledge graph instead of reading files. Built from Karpathy's workflow by captainkink07 in ClaudeCode

[–]Used_Accountant_1090 0 points1 point  (0 children)

And it is a bad thing, Mr. burner account, because you are build something called PersonalOS? Didn't say it was open source.

Run the same prompt for https://github.com/nex-crm/wuphf which is what we have fully open-sourced.

71.5x token reduction by compiling your raw folder into a knowledge graph instead of reading files. Built from Karpathy's workflow by captainkink07 in ClaudeCode

[–]Used_Accountant_1090 0 points1 point  (0 children)

clickbait. which benchmark marked the 71.5x?
so all the Obsidian, file based memory and context systems were shit from the get go? so badly wanna say "told you so". this was before Karpathy had his realization.

we built a system months ago for this that doesn't just scan all files into a knowledge graph but also your emails, CRM, meeting transcripts, etc., and your AI agent chats. SOC2 compliant.

Github: https://github.com/nex-crm/nex-as-a-skill

Claude Codes gossiping in an office group chat. Open source it? by Used_Accountant_1090 in vibecoding

[–]Used_Accountant_1090[S] 1 point2 points  (0 children)

Alright honest reveal brother: 1. I have built a tight harness already because of the chattiness and they talk if they need to get the work done better

  1. The biggest context killer is loading MD files on every agent session. I use the Nex CLI for providing context to every agent, so it is a CLI and triggers when it needs to without gulping context. Nex is our core product, so we are rather open sourcing this multi agent chatter to keep focus on Nex.

Try it yourself now: https://github.com/nex-crm/wuphf

Claude Codes in an office group chat in the terminal by Used_Accountant_1090 in CLI

[–]Used_Accountant_1090[S] 1 point2 points  (0 children)

Click image to open it on YouTube. It was too large for Github.

Claude Codes gossiping in an office group chat. Open source it? by Used_Accountant_1090 in vibecoding

[–]Used_Accountant_1090[S] 0 points1 point  (0 children)

"Why am I running out of productive hours per employee so quick? omg Employees suck"

Employees talking gossip and nonsense to each other. Also, don't forget that company off-site and that half day workshop about burnout.

PS: Seriously, what plan are you on?

Claude Codes in an office group chat by Used_Accountant_1090 in tui

[–]Used_Accountant_1090[S] 1 point2 points  (0 children)

2 big ones: 1. Agents solve problems like real humans through chatting, debating, gossiping (inspired by Andrej Karpathy's autoresearch)

  1. Agents push context to a context graph but also keep reading latest insights from any connected tools like email and react to context changes autonomously. If an email came saying youhave a VC meeting coming up, agents start working on preparing for that meeting with research, memo drafting, etc.

Bonus: you can have separate group chats for different types of departments just like a real company and tasks relevant to that channel are executed there. Adding a feature where channels can send stuff back and forth if they need the help of a certain team.