Index / BashoBot · updated Oct 2, 2026

BashoBot

uraimo/bashobot · healthy · rank 43 of 43 by stars

A delightfully absurd OpenClaw-inspired assistant written in ~4k lines of pure Bash, using named pipes and standard Unix tools with zero runtimes. It's the minimalist hacker's take on the personal AI assistant — runs almost anywhere bash 3.2 exists.

#bash#openclaw-clone#minimalist#telegram-bot#self-hosted
Compare vs OpenClaw
GitHub ↗

Facts

Repository

Contributors1
Open issues4
Last commitFeb 20, 2026
Release cadence~2 days
Latest release0.9.0

Runtime

LanguageShell
Memory8 MB
Boot time15 ms
Deploymentself-hosted · edge · desktop
Setup difficultyMedium
Plugin ecosystemLimited

Posture

LicenseMIT
Local-firstYes
Cloud dependencyOptional
Multi-userNo
Privacy postureStrong

Community

Sentiment45% positive
Reddit mentions0
Web results10

Security breakdown

Composite 55 / 100 · how these are scored

Sandboxing4 / 10

higher is safer

API security5 / 10

higher is safer

Network isolation3 / 10

higher is safer

Telemetry safety8 / 10

higher is safer

Shell access risk8 / 10

higher is riskier

Model access

Read from the repository, not written by a model · 20 files examined

3 providers · custom endpoint

Direct
AnthropicGoogleOpenAI
Compatible
OpenAI-compatible

Pinned models

gpt-4oOpenAI

gpt-4o released 2024-05-13 — 2 years old (from the public model catalogue)

Pin last edited 8 months ago

Evidence

Decision

Why choose BashoBot over OpenClaw?

Why choose this

  • No Node.js or any runtime — pure bash plus standard Unix utilities
  • Tiny footprint; runs on virtually any POSIX system including ancient bash 3.2
  • Entire codebase is small enough to audit in an afternoon

Tradeoffs

  • Far fewer features, integrations, and UI polish than OpenClaw
  • Shell-based tool execution carries higher injection/escape risk
  • Tiny community (6 stars) with no Reddit presence or ecosystem support

Best fit

  • Unix purists who want an assistant with zero runtime dependencies
  • Low-resource or embedded environments where Node/Python won't fit
  • Tinkerers who want a fully auditable ~4k-line codebase

Avoid if

  • You need a polished UI, dashboard, or rich plugin ecosystem
  • You want battle-tested sandboxing for tool execution
  • You need multi-user or team collaboration features
Good Confidence55%

Evidence is limited to the README, commit history, and release metadata; there is no community discussion to validate real-world usage. Security and reliability assessments are inferred from the architecture rather than independent review.

AI layer reviewed Sep 21, 2026 · how this is written

Star activity

6 stars today

Overview

BashoBot is an OpenClaw-inspired personal AI assistant implemented entirely in Bash (3.2+ compatible), totaling roughly 4,000 lines. It eschews Node.js, Python, or any other runtime in favor of standard Unix utilities like curl, jq, and base64, communicating internally through a modular architecture built on named pipes. This makes it runnable on virtually any POSIX system, from routers to ancient macOS installs.

Despite its spartan foundation, it replicates the core OpenClaw feature set: tool calling, markdown-based memory, shared sessions, SOUL.md persona files, multiple LLM providers (including OAuth subscription logins), and both Telegram and CLI interfaces. A daemon mode listens on pipes while clients connect via -cli or single-shot -t messages, and slash commands handle model switching, memory management, and context compaction.

Security is handled pragmatically rather than rigorously: an optional command whitelist with user approval gates the exec tool, and the README suggests running inside a container for real isolation. Compared to OpenClaw, BashoBot trades ecosystem breadth, UI polish, and sandboxing maturity for radical simplicity, auditability, and portability — it's a hacker's homage rather than a production competitor.

Nominate a clone

Add a new Claw

Paste a GitHub repository and tell us why it belongs on the tracker.

Opens a prefilled issue on GitHub — every nomination is public. Comfortable with a PR? Adding the repo to projects.json is faster.