obsidian-agent-fleet 0.4.5 → 0.7.1

package/README.md

@@ -16,13 +16,13 @@ Agent Fleet is an Obsidian plugin that lets you build, configure, and run AI age
 
 💬 **Interactive Chat** — Dock a chat panel anywhere in Obsidian. Switch between agents. Attach documents and images. Send follow-up messages while the agent works.
 
-📡 **Slack Channels** — Chat with your agents from Slack. Multi-agent routing via `@agent-name` prefix. Native "is thinking..." indicator via Slack Assistants API. Session persistence across restarts.
+📡 **Slack & Telegram** — Chat with your agents from Slack or Telegram. Multi-agent routing via `@agent-name` prefix or interactive buttons. Slack Assistants API with native "is thinking..." indicator. Telegram with inline keyboard agent picker and typing dots. Session persistence across restarts.
 
 💓 **Heartbeat** — Autonomous periodic agent runs. Define what an agent does when no one is asking — monitoring, reports, health checks — with results posted to Slack.
 
 📋 **Task Board** — Kanban view with scheduling, priority, real-time progress tracking, and abort. Tasks run on cron schedules or on-demand.
 
-🔌 **MCP Integration** — Discover, authenticate, and inspect MCP servers. One-click OAuth 2.1 authentication. Assign MCP tools to specific agents.
+🔌 **MCP Integration** — Add, remove, authenticate, and inspect MCP servers from the dashboard. One-click OAuth 2.1 with automatic CLI token injection — agents can use authenticated servers immediately.
 
 🧠 **Agent Memory** — Agents persist context across sessions using `[REMEMBER]` tags stored as markdown.
 
@@ -204,6 +204,29 @@ channel_context: |
 
 ---
 
+### Telegram
+
+Chat with your agents from Telegram — simpler setup than Slack, no @mention required in DMs.
+
+**Setup:**
+1. Create a bot via [@BotFather](https://t.me/botfather) — `/newbot`, pick a name and username, copy the token
+2. Add the token in Settings → Agent Fleet → Channel Credentials (type: Telegram)
+3. Create a channel via the dashboard or as `_fleet/channels/my-telegram.md`
+4. Message the bot in Telegram
+
+**Features:**
+- **Zero dependencies** — long-poll via HTTPS, no WebSocket, no SDK
+- **Typing indicator** — `typing...` dots while the agent works (auto-refreshed every 4.5s)
+- **Inline keyboard agent picker** — `/agents` command shows interactive buttons to switch agents
+- **Slash command autocomplete** — commands registered automatically via `setMyCommands`
+- **Agent name prefix** — replies show `[agent-name]` when multiple agents are configured
+- **Group chat support** — add the bot to groups (disable privacy mode via BotFather for full access)
+- **Forum topics** — enable Threaded Mode in BotFather for topic-based conversations
+- **Session persistence** — conversations survive Obsidian restarts via `claude --resume`
+- **4096-char message splitting** — long replies automatically chunked at paragraph boundaries
+
+---
+
 ### Interactive Chat
 
 The chat panel is a first-class Obsidian view — dock it in the sidebar, center, or any split.
@@ -246,7 +269,18 @@ A kanban view for managing agent tasks with five columns:
 
 ### MCP Servers
 
-Discover and manage all MCP (Model Context Protocol) servers configured in Claude Code.
+Add, remove, authenticate, and manage MCP servers directly from the dashboard — no terminal needed.
+
+**Add Server UI:**
+- Click **"Add Server"** on the MCP page to open the form
+- **stdio** — command, arguments, environment variables
+- **HTTP / SSE** — URL, API key (stored securely), custom headers
+- Scope selection (user or local) — defaults to "user" so servers are visible across projects
+- Servers appear immediately after adding, with tools auto-discovered
+
+**Remove Server:**
+- Open any server's detail slideover → click **"Remove Server"**
+- Cleans up CLI registration and stored secrets in one step
 
 **Discovery:**
 - **stdio servers** — spawned and probed directly via JSON-RPC (~1-2s)
@@ -255,12 +289,14 @@ Discover and manage all MCP (Model Context Protocol) servers configured in Claud
 
 **OAuth 2.1 Authentication:**
 
-One-click browser-based auth for MCP servers:
+One-click browser-based auth with unified CLI token injection:
 1. Click "Authenticate" on any server card
 2. Plugin discovers OAuth endpoints automatically
 3. Registers via Dynamic Client Registration
 4. Opens browser for approval (PKCE flow)
-5. Tokens stored in plugin settings, auto-refresh
+5. Tokens stored securely in OS keychain (macOS Keychain, Windows Credential Manager, Linux Secret Service)
+6. Token automatically injected into Claude CLI config — agents can use the server immediately without separate CLI authentication
+7. Background token refresh — expiring tokens are refreshed and re-injected automatically
 
 **Server Management:**
 - Enable/disable toggle per server (writes to Claude's settings)
@@ -386,6 +422,12 @@ Click any run in the dashboard to see full details in a slideover panel.
 | Catch Up Missed Tasks | `true` | Run overdue tasks on startup |
 | Notification Level | `all` | `all`, `failures-only`, `none` |
 
+### Security
+
+All secrets — MCP OAuth tokens, API keys, and channel credentials (Slack/Telegram) — are stored in your OS keychain via Obsidian's SecretStorage API. On first load after updating to v0.6.0, existing plaintext credentials are automatically migrated from `data.json` to the keychain and the plaintext copies are cleared.
+
+Requires Obsidian 1.11.4+ for keychain support. On older versions, credentials remain in `data.json` with a console warning.
+
 ### Channel Settings
 
 | Setting | Default | Description |
@@ -437,11 +479,14 @@ Yes. Each agent has persistent chat sessions that survive Obsidian restarts via
 **Q: Does the Slack bot work when Obsidian is closed?**
 No. The bot runs inside Obsidian via Socket Mode — when Obsidian is closed, the bot goes offline. Slack buffers messages briefly during short disconnects.
 
-**Q: Can I use multiple agents in Slack?**
-Yes. Type `@agent-name: message` to switch agents within a Slack thread. Each agent maintains its own session. Use `/agents` to see available agents.
+**Q: Can I use multiple agents in Slack or Telegram?**
+Yes. Type `@agent-name: message` to switch agents, or use `/agents` to get interactive buttons. Each agent maintains its own session. Works in both Slack and Telegram.
+
+**Q: Which is easier to set up — Slack or Telegram?**
+Telegram. Create a bot via @BotFather (30 seconds), paste the token, create a channel. Slack requires creating an app with Socket Mode, scopes, events, and reinstalls after scope changes.
 
 **Q: What is a heartbeat?**
-An autonomous periodic run — what an agent does on a schedule without user input. Configured via `HEARTBEAT.md` in the agent's folder. Results can be posted to a Slack channel automatically.
+An autonomous periodic run — what an agent does on a schedule without user input. Configured via `HEARTBEAT.md` in the agent's folder. Results can be posted to Slack or Telegram automatically.
 
 ---
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "obsidian-agent-fleet",
-  "version": "0.4.5",
+  "version": "0.7.1",
   "description": "Obsidian plugin for file-backed AI agents, task scheduling, channels (Slack), heartbeat, and interactive chat.",
   "main": "plugin/main.js",
   "bin": {