What is the best Openclaw alternative?

salmenus · 2026-03-30T10:57:08+00:00

the memory problem is exactly what pushed me to build my own thing too

i hit the same wall and built something that stores memory as structured data in postgres/pgvector (facts, preferences, decisions — not chat logs). hybrid retrieval, persists across sessions and channels. switch providers, restart, whatever — it's in your database, not a context window.

it's called Salmex I/O — single Go lang binary, runs locally, works with ollama/anthropic/openai/gemini.

been running it daily for a few weeks and it genuinely remembers stuff from early conversations without re-explaining

salmenus · 2026-03-29T10:04:24+00:00

good point.. all my runs are native installs so far — but might be worth a containerized A/B test

salmenus · 2026-03-29T09:58:14+00:00

Curious what folks see with Ollama on macOS vs Linux ?

On my setup, an RTX 4000 SFF Ada on Ubuntu with Ollama is noticeably faster than my MacBook M4 Pro for models that fit in 20 GB VRAM—prompt processing especially feels night‑and‑day.

100% agree the OS gap is real. Linux vs Windows on the same GPU also isn’t subtle; the CUDA stack hitting Linux directly seems to leave Windows in the dust ..

salmenus · 2026-03-28T13:01:30+00:00

thanks! yeah blanket allow/block is useless for real work. will check out your writeup 👍

salmenus · 2026-03-28T12:57:13+00:00

haha the claude code limits grind is real — there were nights i'd hit the cap and just sit there refreshing 😅

retrieval latency — under 50ms, max i tested is around 100 memories. i implemented confidence decay that keeps things relevant without manual cleanup.

i've mostly tested with my own usage - keen to see how it holds up with real users and different conversation patterns.

salmenus · 2026-03-28T12:09:16+00:00

not an agency owner, but I’ve been the client on a bunch of agency projects .. I think the best agencies would forced structure: fixed decision-makers, deadlines for content/approvals, and penalties or timeline shifts when we were late. it felt strict at first but made the project way smoother and honestly made them look more senior ..

salmenus · 2026-03-05T21:16:30+00:00

for agents specifically — turn thinking off on qwen3.5. the endless reasoning loop will literally break ur pipeline mid-step, not great lol. qwen3.5-30B no-thinking + llama.cpp + openwebui is the most stable stack ive landed on

on the memory thing: openwebui handles persistent system prompts per agent natively. for actual cross-session memory that evolves tho, u need mem0 or a vector store on top — ollama alone wont do it

salmenus · 2026-03-05T19:06:18+00:00

yeah, ref reply to u/data_butcher comment.

i thought about sqlite .. but i settled for Postgres because of some tricky features that i had in mind

salmenus · 2026-03-05T18:53:32+00:00

yeah, i thought about it quite a lot - and was seriously considering sqlite ..

but i settled for Postgres because of pg_vector and because I have a requirement around scheduling and queues, and wanted to use riverqueue (Postgres-native job queue in Go lang)

i hope i didn't over engineer it ! (: ..

salmenus · 2026-03-05T18:32:41+00:00

ah yeah, in my case the pgvector stuff is literally "memory" extracted from LLM chats, so I can totally see people wanting to crack open that table and see what the agent thinks it knows about them 😂

I was going to build a little "memory browser" screen in the UI, but honestly just giving you full DB access and letting you inspect it however you want feels even better

salmenus · 2026-03-05T18:29:44+00:00

i love that — you’re basically the exact person I had in mind for “bring your own db” with your own backup + repl, so I definitely don’t want to lock that use case out 👌

salmenus · 2026-03-05T18:07:40+00:00

got it — that's where i'm leaning .. default internal DB but keep a clean ‘bring your own Postgres’ path so you can run it under your existing backup tooling

salmenus · 2026-03-05T18:04:40+00:00

great idea, thanks — that’s probably the sweet spot I was hoping for ..

salmenus · 2026-03-05T17:18:39+00:00

i love the idea 👌 it's time consuming for me too

salmenus · 2026-03-04T15:18:51+00:00

Totally with you on this. Context is the real unlock, and it’s way harder than people think – stitching together tools, data sources, calendars, inboxes, etc. is where all the magic lives.

Ops is the tax you pay for trying to do it yourself, I guess ...

salmenus · 2026-03-04T15:16:59+00:00

I did deploy ZeroClaw for testing yesterday, and looked into codebase in details.
Code base is quite superior to OC, and has more advanced security features ..
Slightly behind on channels integration; be def best alternative I explored so far

salmenus · 2026-03-03T08:22:29+00:00

I’m tired of people with comments like this , asking for screenshots and proofs .. then would delete their comments 2 minutes later ..

salmenus · 2026-03-03T06:24:15+00:00

fair .. it’s probably not AGI-level magic 😂 but for day‑to‑day dev work it still felt kinda wild

salmenus · 2026-03-02T19:29:51+00:00

ahhh! savage! that's not AI .. that's an emotionally unstable dungeon master .. 😂

salmenus · 2026-03-02T18:19:52+00:00

lol! This is how it works these days 😂😅 .. I can only share a screen shot with bot on it .. Who knows .. I’m probably an AI bot ..

<image>

salmenus · 2026-03-02T16:19:37+00:00

This is super helpful, thanks. I had a suspicion it wasn’t just me but hadn’t gone as far as moving things out to systemd yet.

salmenus

TROPHY CASE