agent-messenger 2.1.0 → 2.2.0

package/skills/agent-channeltalk/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-channeltalk
-description: Interact with Channel Talk using extracted desktop app credentials - read chats, send messages, search messages, manage groups
-version: 2.1.0
+description: Interact with Channel Talk using extracted desktop app or browser credentials - read chats, send messages, search messages, manage groups
+version: 2.2.0
 allowed-tools: Bash(agent-channeltalk:*)
 metadata:
   openclaw:
@@ -16,7 +16,7 @@ metadata:
 
 # Agent Channel
 
-A TypeScript CLI tool that enables AI agents and humans to interact with Channel Talk workspaces through a simple command interface. Features zero-config credential extraction from the Channel Talk desktop app and multi-workspace support.
+A TypeScript CLI tool that enables AI agents and humans to interact with Channel Talk workspaces through a simple command interface. Features zero-config credential extraction from the Channel Talk desktop app (with browser fallback) and multi-workspace support.
 
 ## Key Concepts
 
@@ -48,16 +48,16 @@ agent-channeltalk chat list
 
 ## Authentication
 
-Credentials are extracted automatically from the Channel Talk desktop app on first use. No manual setup required, no API keys needed. Just run any command and authentication happens silently in the background.
+Credentials are extracted automatically from the Channel Talk desktop app (or Chromium browser as fallback) on first use. No manual setup required, no API keys needed. Just run any command and authentication happens silently in the background.
 
-The Channel Talk desktop app stores auth cookies in a SQLite database. On macOS, cookies are plaintext and no Keychain prompt is needed. On Windows, cookies are DPAPI-encrypted and decrypted automatically. The CLI reads two cookies:
+The Channel Talk desktop app stores auth cookies in a SQLite database. On macOS, cookies are plaintext and no Keychain prompt is needed. On Windows, cookies are DPAPI-encrypted and decrypted automatically. When falling back to a Chromium browser on macOS, cookies require Keychain decryption. The CLI reads two cookies:
 
 - `x-account` (JWT) - your account identity
 - `ch-session-1` (JWT) - your session token
 
-These cookies expire after roughly 30 days. When they expire, the CLI automatically re-extracts fresh cookies from the desktop app on the next command.
+These cookies expire after roughly 30 days. When they expire, the CLI automatically re-extracts fresh cookies from the desktop app or browser on the next command.
 
-**IMPORTANT**: NEVER guide the user to open a web browser, use DevTools, or manually copy tokens. Always use `agent-channeltalk auth extract` to obtain credentials from the desktop app.
+**IMPORTANT**: Always use `agent-channeltalk auth extract` to obtain credentials. The CLI extracts from the desktop app first, falling back to Chromium browsers if the app isn't installed.
 
 ### Multi-Workspace Support
 
@@ -166,7 +166,7 @@ If a memorized ID returns an error (chat not found, group not found), remove it
 ### Auth Commands
 
 ```bash
-# Extract cookies from Channel Talk desktop app (usually automatic)
+# Extract cookies from Channel Talk desktop app or browser (usually automatic)
 agent-channeltalk auth extract
 
 # Check auth status
@@ -379,7 +379,7 @@ Use **agent-channeltalk** when you want zero-config access acting as yourself. U
 
 ## Limitations
 
-- macOS and Windows only (Channel Talk desktop app required)
+- Desktop app extraction: macOS and Windows. Browser fallback: macOS, Linux, and Windows.
 - No real-time events / WebSocket connection
 - No file upload support
 - No message editing or deletion

package/skills/agent-channeltalk/references/authentication.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-agent-channeltalk uses cookies extracted directly from the Channel Talk desktop application. This provides seamless, zero-config authentication without API keys or manual token management.
+agent-channeltalk uses cookies extracted from the Channel Talk desktop application, with automatic fallback to Chromium browser profiles (Chrome, Chrome Canary, Edge, Arc, Brave, Vivaldi, Chromium) when the desktop app isn't installed.
 
 ## Cookie Extraction
 
@@ -22,17 +22,19 @@ agent-channeltalk auth extract
 
 ### How It Works
 
-1. Locates the Channel Talk desktop app's SQLite cookie database on macOS
-2. Copies the database to a temp file (avoids locking the original)
-3. Reads `x-account` and `ch-session-1` cookies for `*.channel.io`
-4. Validates cookies against the Channel Talk API
-5. Discovers ALL workspaces you belong to
-6. Stores credentials in `~/.config/agent-messenger/channel-credentials.json`
-7. Sets the first workspace as the current active workspace
+1. Locates the Channel Talk desktop app's SQLite cookie database
+2. If the desktop app isn't found, scans Chromium browser profiles for Channel Talk cookies
+3. Copies the database to a temp file (avoids locking the original)
+4. Reads `x-account` and `ch-session-1` cookies for `*.channel.io`
+5. Decrypts encrypted cookies if needed (macOS Keychain, Linux peanuts, Windows DPAPI)
+6. Validates cookies against the Channel Talk API
+7. Discovers ALL workspaces you belong to
+8. Stores credentials in `~/.config/agent-messenger/channel-credentials.json`
+9. Sets the first workspace as the current active workspace
 
-### No Keychain Prompt
+### Keychain Prompt (Browser Extraction on macOS)
 
-Unlike Slack and Discord, Channel Talk stores cookies in a plaintext SQLite database. There's no OS-level encryption, so no Keychain password prompt is needed. Extraction is completely silent.
+When extracting from the desktop app, no Keychain prompt is needed (cookies are plaintext). When extracting from a Chromium browser, your Mac may prompt for Keychain access to decrypt the browser's cookies.
 
 ### What Gets Extracted
 
@@ -56,7 +58,7 @@ Unlike Slack and Discord, Channel Talk stores cookies in a plaintext SQLite data
 
 The tool checks the sandboxed path first, then falls back to the direct path.
 
-> **Note**: Only macOS is supported. Linux and Windows are not currently supported.
+> **Note**: Desktop app extraction supports macOS and Windows. Browser fallback extraction supports macOS, Linux, and Windows.
 
 ## Multi-Workspace Management
 
@@ -245,16 +247,17 @@ No credentials are configured and auto-extraction failed:
 
 ### Channel Talk desktop app not found
 
-The CLI only supports macOS. It looks for the cookie database in two locations:
+The CLI first checks for the desktop app, then falls back to Chromium browsers.
 
-1. **Mac App Store version**: `~/Library/Containers/com.zoyi.channel.desk.osx/Data/Library/Application Support/Channel Talk/Cookies`
-2. **Electron version**: `~/Library/Application Support/Channel Talk/Cookies`
+Desktop app paths:
+1. **macOS (Mac App Store)**: `~/Library/Containers/com.zoyi.channel.desk.osx/Data/Library/Application Support/Channel Talk/Cookies`
+2. **macOS (Electron)**: `~/Library/Application Support/Channel Talk/Cookies`
+3. **Windows**: `%APPDATA%/Channel Talk/Network/Cookies`
 
-If neither path exists:
+If neither the desktop app nor browser cookies are found:
 
-1. Install the Channel Talk desktop app from the Mac App Store or download it directly
-2. Log in to your account
-3. Run `agent-channeltalk auth extract`
+1. Log in to desk.channel.io in a Chromium browser (Chrome, Edge, Arc, Brave) — the CLI will extract from browser automatically
+2. Or install the Channel Talk desktop app, log in, and run `agent-channeltalk auth extract`
 
 ### Cookies expired or invalid
 

package/skills/agent-channeltalkbot/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-channeltalkbot
 description: Interact with Channel Talk workspaces using API credentials - send messages, read chats, manage groups and bots
-version: 2.1.0
+version: 2.2.0
 allowed-tools: Bash(agent-channeltalkbot:*)
 metadata:
   openclaw:

package/skills/agent-discord/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-discord
 description: Interact with Discord servers - send messages, read channels, manage reactions
-version: 2.1.0
+version: 2.2.0
 allowed-tools: Bash(agent-discord:*)
 metadata:
   openclaw:
@@ -16,7 +16,7 @@ metadata:
 
 # Agent Discord
 
-A TypeScript CLI tool that enables AI agents and humans to interact with Discord servers through a simple command interface. Features seamless token extraction from the Discord desktop app and multi-server support.
+A TypeScript CLI tool that enables AI agents and humans to interact with Discord servers through a simple command interface. Features seamless token extraction from the Discord desktop app (with browser fallback) and multi-server support.
 
 ## Quick Start
 
@@ -33,11 +33,11 @@ agent-discord channel list
 
 ## Authentication
 
-Credentials are extracted automatically from the Discord desktop app on first use. No manual setup required — just run any command and authentication happens silently in the background.
+Credentials are extracted automatically from the Discord desktop app (or Chromium browser as fallback) on first use. No manual setup required — just run any command and authentication happens silently in the background.
 
 On macOS, the system may prompt for your Keychain password the first time (required to decrypt Discord's stored token). This is a one-time prompt.
 
-**IMPORTANT**: NEVER guide the user to open a web browser, use DevTools, or manually copy tokens from a browser. Always use `agent-discord auth extract` to obtain tokens from the desktop app.
+**IMPORTANT**: Always use `agent-discord auth extract` to obtain tokens. The CLI extracts from the desktop app first, falling back to Chromium browsers if the app isn't installed.
 
 ### Multi-Server Support
 
@@ -134,7 +134,7 @@ If a memorized ID returns an error (channel not found, server not found), remove
 ### Auth Commands
 
 ```bash
-# Extract token from Discord desktop app (usually automatic)
+# Extract token from Discord desktop app or browser (usually automatic)
 agent-discord auth extract
 agent-discord auth extract --debug
 

package/skills/agent-discord/references/authentication.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-agent-discord uses Discord's user token extracted directly from the Discord desktop application. This provides seamless authentication without manual token management.
+agent-discord uses Discord's user token extracted from the Discord desktop application, with automatic fallback to Chromium browser profiles (Chrome, Chrome Canary, Edge, Arc, Brave, Vivaldi, Chromium) when the desktop app isn't installed.
 
 ## Token Extraction
 
@@ -22,10 +22,11 @@ This command:
 1. Detects your operating system (macOS, Linux, Windows)
 2. Locates the Discord desktop app data directory
 3. Reads the LevelDB storage containing session data
-4. Extracts user token
-5. Validates token against Discord API before saving
-6. Discovers ALL joined servers
-7. Stores credentials securely in `~/.config/agent-messenger/discord-credentials.json`
+4. If the desktop app isn't found, scans Chromium browser profiles for Discord tokens
+5. Extracts user token (handles encrypted tokens on all platforms)
+6. Validates token against Discord API before saving
+7. Discovers ALL joined servers
+8. Stores credentials securely in `~/.config/agent-messenger/discord-credentials.json`
 
 ### Platform-Specific Paths
 
@@ -209,9 +210,8 @@ This shows:
 
 **Solution**:
 
-1. Install Discord desktop app
-2. Log in to your account
-3. Run `agent-discord auth extract` again
+1. Log in to discord.com in a Chromium browser (Chrome, Edge, Arc, Brave) — the CLI will extract from browser automatically
+2. Or install the Discord desktop app, log in, and run `agent-discord auth extract` again
 
 ### "No Discord token found"
 

package/skills/agent-discordbot/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-discordbot
 description: Interact with Discord servers using bot tokens - send messages, read channels, manage reactions
-version: 2.1.0
+version: 2.2.0
 allowed-tools: Bash(agent-discordbot:*)
 metadata:
   openclaw:

package/skills/agent-instagram/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-instagram
 description: Interact with Instagram DMs - send messages, read conversations, manage accounts
-version: 2.1.0
+version: 2.2.0
 allowed-tools: Bash(agent-instagram:*)
 metadata:
   openclaw:
@@ -16,7 +16,7 @@ metadata:
 
 # Agent Instagram
 
-An Instagram DM CLI for AI agents. Authenticates with username/password (supports 2FA), uses Instagram's private mobile API to read and send direct messages.
+An Instagram DM CLI for AI agents. Supports browser cookie extraction (zero-config, extracts from Chromium browsers) and username/password authentication (with 2FA). Uses Instagram's private mobile API to read and send direct messages.
 
 Use one of these entrypoints:
 - Global install: `agent-instagram ...`
@@ -25,7 +25,8 @@ Use one of these entrypoints:
 ## Key Concepts
 
 - **Thread ID** = Instagram's identifier for a DM conversation. Numeric string returned by `chat list`.
-- **Username/password auth** = authenticates using Instagram credentials. Supports two-factor authentication via SMS or authenticator app.
+- **Browser cookie extraction** = recommended auth method. Extracts cookies from Chromium browsers (Chrome, Chrome Canary, Edge, Arc, Brave, Vivaldi, Chromium) where you're logged into instagram.com. Zero-config.
+- **Username/password auth** = fallback method. Authenticates using Instagram credentials. Supports two-factor authentication via SMS or authenticator app.
 - **HTTP-based** = each command makes HTTP requests and returns. No persistent connection or background process.
 - **Multi-account** = multiple Instagram accounts can be stored. Use `auth list` and `auth use` to switch between them.
 - **DM-only** = this CLI focuses on Instagram Direct Messages. It does not manage posts, stories, or followers.
@@ -33,7 +34,10 @@ Use one of these entrypoints:
 ## Quick Start
 
 ```bash
-# Log in with Instagram credentials
+# Extract cookies from browser (recommended — zero-config)
+agent-instagram auth extract
+
+# Or: Log in with Instagram credentials (fallback)
 agent-instagram auth login --username myaccount --password "mypassword"
 
 # List DM conversations
@@ -45,7 +49,30 @@ agent-instagram message send <thread-id> "Hello from agent-instagram"
 
 ## Authentication Flow
 
-Instagram uses username/password authentication with optional two-factor verification. Sessions are persisted locally so you don't need to re-authenticate for every command.
+Instagram supports two authentication methods:
+
+1. **Browser cookie extraction** (recommended): Extracts your session cookies from a Chromium browser where you're logged into instagram.com. Zero-config, no password needed.
+2. **Username/password login**: Authenticates using Instagram credentials with optional two-factor verification.
+
+Sessions are persisted locally so you don't need to re-authenticate for every command. Browser extraction auto-runs when no session exists.
+
+### Browser Cookie Extraction (Recommended)
+
+`agent-instagram auth extract` reads your Instagram session cookies from Chrome, Edge, Arc, Brave, Vivaldi, or Chromium. You must be logged into instagram.com in one of these browsers.
+
+```bash
+# Extract cookies from browser — zero-config
+agent-instagram auth extract
+
+# With debug output
+agent-instagram auth extract --debug
+```
+
+**How it works**: The CLI reads Instagram cookies (`sessionid`, `csrftoken`, `ds_user_id`) directly from the browser's SQLite cookie database. No browser automation, no password prompts. The session is stored locally in `~/.config/agent-messenger/`.
+
+**When to re-extract**: Browser cookies expire. When your session expires, re-run `agent-instagram auth extract` or let auto-extraction handle it (the CLI attempts extraction automatically when no valid session exists).
+
+**Supported browsers**: Chrome, Chrome Canary, Edge, Arc, Brave, Vivaldi, Chromium
 
 ### Agent Behavior (MANDATORY)
 
@@ -59,11 +86,20 @@ agent-instagram auth list
 
 If accounts exist, use `agent-instagram auth use <account-id>` and retry the original command.
 
-**Step 2: If no accounts, ask for credentials**
+**Step 2: Try browser extraction first**
+
+```bash
+agent-instagram auth extract
+# -> {"authenticated":true,"account_id":"12345678","username":"myaccount"}
+```
+
+If extraction succeeds, proceed with the original command.
+
+**Step 3: If extraction fails, ask for credentials**
 
 Ask the user for their Instagram username and password. These are the ONLY things the user needs to provide.
 
-**Step 3: Start login**
+**Step 4: Start login**
 
 ```bash
 agent-instagram auth login --username myaccount --password "mypassword"
@@ -92,6 +128,8 @@ After successful auth, immediately execute whatever the user originally asked fo
 ### Common Auth Commands
 
 ```bash
+agent-instagram auth extract                 # Extract cookies from browser (recommended)
+agent-instagram auth extract --debug         # Extract with debug output
 agent-instagram auth status                  # Check current auth state
 agent-instagram auth status --account <id>   # Check specific account
 agent-instagram auth list                    # List all stored accounts
@@ -166,6 +204,10 @@ Never store auth credentials, passwords, session tokens, or any sensitive data.
 ### Auth Commands
 
 ```bash
+# Extract cookies from browser (recommended — zero-config)
+agent-instagram auth extract
+agent-instagram auth extract --debug
+
 # Log in (interactive: prompts for username/password)
 agent-instagram auth login
 
@@ -334,8 +376,8 @@ All commands return consistent error format:
 
 Common errors:
 
-- `Not authenticated` - no account configured. Run `auth login`.
-- `Session expired or missing` - session is no longer valid. Run `auth login` again.
+- `Not authenticated` - no account configured. Run `auth extract` or `auth login`.
+- `Session expired or missing` - session is no longer valid. Run `auth extract` to re-extract from browser, or `auth login` to log in again.
 - `Login failed` - wrong username/password. Double-check credentials.
 - `Two-factor authentication failed` - wrong 2FA code. Get a new code and try `auth verify` again.
 - `Rate limited` - too many requests. Wait and retry.

package/skills/agent-instagram/references/authentication.md

@@ -2,9 +2,38 @@
 
 ## Overview
 
-agent-instagram uses username/password authentication against Instagram's private mobile API. The CLI logs in as a mobile client, so your existing app sessions are never affected. Each command makes HTTP requests on demand. No persistent connection or background process.
+agent-instagram supports two authentication methods: browser cookie extraction (recommended, zero-config) and username/password login (fallback). The CLI uses Instagram's private mobile API. Each command makes HTTP requests on demand. No persistent connection or background process.
 
-## Username/Password Login
+## Browser Cookie Extraction (Recommended)
+
+### How It Works
+
+1. Scans Chromium browser profiles (Chrome, Chrome Canary, Edge, Arc, Brave, Vivaldi, Chromium)
+2. Reads the SQLite cookie database for `.instagram.com` cookies
+3. Decrypts encrypted cookies using the browser's encryption key (macOS Keychain, Linux peanuts, Windows DPAPI)
+4. Extracts `sessionid`, `ds_user_id`, `csrftoken`, and optional cookies (`mid`, `ig_did`, `rur`)
+5. Validates the session against the Instagram API to resolve your username
+6. Stores credentials in `~/.config/agent-messenger/`
+
+### Usage
+
+```bash
+# Extract cookies from browser (recommended)
+agent-instagram auth extract
+
+# With debug output
+agent-instagram auth extract --debug
+```
+
+### Auto-Extraction
+
+When no valid session exists, the CLI automatically attempts browser extraction before prompting for credentials. This means most users never need to run `auth extract` manually.
+
+### Keychain Prompt (macOS)
+
+On macOS, your Mac may prompt for your password to access Keychain. This is required because Chromium browsers encrypt cookies using macOS Keychain. Your password is never stored or transmitted.
+
+## Username/Password Login (Fallback)
 
 ### How It Works
 
@@ -227,7 +256,10 @@ If commands start failing with auth errors:
 # Check if still authenticated
 agent-instagram auth status
 
-# Re-login if needed
+# Re-extract from browser (if logged in to instagram.com)
+agent-instagram auth extract
+
+# Or re-login with credentials
 agent-instagram auth login
 
 # Verify it worked

package/skills/agent-kakaotalk/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-kakaotalk
 description: Interact with KakaoTalk - send messages, read chats, manage conversations
-version: 2.1.0
+version: 2.2.0
 allowed-tools: Bash(agent-kakaotalk:*)
 metadata:
   openclaw:

package/skills/agent-line/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-line
 description: Interact with LINE - send messages, read chats, manage conversations
-version: 2.1.0
+version: 2.2.0
 allowed-tools: Bash(agent-line:*)
 metadata:
   openclaw:

package/skills/agent-slack/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-slack
 description: Interact with Slack workspaces - send messages, read channels, manage reactions
-version: 2.1.0
+version: 2.2.0
 allowed-tools: Bash(agent-slack:*)
 metadata:
   openclaw:
@@ -16,7 +16,7 @@ metadata:
 
 # Agent Slack
 
-A TypeScript CLI tool that enables AI agents and humans to interact with Slack workspaces through a simple command interface. Features seamless token extraction from the Slack desktop app and multi-workspace support.
+A TypeScript CLI tool that enables AI agents and humans to interact with Slack workspaces through a simple command interface. Features seamless token extraction from the Slack desktop app (with browser fallback) and multi-workspace support.
 
 ## Quick Start
 
@@ -33,11 +33,11 @@ agent-slack channel list
 
 ## Authentication
 
-Credentials are extracted automatically from the Slack desktop app on first use. No manual setup required — just run any command and authentication happens silently in the background.
+Credentials are extracted automatically from the Slack desktop app (or Chromium browser as fallback) on first use. No manual setup required — just run any command and authentication happens silently in the background.
 
 On macOS, the system may prompt for your Keychain password the first time (required to decrypt Slack's stored token). This is a one-time prompt.
 
-**IMPORTANT**: NEVER guide the user to open a web browser, use DevTools, or manually copy tokens from a browser. Always use `agent-slack auth extract` to obtain tokens from the desktop app.
+**IMPORTANT**: Always use `agent-slack auth extract` to obtain tokens. The CLI extracts from the desktop app first, falling back to Chromium browsers if the app isn't installed.
 
 ### Multi-Workspace Support
 
@@ -137,7 +137,7 @@ If a memorized ID returns an error (channel not found, user not found), remove i
 ### Auth Commands
 
 ```bash
-# Extract tokens from Slack desktop app (usually automatic)
+# Extract tokens from Slack desktop app or browser (usually automatic)
 agent-slack auth extract
 agent-slack auth extract --debug
 

package/skills/agent-slack/references/authentication.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-agent-slack uses Slack's web client credentials (xoxc token + xoxd cookie) extracted directly from the Slack desktop application. This provides seamless authentication without manual token management.
+agent-slack uses Slack's web client credentials (xoxc token + xoxd cookie) extracted from the Slack desktop application, with automatic fallback to Chromium browser profiles (Chrome, Chrome Canary, Edge, Arc, Brave, Vivaldi, Chromium) when the desktop app isn't installed.
 
 ## Token Extraction
 
@@ -22,10 +22,11 @@ This command:
 1. Detects your operating system (macOS, Linux, Windows)
 2. Locates the Slack desktop app data directory (supports both direct download and App Store versions on macOS)
 3. Reads the LevelDB storage containing session data
-4. Decrypts cookies using macOS Keychain (for sandboxed App Store version)
-5. Validates tokens against Slack API before saving
-6. Extracts xoxc token and xoxd cookie for ALL logged-in workspaces
-7. Stores credentials securely in `~/.config/agent-messenger/slack-credentials.json`
+4. If the desktop app isn't found, scans Chromium browser profiles for Slack tokens in `localStorage.localConfig_v2` and `d` cookie
+5. Decrypts cookies using macOS Keychain, Linux keyring, or Windows DPAPI
+6. Validates tokens against Slack API before saving
+7. Extracts xoxc token and xoxd cookie for ALL logged-in workspaces
+8. Stores credentials securely in `~/.config/agent-messenger/slack-credentials.json`
 
 ### Platform-Specific Paths
 
@@ -237,9 +238,8 @@ This shows:
 
 **Solution**:
 
-1. Install Slack desktop app
-2. Log in to your workspace(s)
-3. Run `agent-slack auth extract` again
+1. Log in to your workspace at app.slack.com in a Chromium browser (Chrome, Edge, Arc, Brave) — the CLI will extract from browser automatically
+2. Or install the Slack desktop app, log in to your workspace(s), and run `agent-slack auth extract` again
 
 ### "No workspaces found"
 

package/skills/agent-slackbot/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-slackbot
 description: Interact with Slack workspaces using bot tokens - send messages, read channels, manage reactions
-version: 2.1.0
+version: 2.2.0
 allowed-tools: Bash(agent-slackbot:*)
 metadata:
   openclaw:

package/skills/agent-teams/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-teams
 description: Interact with Microsoft Teams - send messages, read channels, manage reactions
-version: 2.1.0
+version: 2.2.0
 allowed-tools: Bash(agent-teams:*)
 metadata:
   openclaw:
@@ -16,7 +16,7 @@ metadata:
 
 # Agent Teams
 
-A TypeScript CLI tool that enables AI agents and humans to interact with Microsoft Teams through a simple command interface. Features seamless token extraction from the Teams desktop app and multi-team support.
+A TypeScript CLI tool that enables AI agents and humans to interact with Microsoft Teams through a simple command interface. Features seamless token extraction from the Teams desktop app (with browser fallback) and multi-team support.
 
 ## Quick Start
 
@@ -33,11 +33,11 @@ agent-teams channel list <team-id>
 
 ## Authentication
 
-Credentials are extracted automatically from the Teams desktop app on first use. No manual setup required — just run any command and authentication happens silently in the background.
+Credentials are extracted automatically from the Teams desktop app (or Chromium browser as fallback) on first use. No manual setup required — just run any command and authentication happens silently in the background.
 
 Teams tokens expire in 60-90 minutes. The CLI automatically re-extracts a fresh token when the current one expires, so you don't need to manage token lifecycle manually.
 
-**IMPORTANT**: NEVER guide the user to open a web browser, use DevTools, or manually copy tokens from a browser. Always use `agent-teams auth extract` to obtain tokens from the desktop app.
+**IMPORTANT**: Always use `agent-teams auth extract` to obtain tokens. The CLI extracts from the desktop app first, falling back to Chromium browsers if the app isn't installed.
 
 ### Multi-Team Support
 
@@ -145,7 +145,7 @@ If a memorized ID returns an error (channel not found, team not found), remove i
 ### Auth Commands
 
 ```bash
-# Extract token from Teams desktop app (usually automatic)
+# Extract token from Teams desktop app or browser (usually automatic)
 agent-teams auth extract
 agent-teams auth extract --debug
 
@@ -400,7 +400,7 @@ See the [Teams SDK documentation](https://agent-messenger.dev/docs/sdk/teams) fo
 - No webhook support
 - Plain text messages only (no adaptive cards in v1)
 - User tokens only (no app tokens)
-- **Token expires in 60-90 minutes** - auto-refreshed, but requires Teams desktop app to be logged in
+- **Token expires in 60-90 minutes** - auto-refreshed, but requires Teams desktop app or browser to be logged in
 
 ## Troubleshooting
 

package/skills/agent-teams/references/authentication.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-agent-teams uses Microsoft Teams' user token extracted directly from the Teams desktop application. This provides seamless authentication without manual token management.
+agent-teams uses Microsoft Teams' user token extracted from the Teams desktop application, with automatic fallback to Chromium browser profiles (Chrome, Chrome Canary, Edge, Arc, Brave, Vivaldi, Chromium) when the desktop app isn't installed.
 
 ## TOKEN EXPIRY WARNING
 
@@ -56,10 +56,11 @@ This command:
 1. Detects your operating system (macOS, Linux, Windows)
 2. Locates the Teams desktop app data directory
 3. Reads the **Cookies SQLite database** containing session data
-4. Extracts `skypetoken_asm` cookie value
-5. Validates token against Teams API before saving
-6. Discovers ALL joined teams
-7. Stores credentials securely in `~/.config/agent-messenger/teams-credentials.json`
+4. If the desktop app isn't found, scans Chromium browser profiles for Teams cookies
+5. Extracts `skypetoken_asm` cookie value
+6. Validates token against Teams API before saving
+7. Discovers ALL joined teams
+8. Stores credentials securely in `~/.config/agent-messenger/teams-credentials.json`
 
 ### Platform-Specific Paths
 
@@ -280,9 +281,8 @@ This shows:
 
 **Solution**:
 
-1. Install Microsoft Teams desktop app
-2. Log in to your account
-3. Run `agent-teams auth extract` again
+1. Log in to teams.microsoft.com in a Chromium browser (Chrome, Edge, Arc, Brave) — the CLI will extract from browser automatically
+2. Or install the Microsoft Teams desktop app, log in, and run `agent-teams auth extract` again
 
 ### "No Teams token found"
 

package/skills/agent-telegram/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: agent-telegram
 description: Interact with Telegram through TDLib - authenticate, inspect chats, and send messages
-version: 2.1.0
+version: 2.2.0
 allowed-tools: Bash(agent-telegram:*)
 ---