ssslvky1

4 ms·

1.
by ssslvky1 2mo ago
great job! https://github.com/memovai/mimimodel i made it run on esp32s3, and it works!!!
2.
by ssslvky1 8mo ago
This is genuinely one of the cutest projects I’ve seen in a while. It weirdly feels like a tiny companion rather than just a tool. Nice work.
3.
by ssslvky1 8mo ago
sure but if we just use api on device do we need an actual OS?
4.
OpenClaw on $5 chips, no Linux or Node.js(mimiclaw.io)
1 points by ssslvky1 8mo ago|3 comments
5.
by ssslvky1 8mo ago
The world's first AI assistant(OpenClaw) on a $5 chip. No Linux. No Node.js. Just pure C MimiClaw turns a tiny ESP32-S3 board into a personal AI assistant. Plug it into USB power, connect to WiFi, and talk to it through Telegram — it h
6.
Show HN: MimiClaw, OpenClaw(Clawdbot)on $5 Chips(github.com)
1 points by ssslvky1 8mo ago|0 comments
7.
Try Clawdbot Online(tryclawd.io)
2 points by ssslvky1 8mo ago|1 comments
8.
by ssslvky1 8mo ago
The experience of running Moltbot(Clawdbot) today is far from plug-and-play: Complex setup — You need to deploy it yourself on a server or VPS, install prerequisites, configure API keys, integrate with chat platforms, and keep it running 24
9.
by ssslvky1 9mo ago
When I built an agent system, I hoped to give my customers a probably budget.
10.
Ask HN: How to predict nums of output tokens?
2 points by ssslvky1 9mo ago|1 comments
11.
by ssslvky1 10mo ago
Problems with the GitHub model in the AI era: A commit doesn’t explain why the agent wrote that code. Critical reasoning (prompts, plans, tool traces) is lost. Hard to reproduce or continue work across agents/humans. Version control i
12.
Do we need a new GitHub for AI coding era?(github.com)
2 points by ssslvky1 10mo ago|2 comments
13.
by ssslvky1 10mo ago
Over the last year, coding agents have changed how developers work. But GitHub hasn’t changed much: it’s still built around the idea that humans write code, and commits are the primary unit of progress. I’m building MemoV, and I keep runnin
14.
by ssslvky1 11mo ago
Features Spin the slot machine every time you submit code! Endless spins! Wait for your build, vibe hard, and spin again. The Vibe Engine™ — the calmer you are, the luckier you get. (Probably.) Global Leaderboard — who’s the ultimate Vibe C
15.
by ssslvky1 11mo ago
Welcome to the only casino where your code commits to spin the reels of fate. Every git push is a gamble. Every bug fix is a jackpot waiting to happen. You’re not just coding — you’re vibing with destiny.
16.
Show HN: Should we gamify vibecoding? VibeSlots: bet when u vibe code(github.com)
2 points by ssslvky1 11mo ago|2 comments
17.
by ssslvky1 11mo ago
We use memory and back trace for debugging context, which is more find-grained than git commits.
18.
Show HN: Open Aardvark, vibe debugging in traceable context(github.com)
1 points by ssslvky1 11mo ago|1 comments
19.
I'm a jerk of Git management in AI coding(github.com)
1 points by ssslvky1 1y ago|0 comments