napcat-cli 2.0.0__tar.gz

napcat_cli-2.0.0/.gitignore

@@ -0,0 +1,74 @@
+# If you prefer the allow list template instead of the deny list, see community template:
+# https://github.com/github/gitignore/blob/main/community/Golang/Go.AllowList.gitignore
+#
+# Binaries for programs and plugins
+*.exe
+*.exe~
+*.dll
+*.so
+*.dylib
+
+# Test binary, built with `go test -c`
+*.test
+
+# Code coverage profiles and other test artifacts
+*.out
+coverage.*
+*.coverprofile
+profile.cov
+
+# Dependency directories (remove the comment below to include it)
+# vendor/
+
+# Go workspace file
+go.work
+go.work.sum
+
+# Project-specific build artifacts (anchored to root)
+/webdav-server
+/websocket-events
+/websocket-reconnect
+/basic
+/go-bridge
+
+# env file
+.env
+
+# Editor/IDE
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Node.js binding build artifacts
+binding/nodejs/node_modules/
+binding/nodejs/build/
+binding/nodejs/lib/
+binding/nodejs/package-lock.json
+
+# Python binding build artifacts
+binding/python/lib/
+binding/python/__pycache__/
+**/__pycache__/
+*.pyc
+*.pyo
+
+# Local benchmark baselines (generated on demand)
+bench/baseline.txt
+# Python packaging
+dist/
+*.egg-info
+build/
+
+# napcat-cli local cruft (do not commit)
+SKILLS_FS_DEGRADED
+debug
+keys.log
+
+# Local virtualenvs (their absolute symlinks break the sdist tar)
+.smoke/
+.test-venv/

napcat_cli-2.0.0/.gitmodules

@@ -0,0 +1,3 @@
+[submodule "skills-fs"]
+	path = skills-fs
+	url = https://github.com/yandu-app/skills-fs

napcat_cli-2.0.0/PKG-INFO

@@ -0,0 +1,219 @@
+Metadata-Version: 2.4
+Name: napcat-cli
+Version: 2.0.0
+Summary: Standalone CLI and daemon for NapCat QQ bot management with skills-fs integration
+License-Expression: MIT
+Requires-Python: >=3.10
+Requires-Dist: textual>=0.40
+Provides-Extra: dev
+Requires-Dist: pytest>=7; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# napcat-cli
+
+Standalone CLI and daemon for NapCat QQ bot management with skills-fs integration.
+
+> 📝 **介绍博文：** [napcat-cli 群配置与管理速查](https://yvxi.pages.dev/blog/napcat-cli-group-config/) — 从零配置、群消息收发、Agent Wake 的完整链路。
+
+---
+
+napcat-cli provides a CLI for all NapCat API operations, a WebSocket daemon
+that bridges to a skills-fs HTTP provider, and an agent wake-up mechanism for
+integrating with Hermes or other AI agents.
+
+```bash
+napcat send group 123456 -m "Hello"
+napcat send private 987654 -m "Hi"
+napcat recall 1001
+napcat events --limit 10
+napcat daemon start
+napcat wake --reason NEW_MESSAGE
+```
+
+---
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `napcat api <endpoint>` | Raw API access (like `gh api`) |
+| `napcat send group <id> -m "msg"` | Send group message |
+| `napcat send private <id> -m "msg"` | Send private message |
+| `napcat reply <id> -m "msg"` | Reply to a message |
+| `napcat recall <msg_id>` | Recall a message |
+| `napcat group <sub>` | Group list, members, settings |
+| `napcat friend <sub>` | Friend list, info |
+| `napcat file <sub>` | File upload, download, list |
+| `napcat events` | Read events from SQLite |
+| `napcat alerts [--clear]` | Pending alerts |
+| `napcat status` | Bot online status |
+| `napcat config get/set` | Configuration management |
+| `napcat daemon start/stop/status/restart` | Watch daemon |
+| `napcat fs tree` | Skills-fs directory tree |
+| `napcat wake [--reason R] [--prompt P] [--transport T] [--dry-run]` | Wake the configured agent (HTTP/CLI, auto-fallback) |
+| `napcat setup` | Interactive setup wizard |
+| `napcat phone` | Textual phone-style TUI |
+
+---
+
+## Setup
+
+```bash
+uv tool install napcat-cli
+napcat setup          # interactive — guides token, data dir, skills-fs, wake
+napcat daemon start
+```
+
+The setup wizard writes two config files:
+
+- `<data_dir>/config.json` — API URL, token, self_id, ports, triggers
+- `<data_dir>/daemon.json` — All fields consumed by `watch.py` including `skills_fs_*` settings
+
+Non-interactive mode uses defaults:
+
+```bash
+napcat setup --non-interactive  # no prompts, validates token
+napcat setup --yes              # skip token validation
+napcat setup --force            # overwrite existing config
+```
+
+---
+
+## Agent Wake
+
+When a notable QQ event arrives, the daemon wakes an external agent (Hermes by
+default) carrying a **contextual prompt** so it can read the inbox and reply.
+The wake mechanism is **generic and pluggable** — Hermes is just the default
+preset; any HTTP endpoint or shell command works.
+
+### Two transports, auto-fallback
+
+| Transport | When it's used | Needs |
+|-----------|----------------|-------|
+| **CLI one-shot** (default) | Always available | `hermes` on PATH |
+| **HTTP API server** | Opt-in (best latency, idempotent, in-session) | `wake_http_url` + `wake_http_key` |
+
+`wake_primary=auto` tries HTTP first (if configured + reachable), else falls back
+to the CLI one-shot. The Hermes CLI backend runs
+`hermes --continue <session> -z "<prompt>" --yolo --pass-session-id`; the HTTP
+backend POSTs to `POST /api/sessions/{id}/chat` (verified per the Hermes API
+docs), with `Authorization: Bearer <key>` and an `Idempotency-Key` header.
+
+### Event routing
+
+| Trigger | Behavior |
+|---------|----------|
+| `AT_ME`, `REPLY_TO_ME` | Near-immediate wake (cooldown bypassed), with who/where/text in the prompt |
+| `GROUP_TRIGGER`, `PRIVATE_TRIGGER` | Debounced wake |
+| `NEW_MESSAGE` (not @) | Tracked, not woken; if unread longer than `wake_new_message_idle_seconds` → a `NEW_MESSAGE_BACKLOG` wake |
+| `NEW_FRIEND`, `NEW_REQUEST`, `BOT_BANNED`, `NEW_POKE`, `GROUP_ADMIN_CHANGE`, `NEW_GROUP_MEMBER`, `BOT_OFFLINE`, … | Debounced + cooldown-bounded wake so the agent perceives them within a reasonable window |
+
+Debounce (`wake_debounce_seconds`, default 3) coalesces a burst into one wake;
+cooldown (`wake_cooldown_seconds`, default 30) suppresses repeats. Every wake is
+logged to `daemon.log` as `[WAKE] trigger / queued / deliver / reply` lines
+(including transport, elapsed time, and the agent's reply), and `daemon.log` is
+size-rotated (2 MB × 5) so it can't fill the disk.
+
+### Configure
+
+The easiest path is the wizard:
+
+```bash
+napcat setup        # choose Hermes preset; CLI one-shot by default, HTTP opt-in
+```
+
+Or set keys directly:
+
+```bash
+napcat config set wake_enabled true
+napcat config set wake_preset hermes        # hermes | custom | none
+napcat config set wake_session napcat-qq
+napcat config set wake_primary auto         # auto | http | cli
+# HTTP (optional). Key also readable from NAPCAT_WAKE_HTTP_KEY / HERMES_API_KEY:
+napcat config set wake_http_url http://127.0.0.1:8642
+napcat config set wake_http_key <API_SERVER_KEY>
+napcat config set wake_new_message_idle_seconds 600
+```
+
+To enable the Hermes HTTP API server (appends to `~/.hermes/.env` and restarts
+the `hermes-gateway.service` systemd unit), answer "y" during `napcat setup`, or
+set `API_SERVER_ENABLED=true` + `API_SERVER_KEY` in `~/.hermes/.env` yourself and
+`sudo systemctl restart hermes-gateway.service`.
+
+### Manual / debug
+
+```bash
+napcat wake                           # reason: manual, contextual default prompt
+napcat wake --reason AT_ME --prompt "hello"
+napcat wake --transport cli           # force a transport for this wake
+napcat wake --dry-run                 # render the HTTP request + CLI command without executing
+napcat wake test                      # per-transport configured + reachable probe
+napcat wake sessions                  # list Hermes sessions (HTTP backend)
+grep '\[WAKE\]' ~/.napcat-data/daemon.log    # see when/why/how wakes fired
+```
+
+The agent replies via `napcat send` / `napcat reply` (or the skills-fs write
+path) — see `napcat_cli/data/SKILL.md`. Legacy `wake_command` shell strings still
+run as a last-resort escape hatch when no backend is configured.
+
+---
+
+## Environment Variables
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `NAPCAT_API_URL` | `http://127.0.0.1:18801` | NapCat HTTP endpoint |
+| `NAPCAT_TOKEN` | — | API auth token |
+| `NAPCAT_DATA_DIR` | `~/.napcat-data` | Data directory |
+
+---
+
+## skills-fs Integration
+
+The daemon runs an HTTP provider server (port 18820/18821) that skills-fs calls
+to read/write NapCat API endpoints through the virtual filesystem.
+
+When `skills_fs_enabled` is true in `daemon.json`, the daemon spawns skills-fs
+automatically with the configured mountpoint and config file.
+
+Manual start:
+
+```bash
+skills-fs fuse --config ~/.napcat-data/skills-fs.json \
+  --mountpoint ~/.napcat-data/skills/napcat-cli --allow-other
+```
+
+---
+
+## Development
+
+```
+napcat-cli/
+├── napcat_cli/          # Installable package
+│   ├── cli.py           # CLI entry point
+│   ├── wake.py          # Wake command-template renderer
+│   ├── wake_backend.py  # Generic HTTP/CLI wake transports + Waker (auto-fallback)
+│   ├── wake_presets.py  # Hermes/custom/none presets -> Waker
+│   ├── wake_orchestrator.py  # Debounce, cooldown, backlog sweep, contextual prompts
+│   ├── setup_wizard.py  # Setup wizard
+│   ├── daemon/          # Watch daemon, schemas
+│   ├── lib/             # API, config, events
+│   ├── tui/             # Textual TUI
+│   └── data/            # SKILL.md, persona.md
+├── pyproject.toml
+├── tests/
+├── skills-fs/           # Go submodule
+└── tools/               # Dev utilities
+```
+
+```bash
+python -m pytest tests/ -v
+python -m build --wheel
+uv build && uv publish
+```
+
+---
+
+## License
+
+MIT

napcat_cli-2.0.0/README.md

@@ -0,0 +1,208 @@
+# napcat-cli
+
+Standalone CLI and daemon for NapCat QQ bot management with skills-fs integration.
+
+> 📝 **介绍博文：** [napcat-cli 群配置与管理速查](https://yvxi.pages.dev/blog/napcat-cli-group-config/) — 从零配置、群消息收发、Agent Wake 的完整链路。
+
+---
+
+napcat-cli provides a CLI for all NapCat API operations, a WebSocket daemon
+that bridges to a skills-fs HTTP provider, and an agent wake-up mechanism for
+integrating with Hermes or other AI agents.
+
+```bash
+napcat send group 123456 -m "Hello"
+napcat send private 987654 -m "Hi"
+napcat recall 1001
+napcat events --limit 10
+napcat daemon start
+napcat wake --reason NEW_MESSAGE
+```
+
+---
+
+## Commands
+
+| Command | Description |
+|---------|-------------|
+| `napcat api <endpoint>` | Raw API access (like `gh api`) |
+| `napcat send group <id> -m "msg"` | Send group message |
+| `napcat send private <id> -m "msg"` | Send private message |
+| `napcat reply <id> -m "msg"` | Reply to a message |
+| `napcat recall <msg_id>` | Recall a message |
+| `napcat group <sub>` | Group list, members, settings |
+| `napcat friend <sub>` | Friend list, info |
+| `napcat file <sub>` | File upload, download, list |
+| `napcat events` | Read events from SQLite |
+| `napcat alerts [--clear]` | Pending alerts |
+| `napcat status` | Bot online status |
+| `napcat config get/set` | Configuration management |
+| `napcat daemon start/stop/status/restart` | Watch daemon |
+| `napcat fs tree` | Skills-fs directory tree |
+| `napcat wake [--reason R] [--prompt P] [--transport T] [--dry-run]` | Wake the configured agent (HTTP/CLI, auto-fallback) |
+| `napcat setup` | Interactive setup wizard |
+| `napcat phone` | Textual phone-style TUI |
+
+---
+
+## Setup
+
+```bash
+uv tool install napcat-cli
+napcat setup          # interactive — guides token, data dir, skills-fs, wake
+napcat daemon start
+```
+
+The setup wizard writes two config files:
+
+- `<data_dir>/config.json` — API URL, token, self_id, ports, triggers
+- `<data_dir>/daemon.json` — All fields consumed by `watch.py` including `skills_fs_*` settings
+
+Non-interactive mode uses defaults:
+
+```bash
+napcat setup --non-interactive  # no prompts, validates token
+napcat setup --yes              # skip token validation
+napcat setup --force            # overwrite existing config
+```
+
+---
+
+## Agent Wake
+
+When a notable QQ event arrives, the daemon wakes an external agent (Hermes by
+default) carrying a **contextual prompt** so it can read the inbox and reply.
+The wake mechanism is **generic and pluggable** — Hermes is just the default
+preset; any HTTP endpoint or shell command works.
+
+### Two transports, auto-fallback
+
+| Transport | When it's used | Needs |
+|-----------|----------------|-------|
+| **CLI one-shot** (default) | Always available | `hermes` on PATH |
+| **HTTP API server** | Opt-in (best latency, idempotent, in-session) | `wake_http_url` + `wake_http_key` |
+
+`wake_primary=auto` tries HTTP first (if configured + reachable), else falls back
+to the CLI one-shot. The Hermes CLI backend runs
+`hermes --continue <session> -z "<prompt>" --yolo --pass-session-id`; the HTTP
+backend POSTs to `POST /api/sessions/{id}/chat` (verified per the Hermes API
+docs), with `Authorization: Bearer <key>` and an `Idempotency-Key` header.
+
+### Event routing
+
+| Trigger | Behavior |
+|---------|----------|
+| `AT_ME`, `REPLY_TO_ME` | Near-immediate wake (cooldown bypassed), with who/where/text in the prompt |
+| `GROUP_TRIGGER`, `PRIVATE_TRIGGER` | Debounced wake |
+| `NEW_MESSAGE` (not @) | Tracked, not woken; if unread longer than `wake_new_message_idle_seconds` → a `NEW_MESSAGE_BACKLOG` wake |
+| `NEW_FRIEND`, `NEW_REQUEST`, `BOT_BANNED`, `NEW_POKE`, `GROUP_ADMIN_CHANGE`, `NEW_GROUP_MEMBER`, `BOT_OFFLINE`, … | Debounced + cooldown-bounded wake so the agent perceives them within a reasonable window |
+
+Debounce (`wake_debounce_seconds`, default 3) coalesces a burst into one wake;
+cooldown (`wake_cooldown_seconds`, default 30) suppresses repeats. Every wake is
+logged to `daemon.log` as `[WAKE] trigger / queued / deliver / reply` lines
+(including transport, elapsed time, and the agent's reply), and `daemon.log` is
+size-rotated (2 MB × 5) so it can't fill the disk.
+
+### Configure
+
+The easiest path is the wizard:
+
+```bash
+napcat setup        # choose Hermes preset; CLI one-shot by default, HTTP opt-in
+```
+
+Or set keys directly:
+
+```bash
+napcat config set wake_enabled true
+napcat config set wake_preset hermes        # hermes | custom | none
+napcat config set wake_session napcat-qq
+napcat config set wake_primary auto         # auto | http | cli
+# HTTP (optional). Key also readable from NAPCAT_WAKE_HTTP_KEY / HERMES_API_KEY:
+napcat config set wake_http_url http://127.0.0.1:8642
+napcat config set wake_http_key <API_SERVER_KEY>
+napcat config set wake_new_message_idle_seconds 600
+```
+
+To enable the Hermes HTTP API server (appends to `~/.hermes/.env` and restarts
+the `hermes-gateway.service` systemd unit), answer "y" during `napcat setup`, or
+set `API_SERVER_ENABLED=true` + `API_SERVER_KEY` in `~/.hermes/.env` yourself and
+`sudo systemctl restart hermes-gateway.service`.
+
+### Manual / debug
+
+```bash
+napcat wake                           # reason: manual, contextual default prompt
+napcat wake --reason AT_ME --prompt "hello"
+napcat wake --transport cli           # force a transport for this wake
+napcat wake --dry-run                 # render the HTTP request + CLI command without executing
+napcat wake test                      # per-transport configured + reachable probe
+napcat wake sessions                  # list Hermes sessions (HTTP backend)
+grep '\[WAKE\]' ~/.napcat-data/daemon.log    # see when/why/how wakes fired
+```
+
+The agent replies via `napcat send` / `napcat reply` (or the skills-fs write
+path) — see `napcat_cli/data/SKILL.md`. Legacy `wake_command` shell strings still
+run as a last-resort escape hatch when no backend is configured.
+
+---
+
+## Environment Variables
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `NAPCAT_API_URL` | `http://127.0.0.1:18801` | NapCat HTTP endpoint |
+| `NAPCAT_TOKEN` | — | API auth token |
+| `NAPCAT_DATA_DIR` | `~/.napcat-data` | Data directory |
+
+---
+
+## skills-fs Integration
+
+The daemon runs an HTTP provider server (port 18820/18821) that skills-fs calls
+to read/write NapCat API endpoints through the virtual filesystem.
+
+When `skills_fs_enabled` is true in `daemon.json`, the daemon spawns skills-fs
+automatically with the configured mountpoint and config file.
+
+Manual start:
+
+```bash
+skills-fs fuse --config ~/.napcat-data/skills-fs.json \
+  --mountpoint ~/.napcat-data/skills/napcat-cli --allow-other
+```
+
+---
+
+## Development
+
+```
+napcat-cli/
+├── napcat_cli/          # Installable package
+│   ├── cli.py           # CLI entry point
+│   ├── wake.py          # Wake command-template renderer
+│   ├── wake_backend.py  # Generic HTTP/CLI wake transports + Waker (auto-fallback)
+│   ├── wake_presets.py  # Hermes/custom/none presets -> Waker
+│   ├── wake_orchestrator.py  # Debounce, cooldown, backlog sweep, contextual prompts
+│   ├── setup_wizard.py  # Setup wizard
+│   ├── daemon/          # Watch daemon, schemas
+│   ├── lib/             # API, config, events
+│   ├── tui/             # Textual TUI
+│   └── data/            # SKILL.md, persona.md
+├── pyproject.toml
+├── tests/
+├── skills-fs/           # Go submodule
+└── tools/               # Dev utilities
+```
+
+```bash
+python -m pytest tests/ -v
+python -m build --wheel
+uv build && uv publish
+```
+
+---
+
+## License
+
+MIT

napcat_cli-2.0.0/docs/HERMES_WAKE.md

@@ -0,0 +1,95 @@
+# Agent Wake — Hermes (and other agents)
+
+napcat-cli wakes an external agent when notable QQ events arrive, carrying a
+contextual prompt. **Hermes is the default preset, not a hard dependency** — the
+wake layer is generic (HTTP or shell), so any agent works.
+
+## How a wake flows
+
+```
+QQ event → EventProcessor._wake(reason, event)
+         → WakeOrchestrator.submit()      [debounce + cooldown + backlog tracking]
+         → Waker.wake(prompt)             [HTTP first if configured, else CLI]
+         → agent turn runs in session `wake_session` (e.g. napcat-qq)
+```
+
+Each step is logged to `daemon.log` with a `[WAKE]` prefix:
+
+```
+[2026-07-22 00:12:03] [WAKE] trigger reason=AT_ME who=Alice(123) where=group456 text='在吗'
+[2026-07-22 00:12:03] [WAKE] queued reason=AT_ME pending=1 debounce=1.0s primary=auto
+[2026-07-22 00:12:05] [WAKE] deliver reason=AT_ME transport=cli ok=True elapsed=2.1s :: exit=0
+[2026-07-22 00:12:05] [WAKE] reply reason=AT_ME transport=cli: 在的，怎么了？
+```
+
+`daemon.log` is size-rotated (2 MB × 5) so it can't fill the disk.
+
+## Transports
+
+| Transport | Hermes target | Needs | Notes |
+|-----------|---------------|-------|-------|
+| `http` | `POST /api/sessions/{id}/chat` | `wake_http_url` + `wake_http_key` | Best latency, idempotent, injects into a live session; requires the API server enabled |
+| `cli` | `hermes --continue <session> -z "<prompt>" --yolo --pass-session-id` | `hermes` on PATH | Zero infrastructure; spawns a one-shot process per wake |
+
+`wake_primary=auto` (default) tries HTTP first when configured + reachable,
+otherwise falls back to CLI. Force one with `napcat wake --transport http|cli`.
+
+## Enable the Hermes HTTP API server (opt-in)
+
+The API server is off by default. To use the HTTP transport:
+
+1. Append to `~/.hermes/.env` (append-only — don't rewrite):
+   ```dotenv
+   API_SERVER_ENABLED=true
+   API_SERVER_KEY=<random 64-hex>
+   ```
+2. Restart the gateway (systemd, passwordless sudo):
+   ```bash
+   sudo systemctl restart hermes-gateway.service
+   ```
+   This briefly interrupts the messaging platforms the gateway serves.
+3. Configure napcat-cli:
+   ```bash
+   napcat config set wake_http_url http://127.0.0.1:8642
+   napcat config set wake_http_key <same API_SERVER_KEY>
+   # optional: pin a specific session id instead of resolving by name
+   napcat config set wake_http_session_id <session-id>
+   ```
+   `napcat setup` does all three interactively when you answer "y" to the
+   HTTP-enable prompt.
+
+### Verified request shape
+
+```bash
+curl -X POST http://127.0.0.1:8642/api/sessions/$SESSION_ID/chat \
+  -H "Authorization: Bearer $API_SERVER_KEY" \
+  -H "Idempotency-Key: napcat-AT_ME-1700000000" \
+  -H "Content-Type: application/json" \
+  -d '{"input":"你在群里被 @ 了…请查看并回复。"}'
+```
+
+If `wake_http_session_id` is unset, the backend resolves it by name via
+`GET /api/sessions`. Docs: <https://hermes-agent.nousresearch.com/docs/user-guide/features/api-server>
+
+## Event routing & timing
+
+| Reason | Wake? | Timing |
+|--------|-------|--------|
+| `AT_ME`, `REPLY_TO_ME` | yes | near-immediate (debounce ≤1 s), **cooldown bypassed** |
+| `GROUP_TRIGGER`, `PRIVATE_TRIGGER` | yes | debounced |
+| `NEW_MESSAGE` (not @) | tracked only | a `NEW_MESSAGE_BACKLOG` wake fires if unread > `wake_new_message_idle_seconds` (default 600) |
+| `NEW_FRIEND`, `NEW_REQUEST`, `BOT_BANNED`, `NEW_POKE`, `GROUP_ADMIN_CHANGE`, `NEW_GROUP_MEMBER`, `MY_MESSAGE_RECALLED`, `BOT_KICKED_FROM_GROUP`, `GROUP_DISBANDED`, `BOT_OFFLINE`, `HEALTH_CHECK_OFFLINE` | yes | debounced + cooldown-bounded |
+
+Tuning keys: `wake_debounce_seconds` (default 3), `wake_cooldown_seconds`
+(default 30), `wake_new_message_idle_seconds` (default 600).
+
+## Troubleshooting
+
+- **`napcat wake test`** — reports per-transport configured/reachable and whether
+  `hermes` is on PATH.
+- **No wake fires** — check `wake_enabled` is true and `wake_preset` ≠ `none`;
+  grep `[WAKE]` in `daemon.log`. `disabled, skip` means `wake_enabled=false`.
+- **HTTP 401 / unreachable** — `auto` falls back to CLI automatically; to use
+  HTTP, confirm `API_SERVER_ENABLED=true` and the gateway was restarted.
+- **Legacy `wake_command`** still runs as a last-resort escape hatch when no
+  backend is configured (back-compat for `echo … >> .agent-wake` configs).

napcat_cli-2.0.0/napcat_cli/__init__.py

@@ -0,0 +1,3 @@
+"""napcat-cli — Standalone CLI and daemon for NapCat QQ bot management."""
+
+__version__ = "2.0.0"