This repository provides lightweight, deterministic tool adapters so agents built with popular frameworks can call tendr-cli without ever touching raw files directly.
Everything stays 100% plaintext, git-safe, and cultivatable.
🤖 🚰 ✂️ Tend your 🎋 WikiBonsai digital garden with integrated tooling.
Most agent frameworks give agents raw filesystem or shell access.
That quickly leads to corrupted hierarchies, broken [[links]], and messy attributes.
tendr-tools gives agents a single safe entrypoint: Discrete, predictable tendr commands wrapped as native Tools (or Skills) for each framework.
git clone https://github.com/wikibonsai/tendr-tools.git
cd tendr-toolsSet your vault location (defaults to ~/.tendr/garden):
export TENDR_VAULT=~/path/to/your/garden| Framework | Folder | File | Type |
|---|---|---|---|
| LangGraph / LangChain | langgraph/ |
tendr_tool.py |
Tool |
| CrewAI | crewai/ |
tendr_tool.py |
Tool |
| Letta | letta/ |
tendr_tool.py |
Tool |
| OpenClaw | openclaw/ |
tendr_skill.md |
Skill |
See the README inside each framework folder for usage examples and code snippets.
All tools respect:
TENDR_VAULTenvironment variabletendr-clisafety rules and auth mode (uservsagent)- Your existing semtree, typed links, and CAML structure
A knowledge base that merely accumulates is a liability.
One that gets actively tended becomes an asset that appreciates over time.
[Read more here]
These integrations make it easy for agents to cultivate instead of just retrieve.
- garden-beds — Starter vaults
- tendr-cli — Core deterministic commands
- tendr-skill — Agent behavior & prompts
- wikibonsai — The legible knowledge layer
Status: Early / Beta — always keep backups and use version control.
Happy tending 🌱