From b9eb95d8c0af2cac0d8a039ffe9aa2f72101cc6d Mon Sep 17 00:00:00 2001 From: h Date: Sat, 5 Sep 2026 04:56:57 +0200 Subject: [PATCH] docs(readme): what the setup is, link to the site, memory seeding --- README.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 61b2a33..1bb266f 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,10 @@ # beaver-agent -My real beaver-gateway setup (paired with the protocol from beaver.kotikot.com). +My real [beaver-gateway](https://git.kotikot.com/beaver/beaver-gateway) setup: the Beavering Manager, a personal agent that lives on a home server, reads an Obsidian vault, talks through Telegram and deep chats in the vault, remembers people and promises, and has hands (Komodo, Home Assistant, T3 Code threads, calendars, Firefly, Telegram history through beavergram). The narrative and the docs are on [the site](https://beaver.kotikot.com/docs); this README is the operator's part: how to run it. -Uses Claude Code and Raycast subscriptions for agents, has some MCPs set up. You can use this as-is or modify to match your needs: `config.py` assembles the gateway from the `beaver_agent/` package. +Uses Claude Code and Raycast subscriptions for agents, has some MCPs set up. You can use this as-is or modify to match your needs: `config.py` assembles the gateway from the `beaver_agent/` package. It is opinion, not core - every piece is meant to be rewritten for your own vault. + +Seeding memory from an existing vault (old chats into digests, diary days and thoughts into notes about people) is one run of `scripts/seed_memory.py`; `--dry-run` first. ## Requirements