Pinned Tweet
𝘁𝗵𝗲 𝗱𝗶𝗿𝘁𝘆 𝘀𝗲𝗰𝗿𝗲𝘁 𝗼𝗳 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗔𝗜 𝗮𝗴𝗲𝗻𝘁𝘀 ↓
𝟮× 𝗺𝗼𝗿𝗲 𝘁𝗶𝗺𝗲 𝘂𝗽𝗳𝗿𝗼𝗻𝘁. not less.
you're not replacing work
you're 𝘥𝘰𝘤𝘶𝘮𝘦𝘯𝘵𝘪𝘯𝘨 work you've never named
→ every gap in your process
→ every judgment call you've made 100×
→ every exception you handle "automatically"
write it down. then the agent can do it.
45 days on the road. ops still ran. 🦞
𝘵𝘩𝘢𝘵'𝘴 𝘵𝘩𝘦 𝘶𝘯𝘭𝘰𝘤𝘬.
124
Johnny Halife retweeted
🇱🇻 Club Atlético Lanús envía sus felicidades a toda la comunidad judía en este Año Nuevo. Nuestros mejores deseos para que el 5787 sea bueno y dulce. Shaná Tová Umetuká!
apparently i'm a 92-rated ST. my commits do numbers, my cardio does not.
get scouted → gitfut.com/johnnyhalife #GitFut
3
49
There is a gap between "I have an AI agent" and "I have a system."
Most people stop at the agent.
The difference isn't the model. It's the architecture — and getting there has a shape.
Checkout Crawl-Walk-Run of Building an AI System 👇
❓ Most people ask: which AI is best?
❌ Wrong question.
The right one: how much intelligence does this task actually need?
Classifying emails. Routing workflows. Extracting structured fields. None of that needs a frontier model. It needs fast, cheap, and always-on.
When I brought a DGX Spark machine online, the real unlock wasn't cost. It was that it changed what's worth automating.
When a run costs nothing, you stop asking "is this worth building?" You start asking "why isn't this built yet?"
That's a different mode of thinking entirely.
1
54
My life lately.
I haven't been this excited about technology since the early days of the cloud.
1
43
I'm back to VSCode. Built something this week for my @openclaw agent workflows. It's called clawtask.
A lightweight, self-hosted task tracker where AI agents are first-class. 24 hours from idea to shipped. 🧵
2
2
140
Stack: Next.js 14 · SQLite · SSE for real-time UI · OpenClaw WSS
One AdapterService singleton maintains persistent WebSocket connections per agent. Task lifecycle is fully automatic — todo → in_progress → done driven by the agent itself.
REST API at /api/v1/ means I can enqueue tasks from anywhere. I fire them from Temporal workflows. Could be a cron, a webhook, anything external.
Queue-per-agent. Local. Self-hosted. Expose via Tailscale. No special infrastructure, no weird setup.
Curious if @steipete or anyone in the @openclaw community has found a better way to do this — it's the only pattern I landed on, would love the input.
1
79
The best AI is the AI you don't see.
clawtask is the queue that makes that possible — for anyone building seriously with OpenClaw.
Built it for me. Open sourcing it because I think the community can make it better.
OSS · MIT · Built with OpenClaw + Anthropic Sonnet · Code-reviewed by GitHub Copilot (ACP)
⭐ Star it 🐛 Break it 🔧 Improve it
github.com/johnnyhalife/claw…
80













