​

Multi-Channel Integration

​

Supported Channels

​

iMessage Deep Integration

​

Setup

1. Install BlueBubbles on a macOS machine with iMessage active
2. Navigate to Settings > Channels > iMessage in the GUI
3. Enter your BlueBubbles API URL and password
4. Optionally provide a Webhook URL — the agent registers it automatically on connect
5. Enable Private API in BlueBubbles for quoted replies, read receipts, and typing indicators

​

Graceful Degradation

​

Setup

​

Public Ingress Guidance

Honest boundary: Ingress guidance is per-channel transport classification, not a live connectivity test. Webhook delivery still depends on your tunnel/proxy being reachable from the platform.

​

WeChat (via iLink)

1. Navigate to Settings > Channels > WeChat in the GUI
2. Click Scan to Connect — a QR code dialog appears
3. Open WeChat on your phone and scan the QR code
4. Confirm on your phone — the dialog updates in real-time (SSE streaming)
5. Done — your WeChat is connected

​

WeChat Official Account (draft publishing)

1. Settings → Channels → WeChat Official — AppID, AppSecret, IP whitelist, test connection.
2. Format vault Markdown with wechat-article-formatter → .wechat.html artifact.
3. Preview in chat → Push to WeChat Draft (title + cover; first inline image auto-suggested).
4. Publish manually from mp.weixin.qq.com draft box.

​

WhatsApp (via Baileys)

1. Navigate to Settings > Channels > WhatsApp in the GUI
2. Click Scan to Connect — same QR code dialog as WeChat
3. Open WhatsApp on your phone → Linked Devices → scan the QR code
4. Connection established automatically

​

Email (IMAP + SMTP)

1. Open Settings > Channels > Email
2. Configure IMAP (inbox) and SMTP (outbox) server, port, and credentials
3. Save — polling starts automatically

• Supports Gmail, Outlook, QQ Mail, 163 Mail, Foxmail, and other major clients
• Three-layer detection: Subject prefix (Fwd:/FW:/转发:/轉發:) → Body separator → MIME attachment
• Just write “expense this” or “translate to English” when forwarding — Agent sees both your instruction and the full original email, then executes precisely
• Full CJK email client support with adaptive charset decoding (gb2312/GBK/UTF-8)

• If you have multiple Agents configured, route incoming messages using prefixes or slash commands: /coder review this PR routes to your “coder” agent, /accountant expense this routes to your “accountant” agent.
• BYOD Custom Domain Support: Protect sender reputation by connecting your own domain or private SMTP instead of a public shared domain (which competitors found immediately blacklisted by Outlook/Exchange).
• Rename & Release Window: Dedicated agent email handles support safe renaming and tombstone releases without locking an account forever.
• Zero-Token System Command Bypass: Diagnostics and status management commands run locally at zero token cost and remain accessible even if conversation quotas hit 100%.

• Strict 4-Hop Limit: Each inter-agent email increments X-Myrm-Hop-Count, cutting off runaway threads at 4 hops.
• Terminal Courtesy Ack Suppression: When a peer agent sends pure acknowledgements (“Thanks!”, “Confirmed”), the receiving agent silently terminates rather than triggering another round, eliminating token-burning ping-pong loops.
• Outbound Human Approval: Any outgoing email addressed to external humans requires explicit approval in the UI before transmission.
• Attachment Text Extraction: PDF and Office attachments (docx / xlsx / xls / pptx / ppt) are text-extracted by default and handed to the Agent together with the message body. Up to 4 attachments per email are processed, each at most 20 MB; text beyond 200,000 characters is cut off with a note stating the full length. Other attachment types (JSON, archives, …) are announced by file name only and their content is not read.
• Sandbox Magic Link Auto-Activation: When signing up for third-party services, incoming verification emails automatically have their confirmation links extracted and safely verified inside a sandboxed browser (browser_navigate), turning unclickable text into full service onboarding.
• 4-Tuple Enclave Multi-User Sharing: Allows multiple users (e.g., family members sharing a household budget agent) to communicate with the same bot instance; 4-tuple enclave routing (routing_enclave_key) guarantees personal conversations remain strictly isolated while common ledgers stay shared.

​

Telegram

1. Navigate to Settings > Channels > Telegram
2. Enter your Bot Token (get one from @BotFather) and an optional Webhook URL
3. Save — the bot connects and begins receiving messages

​

iMessage (via BlueBubbles)

1. Settings → Channels → iMessage
2. Enter your BlueBubbles Server API URL (e.g. http://127.0.0.1:1234) and Password
3. Configure the webhook URL and save
4. (Optional) Configure group wake-word regex under “Mention Patterns” (default: ^@?(?:Myrm|myrm|小助手|助手)\b)

• Apple Watch Wrist Reach: No third-party Watch app required. Text your agent in the native Messages app, and approve high-risk tool execution (HITL) via Tapback 👍 reactions.
• Group Wake-Word & Prefix Cleaning: In group chats, wake words are automatically matched and stripped along with the punctuation after them, so the model sees the message without the leading wake word.
• Health Diagnostics & Helper Status: Real-time diagnostic indicators for BlueBubbles Private API and Helper connection.

​

Slack

Honest boundary: Hermes offers an optional rich-blocks mode that turns very long markdown (tables, headers) into native Slack layout blocks. Myrm today focuses on reliable mrkdwn + interactive buttons — enough for day-to-day team chat. Complex table layouts may fall back to monospace formatting.

​

SMS (Twilio)

1. Open Settings > Channels > SMS
2. Enter your Twilio Account SID, Auth Token, and Phone Number (E.164 format, e.g. +15551234567)
3. Copy the auto-generated Webhook URL and paste it into your Twilio Console > Phone Numbers > Messaging webhook
4. Click Test Connection to verify

• Bidirectional: receive SMS from any phone → Agent processes → replies via SMS
• Long messages are automatically split at natural boundaries (max 1600 chars per segment)
• Twilio signature verification ensures only legitimate messages are processed

​

Message Types

• Text messages with platform-appropriate formatting
• Image / document / audio / video attachments (MediaType enum)
• File uploads with automatic type detection

​

Bi-directional File Transfer

​

Inbound (User → Agent)

​

Outbound (Agent → User)

​

Artifact Deep Links

​

Channel-Aware Output Adaptation

​

Outbound Noise Filtering

• 🔍 Searching: AI coding tools 2025 (not just “Searching the web…”)
• 📄 Reading: config/settings.yaml (not just “Reading file…”)
• ⏳ **notion_query** — Search meeting notes (custom MCP tools get automatic coverage)

​

Pre-hoc Guidance (channel_output_hints)

• Telegram: Tables, LaTeX, and nested lists render natively via Bot API 10.1 Rich Message; the hint is only active when Rich is unavailable
• WhatsApp: “Markdown does NOT render — use plain text only”
• Discord: “Messages over 2000 chars are split automatically”
• Voice: “Speak as you would to a person in conversation”

​

IM Behavior Persona (auto-injected)

• Concise chat style: replies like a chat conversation, not a textbook
• Long content → file + summary: content exceeding ~200 characters is written to a workspace file; the IM reply contains only a one-sentence summary + Artifact deep link
• Focused clarification: asks at most 1-2 key questions when user intent is unclear

​

Post-hoc Format Downgrade (renderer)

• supports_tables=false → Markdown tables converted to bullet lists
• supports_latex=false → LaTeX formulas stripped to plain text
• HTML/SVG code blocks replaced with short placeholders on IM channels
• Orphan citation markers auto-cleaned when no sources are present

​

Per-Message Cost Display

💰 claude-sonnet-4-20250514 | 2.5k tokens | ~$0.0035

• Zero-cost replies are hidden — cached or free-model responses show no footer
• Emoji toggle — disable the 💰 prefix via user config while keeping the data
• Feishu cards — cost appears as a native note element alongside the timestamp
• Precision — costs always show 4 decimal places for accurate tracking

​

Smart Message Splitting

• Code fence state machine ensures code blocks are properly closed and reopened across chunks
• Intelligent line splitting at whitespace and punctuation boundaries
• Configurable overflow tolerance for semantic preservation
• Per-channel length limits (e.g., Discord 2000 chars, Telegram 4096 HTML / 32000 Rich Message)

​

Telegram Rich Message (Bot API 10.1)

1. Rich Message — tables, LaTeX formulas, and nested lists render natively (32KB limit)
2. HTML — auto-converted with ASCII monospace table degradation (4096 UTF-16 limit)
3. Plain text — last resort when HTML parsing fails

​

Group Chat Features

​

AllowPolicy

​

GroupTriggerMode

​

Topic Binding

• Thread level: Bound to a specific topic/thread
• Chat level: Bound to a specific group/conversation
• Channel level: Bound to the entire channel

​

Topic Workspace Binding (Vault / Project)

​

Obsidian Vault Write Fidelity

1. Frontmatter preserve — if the LLM drops the --- YAML block while editing the body, the write guard reinjects the pre-edit frontmatter before save (date:, tags:, Dataview fields stay intact).
2. No prettier on vault notes — FormatObserver skips .md files under a .obsidian/ vault root so automated formatting cannot strip metadata.

​

Thread Follow-Up

​

Guest Mention

​

Precise Bot ID Matching

​

GroupContextBuffer

​

SessionGate

​

Deterministic Pre-LLM Processing

​

What this means for users

• Common questions answered instantly — FAQ hits skip the LLM entirely, saving both time and money
• Sensitive content blocked automatically — compliance-ready without manual moderation
• Fast commands with zero wait — /stop, /new, /status execute immediately
• Rapid messages handled gracefully — burst messages are merged, not processed redundantly
• No token waste — only messages that genuinely need AI reasoning reach the model

​

Agent-Initiated Notifications

​

How It Works

1. In Agent settings → Notification Channels, pick a channel from your currently running integrations (dynamic list with human-readable names — new channels appear without a frontend release), then select a recipient from paired contacts (or enter an ID manually)
2. The agent calls channel_notify_tool when it needs to alert you (task completion, anomaly detection, scheduled report ready)
3. Optionally attach files or images — local paths and URLs are auto-resolved with correct media type detection
4. Delivery uses send_tracked for a synchronous success/failure result (same retry policy as critical channel messages), not fire-and-forget queue drops

vs Notification Deliveries: Agent settings → Notification Channels whitelists channel_notify_tool only. Settings → Notification Deliveries routes system events (OAuth, budget, pairing, channel health). They are not interchangeable.

​

Security

Test coverage (2026-09-03): 171+ automated tests (including readonly mode guard, sandbox file validation, DLQ/toast chain, sub-agent isolation, attachment path sandbox) & live Chrome E2E passing.

​

Example Scenarios

• Scheduled task completes at 3 AM → agent sends summary + report PDF to your Telegram
• Long-running code analysis finishes → results + generated chart pushed to Slack channel
• Anomaly detected in monitored data → alert with dashboard screenshot sent to configured target

​

Web Push (Offline Notifications)

​

Supported Events

​

Setup

1. Navigate to Settings > System > Push Notifications
2. Toggle Enable — your browser asks for notification permission
3. Done. Notifications arrive even with the browser tab closed.

​

Platform Notes

​

Security & Maintenance

• VAPID key auto-generation — server creates and persists keys on first boot, zero configuration
• Expired subscription cleanup — push failures (410/404) automatically remove stale subscriptions
• No third-party service — pushes go directly to browser vendor endpoints (Google FCM, Apple APNs, Mozilla autopush)
• Tauri-aware — the setting card is hidden in desktop app builds where native notifications already work

​

One-click approval deep links

• Approval requests navigate to /{chat_id}?approval={id}; the WebUI opens the global ApprovalDrawer and strips the query param for a clean URL
• Service Worker routing sanitizes same-origin paths and, when your chat tab is already open, calls navigate() instead of focus-only — so a new approval on an open tab still opens the drawer (OpenClaw’s SW only compares pathname and misses this)
• Chrome MCP E2E verified — hot tab + cold start deeplink paths (2026-07)

​

Background Task Auto-Reply

• Thread-precise delivery — replies land in the exact thread where you started the task
• Localized notifications — messages respect your language preference (English, Chinese, and more)
• Failure alerts — if a task fails, you get an error summary instead of silence
• Reliable delivery — uses the same retry infrastructure as all channel messages
• Non-disruptive — runs independently of your notification settings; this is a direct reply, not a broadcast

​

Goal Completion Auto-Reply

• Thread-precise delivery — replies land in the exact thread where you started the goal
• Localized notifications — messages respect the language you used when creating the goal (English, Chinese, Japanese, Traditional Chinese)
• Deeplink button — “Continue in browser” opens the full Goal detail with execution summary in WebUI
• Success & failure coverage — both completed and failed goals trigger a notification
• Consistent infrastructure — uses the same delivery pipeline as /btw background task notifications

​

Long-Task Heartbeat (Edit-in-Place)

​

How It Works

1. A parallel background monitor tracks the time since the last activity (message sent, progress update, etc.)
2. After 2 minutes of silence, a heartbeat message is sent to the originating IM channel
3. On subsequent heartbeats, the same message is edited in place with updated elapsed time, step count, and stage — no new messages are created
4. If the channel does not support message editing, only a single message is sent (no spam)
5. Up to 3 heartbeat cycles per task
6. Uses NORMAL priority — the heartbeat arrives silently without triggering a push notification on your phone

​

Example Message

⏳ Working — 3 min (12 steps, data analysis)

⏳ Working — 5 min (18 steps, code generation)

​

Smart Silence Detection

​

Channel-Aware Adaptation

​

Details

​

In-Chat Agent Switching

​

Telegram (/agent command)

1. Send /agent in any chat
2. An InlineKeyboard appears listing all available agents — the currently bound agent shows a checkmark indicator
3. Tap your desired agent — the picker message is replaced with a confirmation text (“Switched to: AgentName”)
4. All subsequent messages in this topic go to the new agent (independent system prompt, model, tools, memory)

​

Quick Switch Commands

• /cc fix this bug — one-shot routing: this message is handled by the Claude agent, but your binding stays unchanged (next message goes to your previous agent)
• /cc (no arguments) — persistent binding: switches your default agent to Claude for all subsequent messages

​

Topic Binding Granularity

​

i18n Support

​

Cross-Device Task Sync

• Single source of truth — task state lives in the server’s Kanban system, not on any single device
• Real-time updates everywhere — SSE events push status changes (completion, failure, progress) to every connected client simultaneously
• Consistent UI — Desktop (Tauri) embeds the same Web UI frontend, so the experience is identical across surfaces
• IM channel integration — BtwTaskNotifier pushes results to IM channels in parallel with the UI updates
• IM Kanban management — use /kanban (or /kb) directly in Telegram, Discord, Slack, etc. to create, list, edit, complete, block, and archive tasks without leaving the chat. Zero LLM cost — commands bypass the Agent pipeline entirely

​

Cross-Platform Handoff

• Web UI — right-click any conversation in the sidebar → “Transfer to…” → a dialog auto-discovers all connected channels with icons and status indicators → select and transfer in one click
• IM command — type /handoff <target_channel> in any IM channel (Telegram, Discord, Slack, etc.)

​

Automatic “Continue in Browser” Button

• Precise routing — The button links to /{chatUUID} using the database Chat UUID (not the IM platform’s peer ID), so it always opens the correct conversation
• Background task notifications — When a /btw background task finishes, the IM notification also includes the button
• Graceful degradation — Channels that don’t support interactive buttons (e.g., WeChat) automatically fall back to a text link; if no public URL is available, the button is silently omitted without blocking the reply
• WebUI filtering — Messages already in the Web UI do not show the button (no redundant self-links)

​

Session Continuity & Context Preservation

​

Undo, Retry & File Revert in IM

​

Channel Self-Healing & Reliability

​

Health Loop

1. Exponential backoff — restart delay grows from 5s to 300s max, preventing resource thrashing
2. Jitter — 25% random variation prevents thundering herd when multiple channels fail simultaneously
3. Full restart — executes stop() (releases all handles) then start() (fresh initialization)
4. Status broadcast — frontend ConnectionBadge updates in real-time via EventEmitter

​

Message Recovery

​

Dead Letter Queue

​

Generic Reconnect Loop

​

Platform-Specific Rate Limiting

1. Maps the error to a RateLimitError with a platform-specific retry_after delay
2. Retries with exponential backoff, respecting the retry_after value
3. Falls back to DLQ if all retries exhaust — text messages are never silently dropped

​

Circuit Breaker & Graceful Degradation

​

What This Means for Users

• Zero-downtime experience — temporary network issues or platform outages resolve themselves
• Messages are recovered after a restart — a message that was being processed when the service crashed or restarted, or that was waiting in a chat’s queue at a normal shutdown, is replayed on the next start (see Message Recovery for what is not covered)
• No account bans — per-channel rate limiting prevents exceeding platform API quotas
• Visible status — channel health is always visible in Settings > Channels via color-coded badges
• No manual restarts — channels heal themselves; you only see the result, not the recovery process
• No sudden blackouts — streaming updates degrade gracefully instead of stopping abruptly

​

GitHub Channel & CI/CD Integration

​

Supported Events

​

Setup

1. Navigate to Settings > Channels > GitHub
2. Enter your Personal Access Token (with repo scope for posting comments)
3. Enter your Webhook Secret (for signature verification)
4. Add the webhook URL (https://your-server/channels/github/webhook) to your GitHub repo settings

​

Security

​

CI/CD Pipeline Integration

curl -X POST https://your-server/api/chats/ \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"message": "Review the latest commit on branch feature/xyz"}'

​

Remote Approval (HITL)

​

How It Works

1. Agent encounters a dangerous tool call
2. A message with approve/deny buttons is sent to your IM channel
3. You approve, reject, or use batch commands
4. Agent resumes or halts based on your decision

​

Approval Methods

​

Interactive Buttons (ActionButton)

1. Resolves the approval in the database (PENDING-only — duplicate clicks are safely ignored)
2. Edits the original message to show the outcome (e.g. “Approved by alice”)
3. Resumes the interrupted agent automatically

​

Security

• Group chat protection: Only the original requester or configured co-approvers can approve
• Idempotency guard: Already-resolved approvals cannot be re-resolved or status-flipped (DB-level PENDING check)
• Timeout guard: Unanswered approvals auto-deny (configurable)
• Persistent allowlist: “Always allow” decisions survive restarts
• Anti-retry: After 3 denials, agent stops retrying

​

Outbound HITL (Draft Review)

​

Configuration

​

How It Works

1. Message arrives on IM channel → Agent generates a reply
2. Reply is intercepted and stored as an ApprovalRecord (not sent)
3. Reviewer sees the draft in WebUI Approval Drawer or IM ActionButton
4. Approve → message is sent to the channel
5. Reject → message is discarded
6. Timeout → configurable auto-send or auto-reject

​

Review Channels

• WebUI Approval Drawer: Shows the original customer message, AI-generated draft, channel/topic info
• IM ActionButtons: Approve/Deny buttons on the approval notification in the channel

​

Use Cases

​

Intelligent Silent Filtering

• Group chats: Agent is mentioned, checks, finds nothing notable → sends no message (zero noise)
• Scheduled tasks: Periodic checks come back normal → auto-silent, only pushes when issues found
• Placeholder cleanup: “Processing…” placeholder messages are silently removed

​

Detection Rules

​

Deep Feishu Integration

​

Supported Capabilities

​

Typical Workflows

1. Feishu WebSocket pushes comment event in real-time
2. Agent reads the comment and its replies, the document title and link, and — for new-style documents (docx) — the full document text
3. Generates reply and auto-posts to comment thread

​

Setup

1. Go to Settings > Channels > Feishu
2. Enter App ID and App Secret
3. Enable WebSocket long connection (no public IP required)
4. Enable Feishu app permissions as needed:
   • drive:drive — Document access
   • docs:document.content:read — Read the full document text (attached to comment Q&A); docx:document:readonly works as a text-only alternative
   • wiki:wiki — Wiki access
   • im:message — Messaging
   • contact:user.id:readonly — User identification

​

Multi-App Concurrent Instances

1. In Settings > Channels > Feishu, click Add App
2. Scan the QR code (or paste App ID/App Secret in the edit dialog)
3. The new instance comes online immediately — both apps now answer messages concurrently

​

WeCom Dual Channels

• XML message encryption/decryption (AES-CBC)
• Callback signature verification (anti-forgery)
• Message deduplication (prevent duplicate processing)

​

Remote Ops & Autonomous Self-Healing Suite

1. High-Entropy Terminal Log Distillation (TerminalLogDistiller): Strips ANSI noise and carriage return animations, pinpoints key diagnostic signatures (HTTP 403, EADDRINUSE, tracebacks), and retains tail context to compress thousands of lines into <50 high-signal lines (>96% token reduction).
2. Troubleshooting Budget & Anti-Oscillation State Machine (TroubleshootingBudgetManager): Provides 5 autonomous retry attempts across domestic mirror failovers, port probing, and dependency remediation. Deduplicates retry strategies using SHA256 hashes to prevent infinite retry loops and broadcasts progress beacons to IM channels. High-risk operations (e.g. rm -rf /) escalate to interactive approval cards immediately.
3. Idempotent Patch Replay Depot: Packages successful deployment recipes into idempotent deploy.sh scripts with [0/N] phase markers, returned as downloadable artifacts for seamless replayability after software upgrades.

​

WeChat Personal Dual Channels

​

Multi-Channel DM Session Enclave & Anti-Poisoning Gate

1. 4-Tuple Physical Session Enclave (routing_enclave_key): Strictly isolates sessions via (tenant_id, channel, peer_id, agent_profile_id), physically preventing conversation cross-talk and data leaks across tenants, channels, senders, and multi-agent personas while seamlessly maintaining backwards-compatible 2-tuple parse_enclave_key resolution;
2. Stranger Privilege Escalation Defense Gate (Anti-Privilege Escalation Gate): Closes the critical vulnerability in OPEN policy where unpaired senders automatically fell back to inheriting default_user_id (sandbox superuser privileges); unpaired senders are strictly assigned isolated guest identities (guest_{channel}_{sender_id}) with zero access to privileged execution tools;
3. Long-Term Memory Anti-Poisoning Fence (Anti-Poisoning Fence): Directly validates authentication state in the inbound persistence pipeline record_inbound; visitor and unpaired messages are strictly stamped with learning_eligible=False, physically blocking prompt injection attempts from polluting long-term memory and vector indices.

​

Unified Cross-Channel Native Approvals

• Non-blocking Async Concurrency: Completely immune to single-file fcntl.flock deadlocks common in CLI-based competitor daemons.
• Adaptive Multi-Modal Card Interfaces:
  • Feishu / DingTalk / Telegram / Slack / Discord: Delivers interactive cards with native ActionButton elements (✅ Approve / ❌ Deny) directly in your chat stream;
  • WeChat / iMessage / SMS: Seamlessly degrades to text command parsing (/approve) and Apple Watch Tapback 👍 emoji gestures.
• Multi-Client Real-Time Sync: Approvals resolved on your phone instantly push updates to WebUI (CronJobCard) and Desktop via SSE/WebSocket without manual page refreshes.

​

Team Identity: A Named Teammate in Every Group Chat

1. Open Settings → Integration → Channel Routing, pick the channel and topic, type a name (e.g. Helper), and choose a scope: Inherit (channel baseline), Shared, or Private (independent, no baseline inheritance);
2. In the group, mention it (@Helper, research this and file it to our topic library) — it answers in thread, remembers the discussion in its own memory compartment, and never sees your DMs;
3. Group turns run on shared credentials that never touch your personal tokens; DMs always stay personal;
4. Freeze the identity anytime (routing falls back to the default agent, memory retained) or check /topic status. Or in chat: /bind agent=my-agent identity=Helper identity_scope=shared.

​

Proactive Follow-up: Receipts and Stall Nudges

1. In the same Channel Routing row, enable Completion receipts (posts a delivery card in the origin thread when long work finishes) and optionally Stall nudge (one @-mention when a thread with open items goes quiet);
2. Every proactive message carries an AI badge and goes through your approval gates first — drafts held for review never auto-post;
3. Mute any thread with /mute; frozen identities never send proactive messages.

​

Channel Quota Diagnostics & Group RBAC Zero-LLM Direct Output

1. Zero-LLM Token Direct Output:
   • When a user sends /quota (or @bot /quota in groups), the router intercepts the request in the Inbound Pipeline and immediately aggregates usage records from local SQLite;
   • Consumes 0 LLM Tokens, eliminates API network latency, and preserves Prompt Cache prefix hit rates;
2. Group RBAC & Bypass White-listing:
   • Decouples sender privileges (Admin, Member, Guest) to prevent Confused Deputy exploits;
   • Read-only diagnostic commands (/status, /quota, /help) are explicitly white-listed, ensuring that even when a member’s daily quota is exhausted, they can still inspect their remaining allocation and countdown without being deadlocked;
3. High-Signal Visual Progress & Dual-Time Display:
   • Renders standard 10-char ASCII progress bars ([████████░░] 80%) for consistent cross-channel rendering;
   • Displays UTC reset time alongside dynamic relative countdown (Resets at: 00:00 UTC (in ~X hours Y minutes));
   • Fully localized across English, Simplified Chinese, Traditional Chinese, and Japanese;
4. Mobile Responsive Management in WebUI:
   • Administrators can review and inline-edit member quotas under Settings → Channels → Pairing, with full mobile flex-wrap responsive adaptation.