docs: update all documentation for v2.3.0 (channel monitoring, thread-per-session)

Author: zebbern

CHANGELOG.md

@@ -5,6 +5,21 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.3.0] - 2026-03-03
+
+### Added
+- **Channel Monitoring** (#17): Watch a Discord channel for bot/webhook messages and auto-trigger a Claude investigation in a thread. Messages are batched over a 30-second debounce window. Requires `MONITOR_CHANNEL_ID` and `MONITOR_BOT_IDS` env vars and the Message Content privileged intent.
+- **Thread-per-Session** (#19): New `/claude-thread` command starts each conversation in a dedicated Discord thread with a custom name.
+- **Per-Channel Session Tracking**: Regular `/claude` commands in the same channel automatically reuse the last session — no need to pass `session_id` manually.
+- **Custom Thread Names**: `/claude-thread name:"Fix auth bug" prompt:"Review the auth module"` creates a thread titled "Fix auth bug".
+- **Thread-Aware Channel Detection**: Commands work correctly inside session threads (bot recognizes the parent channel).
+
+### Changed
+- `discord/session-threads.ts` added — `SessionThreadManager` handles thread creation, lookup, and lifecycle
+- `discord/types.ts` — `InteractionContext` now exposes `getChannelId()` for per-channel session mapping
+- `core/handler-registry.ts` — `channelSessionMap` maintains channel → session mapping
+- `.env.example` updated with Channel Monitoring section
+
 ## [2.2.0] - 2025-07-18
 
 ### Added
@@ -188,6 +203,7 @@ This is the first stable release of Claude Code Discord Bot - a Discord bot that
 
 ---
 
+[2.3.0]: https://github.com/zebbern/claude-code-discord/releases/tag/v2.3.0
 [2.2.0]: https://github.com/zebbern/claude-code-discord/releases/tag/v2.2.0
 [2.0.0]: https://github.com/zebbern/claude-code-discord/releases/tag/v2.0.0
 [1.0.0]: https://github.com/zebbern/claude-code-discord/releases/tag/v1.0.0

README.md

@@ -26,6 +26,7 @@
 | Role-based access control | Restrict destructive commands (`/shell`, `/git`, worktree ops) to specific Discord roles | ✅ |
 | Local hosting & security | Keep keys and code on your infra while exposing a controlled interface through Discord | ✅ |
 | Channel monitoring | Watch a channel for bot/webhook messages and auto-investigate in a thread | ✅ |
+| Thread-per-session | Each `/claude-thread` conversation gets its own Discord thread with custom names | ✅ |
 | Audit trail & accountability | Channel history provides an easy-to-search record of who ran what and when | ✅ |
 
 </kbd>

deno.json

@@ -1,5 +1,5 @@
 {
-  "version": "2.2.0",
+  "version": "2.3.0",
   "compilerOptions": {
     "lib": ["deno.window"],
     "strict": true

docs/architecture.md

@@ -24,6 +24,7 @@ claude-code-discord/
 │
 ├── discord/                    # Discord integration layer
 │   ├── sender.ts               # Message sending, embeds, streaming
+│   ├── session-threads.ts      # Thread-per-session lifecycle management
 │   └── ...
 │
 ├── settings/                   # Settings management

docs/commands.md

@@ -1,10 +1,11 @@
 # Command Reference
 
-## Core Claude Commands (3)
+## Core Claude Commands (4)
 
 | Command | Description |
 |---------|-------------|
 | `/claude` | Send a prompt to Claude Code. Supports `prompt` and `session_id` options. |
+| `/claude-thread` | Start a new Claude conversation in a dedicated Discord thread. Options: `name` (thread title), `prompt`. |
 | `/resume` | Resume (continue) a previous Claude conversation with an optional follow-up prompt. |
 | `/claude-cancel` | Cancel the currently running Claude operation. |
 | `/fast` | Toggle Opus 4.6 fast mode — 2.5x faster responses, same quality. |

docs/features.md

@@ -49,6 +49,8 @@ Set via `/settings` > `claude` > `set-effort`.
 | Fork Session | Branch a conversation into a new independent session |
 | AskUserQuestion | Claude can ask clarifying questions mid-session via Discord buttons |
 | Interactive Permission Requests | Allow/Deny buttons when Claude wants to use unapproved tools (replaces CLI TUI prompt) |
+| Channel Monitoring | Auto-detect bot/webhook messages and trigger Claude investigation in a thread |
+| Thread-per-Session | Dedicated Discord thread for each `/claude-thread` conversation with custom names |
 
 Toggles available via `/settings` > `claude`.
 
@@ -153,6 +155,43 @@ Example schema:
 
 When enabled, responses follow `json_schema` output format through the SDK.
 
+## Thread-per-Session
+
+Keep conversations organized with dedicated Discord threads:
+
+- **`/claude-thread`** — Start a new Claude session in its own thread
+  - `name` — Custom thread title (required)
+  - `prompt` — Your initial prompt (required)
+- **Per-channel session tracking** — Regular `/claude` commands in the same channel automatically reuse the last session (no need to pass `session_id`)
+- **Thread auto-naming** — Threads are named with your custom title or a truncated version of the prompt
+- **Seamless continuation** — Subsequent `/claude` commands inside a session thread continue that conversation
+
+### How It Works
+
+1. Run `/claude-thread name:"Fix auth bug" prompt:"Review the auth module"`
+2. A new thread titled **Fix auth bug** is created
+3. Claude's response streams into the thread
+4. Any further `/claude` commands in that thread continue the same session
+5. Use `/claude-thread` again in the main channel to start a fresh conversation in a new thread
+
+## Channel Monitoring
+
+Automatically investigate alerts from other bots or webhooks:
+
+1. A monitored bot posts in the configured channel
+2. Messages are batched over a 30-second debounce window
+3. A thread is created on the alert message
+4. Claude analyzes the alert and streams its investigation into the thread
+
+### Setup
+
+```env
+MONITOR_CHANNEL_ID=123456789012345678    # Channel to watch
+MONITOR_BOT_IDS=987654321,111111111      # Bot/webhook user IDs to respond to
+```
+
+Requires the **Message Content** privileged intent enabled in the Discord Developer Portal. The bot needs Read Messages, Create Public Threads, and Send Messages in Threads permissions in the monitored channel.
+
 ## Role-Based Access Control (RBAC)
 
 Restrict dangerous commands to authorized users and roles:

docs/installation.md

@@ -123,6 +123,10 @@ ANTHROPIC_API_KEY=your_anthropic_api_key_here  # Only needed if not using `claud
 USER_ID=your_discord_user_id                   # Get mentioned when Claude finishes
 CATEGORY_NAME=claude-code                      # Discord category for channels
 WORK_DIR=/path/to/project                      # Working directory (default: current)
+
+# Channel Monitoring (optional)
+MONITOR_CHANNEL_ID=123456789012345678          # Channel to watch for alerts
+MONITOR_BOT_IDS=987654321,111111111            # Bot/webhook user IDs to respond to
 ```
 
 Environment variables override `.env` file settings. CLI flags override environment variables.

docs/known-issues.md

@@ -1,6 +1,6 @@
 # Known Issues & Accepted Risks
 
-> Last audited: 2025-02-18  
+> Last audited: 2026-03-03  
 > Context: Single-user personal Discord bot — not a production multi-user service
 
 This document tracks issues identified during a comprehensive code audit that were **intentionally not fixed**. Each entry explains why the issue exists, why it doesn't matter for our use case, and under what conditions (if any) it would need revisiting.