claude-notification-plugin 1.0.82 → 1.0.88

package/commands/listener.md

@@ -1,100 +0,0 @@
----
-description: Manage the Telegram Listener daemon (start, stop, status, logs, restart)
----
-
-# Listener Management
-
-Manage the Telegram Listener daemon that receives tasks from Telegram and executes them via `claude -p`.
-
-The user invokes this command as `/claude-notification-plugin:listener <action>`.
-
-## Actions
-
-Determine the action from the user's input. If no action is provided, show the help text below and ask which action they want.
-
-### start
-
-Start the listener daemon.
-
-1. Determine the plugin root path — use the directory where this command file lives: `${CLAUDE_PLUGIN_ROOT}`. The listener CLI script is at `${CLAUDE_PLUGIN_ROOT}/bin/listener-cli.js`.
-2. Run in a shell:
-   ```bash
-   node "${CLAUDE_PLUGIN_ROOT}/bin/listener-cli.js" start
-   ```
-3. Show the output to the user. If it says "Listener started", confirm success. If there is an error (missing config, missing projects, already running), explain what to do.
-
-### stop
-
-Stop the listener daemon.
-
-1. Run:
-   ```bash
-   node "${CLAUDE_PLUGIN_ROOT}/bin/listener-cli.js" stop
-   ```
-2. Show the output.
-
-### status
-
-Show the listener status.
-
-1. Run:
-   ```bash
-   node "${CLAUDE_PLUGIN_ROOT}/bin/listener-cli.js" status
-   ```
-2. Show the output.
-
-### logs
-
-Show recent log entries.
-
-1. Run:
-   ```bash
-   node "${CLAUDE_PLUGIN_ROOT}/bin/listener-cli.js" logs
-   ```
-2. Show the output.
-
-### restart
-
-Restart the listener daemon.
-
-1. Run:
-   ```bash
-   node "${CLAUDE_PLUGIN_ROOT}/bin/listener-cli.js" restart
-   ```
-2. Show the output.
-
-## Help text
-
-If the user doesn't specify an action, show:
-
-```
-Telegram Listener — receives tasks from Telegram and executes via claude -p.
-
-Usage:
-  /claude-notification-plugin:listener start    — Start the daemon
-  /claude-notification-plugin:listener stop     — Stop the daemon
-  /claude-notification-plugin:listener status   — Show status
-  /claude-notification-plugin:listener logs     — Show recent logs
-  /claude-notification-plugin:listener restart  — Restart the daemon
-
-Prerequisites:
-  1. Telegram bot configured (token + chatId in ~/.claude/notifier.config.json)
-  2. "listener.projects" section in config with at least one project
-
-See LISTENER.md for detailed documentation.
-```
-
-## Important
-
-- The `${CLAUDE_PLUGIN_ROOT}` variable resolves to the plugin installation directory. Always use it to build the path to `bin/listener-cli.js`.
-- If the config doesn't have a `listener.projects` section, tell the user to add one and show a minimal example:
-  ```json
-  {
-    "listener": {
-      "projects": {
-        "default": { "path": "/path/to/your/project" }
-      }
-    }
-  }
-  ```
-- If Telegram credentials are missing, suggest running `/claude-notification-plugin:setup` first.

package/commands/setup.md

@@ -1,54 +0,0 @@
----
-description: Configure Telegram credentials and notification settings
----
-
-# Setup claude-notification-plugin
-
-Help the user configure the notification plugin. The config file is `~/.claude/notifier.config.json`.
-
-## Steps
-
-1. **Read existing config** (if it exists) from `~/.claude/notifier.config.json` to preserve current settings.
-
-2. **Ask for Telegram bot token**. If a token already exists in the config, show a masked version (first 6 and last 4 characters) and ask if the user wants to keep it. If they want a new one, ask them to provide it.
-
-3. **Get the Chat ID**. If the token is available and Chat ID is missing:
-   - Ask the user to send any message to their bot in Telegram.
-   - Fetch `https://api.telegram.org/bot<TOKEN>/getUpdates` to auto-detect the Chat ID.
-   - If auto-detection fails, ask the user to enter the Chat ID manually.
-   - If Chat ID already exists, show it and ask if the user wants to keep it.
-
-4. **Write the config** to `~/.claude/notifier.config.json`. Merge with existing config — do NOT overwrite settings that already exist (`notifyAfterSeconds`, `notifyOnWaiting`, `debug`, channel `enabled` flags, etc.). Only update `telegram.token` and `telegram.chatId` with the values from this session.
-
-   Default config structure (for new installs):
-   ```json
-   {
-     "telegram": {
-       "enabled": true,
-       "token": "<TOKEN>",
-       "chatId": "<CHAT_ID>",
-       "deleteAfterHours": 24
-     },
-     "windowsNotification": { "enabled": true },
-     "sound": { "enabled": true, "file": "C:/Windows/Media/notify.wav" },
-     "voice": { "enabled": true },
-     "notifyAfterSeconds": 15,
-     "notifyOnWaiting": false,
-     "debug": false
-   }
-   ```
-
-5. **Register CLI commands** — so that `claude-notify-listener`, `claude-notify-install`, and `claude-notify-uninstall` are available from the terminal (not just inside Claude).
-
-   Run in a shell:
-   ```bash
-   node "${CLAUDE_PLUGIN_ROOT}/bin/register-cli.js"
-   ```
-   This finds the directory where `claude` is installed and creates wrapper scripts there. Show the output to the user. If registration fails (e.g. `claude` not in PATH), inform the user but do NOT treat it as a fatal error — the rest of setup is still valid.
-
-6. **Confirm** — show the user a summary of what was saved.
-
-## Important
-
-- NEVER log or display the full token. Always mask it.
-- Preserve all existing config values when writing — only update token and chatId.