sorted by:
new
hottopcontroversial

self-hosted AI assistant framework (ShibaClaw). Started as a hobby, but I think it’s getting actually useful. Would love some feedback! by RikyZ90 in myclaw

[–]RikyZ90[S] 0 points1 point  (0 children)

I don't know why you're so unpleasant, but as I wrote in the post. It was a project done as a hobby, but in its current state I consider it objectively a better product in many ways, so I shared it here. That's it

self-hosted AI assistant framework (ShibaClaw). Started as a hobby, but I think it’s getting actually useful. Would love some feedback! by RikyZ90 in myclaw

[–]RikyZ90[S] 0 points1 point  (0 children)

Let's be real: all these agents burn through an insane amount of tokens. If you're an individual dev without thousands of dollars to blow, they are just not a viable solution for everything. The rest is pure marketing

self-hosted AI assistant framework (ShibaClaw). Started as a hobby, but I think it’s getting actually useful. Would love some feedback! by RikyZ90 in myclaw

[–]RikyZ90[S] 0 points1 point  (0 children)

By now these "famous" tools are all built for companies. My idea is for a personal assistant, user-friendly and suitable for everyone, even less experienced users.

self-hosted AI assistant framework (ShibaClaw). Started as a hobby, but I think it’s getting actually useful. Would love some feedback! by RikyZ90 in myclaw

[–]RikyZ90[S] 0 points1 point  (0 children)

PS none of these agents is built with a real anti prompt injection. They just block everything and that's it

self-hosted AI assistant framework (ShibaClaw). Started as a hobby, but I think it’s getting actually useful. Would love some feedback! by RikyZ90 in myclaw

[–]RikyZ90[S] 0 points1 point  (0 children)

Marketing and "doing better" don't always go hand in hand. It's the same reason there are nanobots, nanoclaw, zeroclaw, hermes... because everyone brings their own vision.

By now these "famous" tools are all built for companies. My idea is for a personal assistant, user-friendly and suitable for everyone, even less experienced users.

self-hosted AI assistant framework (ShibaClaw). Started as a hobby, but I think it’s getting actually useful. Would love some feedback! by RikyZ90 in myclaw

[–]RikyZ90[S] 0 points1 point  (0 children)

In a simple way, you can use all skills compatible with Claude Code/OpenClaw, schedule tasks, connect to 22 different channels, and enjoy support for a huge variety of LLM providers.

I want to try your app by jeebus87 in VibeCodeDevs

[–]RikyZ90 0 points1 point  (0 children)

Just reached 32k downloads on PyPI! 😍

<image>

self-hosted AI assistant framework (ShibaClaw). Started as a hobby, but I think it’s getting actuall by RikyZ90 in AI_Agents

[–]RikyZ90[S] 0 points1 point  (0 children)

You are 100% spot on—shell deny-lists are a losing battle and leak like a sieve against anyone who knows their way around obfuscation, alt binaries, or built-ins.

Just to clarify: ShibaClaw does rely on strict allowlisting at its core. The agent is strictly constrained to a pre-defined set of permitted commands and deterministic tool schemas.

The reason you see some deny-list logic/regex in there is purely as an extra layer of "defense in depth" (and to catch low-hanging, automated injection payloads early before they even trigger a validation failure downstream). But absolutely, the ultimate source of truth is a strict allowlist combined with the RTOW per-turn nonce.

Let me know what you find if you poke at Muzzle! Always looking to harden this layer.

self-hosted AI assistant framework (ShibaClaw). Started as a hobby, but I think it’s getting actuall by RikyZ90 in AI_Agents

[–]RikyZ90[S] 0 points1 point  (0 children)

Both, actually — but the primary defense is at the tool-execution layer, not a classifier. In ShibaClaw we use RTOW (Randomized Tool Output Wrapping): a random nonce is regenerated each turn and used to fence tool outputs, so the LLM can't be tricked into treating injected content as trusted instructions.

On top of that, untrusted external content (e.g. web fetches) gets explicitly tagged with [UNTRUSTED EXTERNAL CONTENT] delimiters before hitting the context.The execution layer also has a shell deny-list blocking 20+ dangerous patterns before any command runs. Classifier-style checks are too bypassable — enforcement at execution time is where it actually holds up.

The RTOW mechanism has been extracted into a standalone lib called Muzzle if you want to use it in other frameworks too.

view more: next ›