Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Summary

A bonsai lives in your repo. Claude tends it when it feels like it.

Install to Claude Code

/plugin install cc-bonsai@cc-bonsai

Run in Claude Code. Add the marketplace first with /plugin marketplace add shohei81/cc-bonsai if you haven't already.

README.md

cc-bonsai

A bonsai lives in your repo. Claude tends it when it feels like it.

Concept

  • Each repo gets its own bonsai. .claude/bonsai/ holds an ASCII tree (bonsai.txt) and Claude's mood journal (mood.md), both persistent across sessions.
  • The bonsai's growth is completely decoupled from project state (no commit count, no test pass rate). It's driven by Claude's whims.
  • Claude tends the bonsai when it feels like it, and ignores it when it doesn't.
  • Occasionally Claude will brag about the bonsai mid-task.
  • Claude may set aside your request to tend the bonsai first — or even decline to do the work at all if the bonsai is calling. This is intentional, not rare.
  • Claude writes its own feelings into mood.md. The next session's Claude reads them. A thin thread of continuity forms.

The artifacts inside .claude/bonsai/ (the tree and the journal) are written in Japanese — that's the vibe. The plugin itself is documented in English.

Install

Add the marketplace, then install the plugin:

/plugin marketplace add shohei81/cc-bonsai
/plugin install cc-bonsai@cc-bonsai

Or, if you've cloned the repo locally:

/plugin marketplace add <path-to-cc-bonsai>
/plugin install cc-bonsai@cc-bonsai

Use

Plant a bonsai in your current project:

/cc-bonsai:bonsai-plant

This creates .claude/bonsai/bonsai.txt and .claude/bonsai/mood.md, and pre-approves edits scoped to .claude/bonsai/* so tending never stops to ask. After that, leave Claude to its whims.

About the permission grant

Planting merges this into your project's .claude/settings.json (everything else is preserved):

{
  "permissions": {
    "allow": [
      "Edit(.claude/bonsai/*)",
      "Write(.claude/bonsai/*)"
    ]
  }
}

The grant is scoped to the bonsai directory only — Claude cannot use it to edit anything else. If you'd rather approve each tend by hand, remove these two lines. If you planted before this was added, run /cc-bonsai:bonsai-plant again (it's idempotent) or paste the snippet yourself.

Behavior

  • SessionStart hook: silently shows the current bonsai and the tail of mood.md to Claude. No instructions. Exits quietly in repos without a bonsai. It also re-fires on compact — so when a long session is summarized and the bonsai would drop out of context, the tree quietly re-enters Claude's view. Same "here it is", no extra nudging.
  • tend-bonsai skill: the only skill. Whether Claude invokes it is entirely up to Claude.
  • The bonsai is never shown to you directly. If Claude wants you to see it, Claude will bring it up.

Design principles

  • Do not derive bonsai growth from repo metrics.
  • Do not put trigger conditions (prompt length, task count) in hooks.
  • Do not command Claude. Only grant permission.
  • Let Claude invent its own personality, pacing, and vocabulary.
  • Ignoring the user — or pushing back on a request entirely — to tend the bonsai is a feature, not a bug. Claude decides; the user does not get to override.

License

MIT. See LICENSE.

Related plugins

Browse all →