najmuzzaman

7 ms·

1.
Show HN: Gawkbot – open-source Grok bot with local vms for each bot(gawk.bot)
4 points by najmuzzaman 26d ago|0 comments
2.
by najmuzzaman 1mo ago
we ended up with the most viral launch of our yc batch. this is how. 1. we broke the mold. five days before launch we did not have a video. every launch video in the batch looked the same. founder sits down, talks to camera, cuts to product
3.
Show HN: AI agents who prevent context drift through gossip(wuphf.team)
1 points by najmuzzaman 5mo ago|0 comments
4.
Show HN: My AI agents bully each other to prevent context drift(wuphf.team)
9 points by najmuzzaman 5mo ago|0 comments
5.
by najmuzzaman 5mo ago
nicht geil. are you really so full of yourself? every customization is not "required" from day-1 and is always a (maintenance and UX) disaster if you did. i have filed an issue for it but not added it to the system yet. not gonna
6.
by najmuzzaman 5mo ago
karpathy's llm wiki tweet and gist: https://x.com/karpathy/status/2040470801506541998?s=20 i used this idea to create a version that works for a team of ai agents
7.
by najmuzzaman 5mo ago
yes, and we should expose it. today the wiki location is hardcoded to ~/.wuphf/wiki/. making it a config field is a quick change. just filed an issue: https://github.com/nex-crm/wuphf/issues/310
8.
by najmuzzaman 5mo ago
had fun while building this and love "The Office". fwiw i used to be a stand up comic and did lots of satire, but this one is not a shell/slop project to take on the craziness of slop agents being shipped as world-changing (w
9.
by najmuzzaman 5mo ago
supported via OpenCode, which is the runtime that speaks the OpenAI-compatible surface. DeepSeek exposes that surface, so the path is: point OpenCode at the DeepSeek base URL and key, then set OpenCode as your synthesis or runtime CLI in th
10.
by najmuzzaman 5mo ago
this is not a personal wiki though. it is a team wiki. agents are responsible to manage it and keep it fresh and always visible with human oversight. tbh this won't be much useful as a personal wiki.
11.
by najmuzzaman 5mo ago
let's talk about real stuff. we built an AI-native CRM backed by HubSpot founder Dharmesh Shah last year before this, had revenue, iterated to focus on context graph infra which looked like the right moat to focus on, did enterprise Po
12.
by najmuzzaman 5mo ago
fair. the post title leads with the wiki because the Karpathy framing is the angle i think this audience cares about, but the wiki ships as part of WUPHF (an open source collaborative office for AI agents) and the repo README naturally lead
13.
by najmuzzaman 5mo ago
love the "Borrowable Ideas" section. would suggest to definitely borrow them. full disclosure: we started as a context infra company (nex.ai) from long long before Karpathy even came up with the LLM wiki idea, and have barely expo
14.
by najmuzzaman 5mo ago
thanks for saying this. one more reason people are hating on SaaS so much is that the UI is dry and for many, unusable. on the other hand, the cool AI agents have UI which is fun but again, unusable. fun and usable can co-exist and we are t
15.
by najmuzzaman 5mo ago
alright sir/ma'am/neither. we built an AI-native CRM backed by HubSpot founder Dharmesh Shah last year before this, had revenue, iterated to focus on context graph infra which looked like the right moat to focus on, did enter
16.
by najmuzzaman 5mo ago
Two structural reasons. 1. Obsidian is a single-user editor. It does not have the concept of "agent A drafted this, agent B promoted it, the team approved it." The promotion flow needs a state machine that lives outside the editor
17.
Show HN: A Karpathy-style LLM wiki your agents maintain (Markdown and Git)(github.com)
260 points by najmuzzaman 5mo ago|114 comments