holix-extensions

## When to use The user wants the agent to **grow new capabilities** safely: - add a custom tool or slash command - “напиши расширение”, “допиши себя”, “добавь skill/tool” - list what extensions are loaded - disable something that breaks the agent **Never edit Holix core** (`core/`, `cli/`, `integrations/`, package source). Only create **profile-local drop-in extensions**. ## Mode restriction (important) Self-authored extensions (**create / enable / hot-reload**) work **only in local single-operator** mode: | Mode | Create / hot-reload | |------|---------------------| | CLI, TUI, `holix run` (local operator) | **Allowed** | | Telegram / MAX multi-user bots | **Denied** | Messenger hosts set `HOLIX_MESSENGER_HOST` and `self_extensions_enabled=False`. Override (not recommended on shared bots): `HOLIX_SELF_EXTENSIONS=1`. If `manage_agent_extensions` returns `self_extensions_denied`, tell the user to use a **local** profile session — do not try to force-create on the group bot. ## Architecture (safe zone) ```text ~/.holix/profiles/<profile>/extensions/<name>/ agent.py # get_agent_extension() holix.plugin.json settings.default.yaml README.md ``` - Discovered on agent start **and** via **hot-reload** after `create` / `reload` (local mode). - Does **not** require pip install. - Same profile only (unless user copies to `~/.holix/extensions/`). ## Primary tool Use **`manage_agent_extensions`**: | action | Purpose | Local only? | |--------|-------...