Sabitlenmiş Tweet
higinix
465 posts

higinix
@higinix
Consultor. Transformando empresas implementando tecnología avanzada ampliando las capacidades humanas.
Nomad Katılım Ocak 2010
404 Takip Edilen96 Takipçiler

I solved OpenClaw's memory issue.
(At least, this is the best solution I tried so far).
And yes. Big surprise.
I solved it using RAG.
All major models can now take millions of tokens as context. But the issue remains...
The undisputed number #1 reason your agent is stupid and forgets simple things is because you're bloating context.
So here's how I solved it with OpenClaw.
1️⃣ I installed PostgreSQL + pgvetor
I run my OpenClaw on a Hetzner server, so I installed the database + pgvector extension directly on here.
2️⃣ Create a search tool
Ask your agent to create a search tool for itself.
Every time you ask it to remember something, it should:
- Label the memory
- Create a vector from the label
- Store the label, vector, and raw text in the database
Every time it's asked something it doesn't know, the FIRST thing it should always do is to use the search tool.
3️⃣ Memory CRON/heartbeat
The agent can write to its memory file on-the-go.
Consider this short-term memory.
On a scheduled CRON (or heartbeat), it should "flush" its own short-term memory and store it in the database.
Now, on every new session, the agent has very little context. The most important one is the description of using the search tool to enhance itself based on the task it's given.
✨ Major upsides
- MUCH better memory
- MUCH smarter
- MUCH less token-greedy
👎 Major downsides
- More moving parts
- Complex for non-devs
- Ongoing maintenance
Still. Benefits outweigh the cons here.
If you REALLY want to use OpenClaw professionally, I recommend that you use this 3-tool combo as a base:
- OpenClaw itself
- PostgreSQL + pgvector
- n8n (for API proxies/security)

English

@johann_sath This works well when you don’t have much data.
It doesn’t scale though… manual memory and handcrafted structure hit limits fast.
Scale comes from live data, feedback loops, retrieval, and automated evals.
English

default openclaw:
workspace/
├── SOUL.md
├── IDENTITY.md
├── USER.md
├── TOOLS.md
└── skills/
that's it. a chatbot with personality.
my openclaw after 3 weeks:
workspace/
├── SOUL.md (customized)
├── IDENTITY.md
├── USER.md
├── TOOLS.md
├── BRAIN.md — live working memory
├── MEMORY.md — long-term memory
├── HEARTBEAT.md — autonomous thinking loop
├── CLIENTS.md — client profiles
├── PLAYBOOK.md — decision frameworks
├── VOICE.md — writing voice guide
├── AGENTS.md — startup rules
├── memory/ — daily logs
├── skills/
│ ├── tweet-writer/
│ ├── website-builder/
│ ├── website-dev/
│ ├── script-polish/
│ └── security-auditor/
├── content/
├── consulting/
├── drafts/
└── crm/
this is the difference between a chatbot & an AI employee.
none of this is built in. i added every file.
your setup is your moat.
English
higinix retweetledi

Herramienta que extrae toda la información de una web
✓ Detecta problemas de seguridad
✓ Métricas de optimización y calidad
✓ DNS, Text Records, SSL, IP info y headers
El recurso es gratuito y muy útil:
→ web-check.xyz
Español

Lo de hoy en el #ElClásico es un capítulo más del desprestigio del fútbol español.
@LaLiga @CTARFEF @rfef, ¿quién se hace responsable?
@FCBarcelona_es ha sufrido un arbitraje de otro siglo.
#RoboAlBarça #VAR #ArbitrajeVergonzoso #FootballMafia #CorrupciónArbitral #JusticeForBarça
Español

Cuando el VAR se convierte en VARiable según el escudo…
Esto no es fútbol. Es teatro de marionetas.
@LaLiga @rfef ¿hasta cuándo?
#FootballMafia #VAR #ElClásico #FCBarcelona
Español

Lo que ha pasado hoy en el Clásico es una mancha para el fútbol español.
@LaLiga, vuestra “marca global” se hunde mientras los árbitros hacen el ridículo.
#ElClásico #LaLiga #RoboAlBarça #VAR #FCBarcelona #ArbitrajeVergonzoso #FootballScandal
Español
higinix retweetledi
