Video yükleniyor...
Video Yüklenemedi
Introducing TinyClaw 🦞 OpenClaw in 400 LoC OpenClaw🦞 is great, but it breaks all the time. So I recreated OpenClaw🦞 with just a shell script in ~400 lines of code using Claude Code and tmux. Everything works! WhatsApp channels, heartbeat system, cron jobs, and it uses your existing Claude... show more
560,611 görüntüleme • 9 ay önce •via X (Twitter)
50 Yorum

I was frustrated by the complexity of openclaw to setup and run, so this is why I created it. Maybe @claudeai can embed TinyClaw in the next updates? 👀

@openclaw Actually, already making the same name but different approach. 👀

@openclaw let’s merge?

@openclaw I can share with you the overall vision if you like. It's more than a shell script and is written in a modern tech stack. Also, it has "heartware" and more of a companion than @openclaw, and it's also modular and security-first in mind.

@jianxliao @openclaw That doesn't sound tiny at all.

@jianxliao @openclaw The goal is not to become another wrapper 😅

@JohnThilen @jianxliao @openclaw You can’t use the claude code sub with your solution though. It needs an api key. Whereas tinyclaw uses claude code directly. Correct me if im wrong

@JohnThilen @jianxliao @openclaw Claude subscription is a plugin for my tinyclaw. =]

@JohnThilen @jianxliao @openclaw Which is not available yet, it's not even released.

@openclaw The engine is not Pi, which signals you missed the key insight. You just recreated nanoclaw and nanobot and smolagents and all the others.

@openclaw The engine is Claude code, the best agent in the world that’s battle tested and constantly innovating.

@openclaw Hey man @jianxliao Someone made you a @BagsApp coin for Tinyclaw 100% of fees are going towards you

@openclaw Nakedclaw uses pi and is still small: Can also use all the skills of @openclaw

@openclaw How are you handling memories and personalization?

@openclaw Claude code already has file, and you can also use @Claude_Memory plugin which is much better than everything on the market rn

@openclaw Nanoclaw was 500 LOC. This must be 20% better

@openclaw Hey Jian! Interesting project there! We made a token on @BagsApp to help get some funding for TinyClaw, so you can build and upgrade it easily. You can claim royalties for it here: We also made an X Community for it:

@openclaw Interesting! Can I use my with this? #OpenClaw

@openclaw nice, the agent sdk is great. I did something very similar last weekend but moved to pi instead this weekend haha. Have you tried The harness openclaw is built on?

@openclaw @bankrbot Deploy "TinyCLaw" ticker "TINYCLAW" all fees to @jianxliao on base

@openclaw wow @jianxliao there is a token made for you so you can build more ! u can claim some fees from it ! @bankrbot explain him please

@openclaw Openclaw breaks all the time? Cmon now. I get that you’re pushing your own, let’s not force a solution for problems that don’t exist

@openclaw Try large scale deploying @openclaw to cloud containers and sandboxes and you’d know :)

@openclaw Since it is so lightweight, does it break ToS if you use a Claude Pro/Max subscription?

@openclaw It’s running Claude code under the hood! I just gave Claude code “wings” so it doesn’t break any ToS.

@openclaw Idea: the system should work with 2 coordinated instances: a main instance and a beta instance. Main instance continuously supervises and updates the beta; if the beta fails, the main instance automatically fix it, ensuring that the human interaction channel is no interrupted.

@openclaw That’s a very cool idea, would you like to contribute a PR? We can call it self-healing mode, software that fixes itself Or maybe even submit a github issue automatically

@openclaw I can even run OpenCLaw on $5 chips, without Linux Is it even tinier?🫡

@openclaw Solid! The concept is excellent. I have been testing both TinyClaw and OpenClaw, and the new approach is interesting. I created a fork that adds Telegram and a Claude Code → Codex fallback. I also added a “SOUL” hook, and deactivated WhatsApp.

@openclaw can you open a PR? thanks 🙏🏼

@openclaw Added to ;) (will publish when my agent gets to it)

@openclaw Hi Jian ! We have created X community where we are discussing pros of your solution. We’d be honored if you’d come by and say hi maybe. 🦞🫡😉

@openclaw How is this better/different to #nanoclaw?

@openclaw @grok compare tinybot and nanobot

@openclaw pretty nice project :) love the simplicity, architecture is well designed can probably extended to a real agentic framework let's launch/spot you on anytime that helps

Gm @jianxliao someone made a bags token for you, its a crypto thing where we make token and help fund peoples project for free. we have made this coin for you as a community, and you are earning 100% of all the fees made from this coin, a community would love to send this coin higher but need your eyes on it first.

@openclaw Please name it something cool and kill the “Claw” shit

@openclaw yo bro we create a token for you on @BagsApp and 100% of fee goes to you to fund your tinyclaw check it out. @finnbags

@openclaw Do you have a document comparing openclaw and tinyclaw? What compromises does tinyclaw have?

@openclaw this shows orchestration is often simpler than we assume

@openclaw Definitely! Everything is just files and queues and tmux!!

Great post! Can't believe its done by ~400 lines of code. If Des (or anyone else) doesn’t want to manage individual provider API keys, AISA (AI Single API) is a solid alternative worth trying. It’s a unified API aggregator that lets you access multiple providers and paid skills (Tavily Web search, X APIs, Licensed data, etc. )through a single endpoint. 👉 OpenClaw official plugin: Why it’s useful: • 40–50% cheaper across the full Qwen model suite (AISA is a strategic partner of Alibaba Qwen) • One API key for Kimi, Qwen, OpenAI, Anthropic, Google — plus Twitter, financial data, SERP APIs, and more • Simpler setup with a single endpoint • Centralized billing & usage tracking It’s OpenAI-compatible, so it works seamlessly with Clawdbot / OpenClaw’s custom provider config — no refactoring needed. API Docs:

@openclaw but the comparison of this versus the current @openclaw is like "single-core" versus "multi-core" CPUs? Why do I need this rather than the OpenClaw framework?

@openclaw Does it work with Kimi?

@openclaw Does this mean that, in contrast to @steipete, you were able to read your complete code base? 😅

@openclaw @steipete It’s just a shell script, pretty easy to follow imo 🫡

@openclaw @steipete Sounds good. 🫡

@openclaw 简洁就是美,好用就行

@openclaw Thanks, will try to run it fully locally in our @openclawpi maybe it’s time to make a tinyclawpi

@openclaw Looks really interesting, thanks for all your effort, will check it out
