@maincode-ai/matilda-code 0.21.12 → 0.21.13-nightly.20261026.e0eae1d8c

package/locales/ru.js

@@ -862,7 +862,6 @@ export default {
     'Использование: /language ui [{{options}}]',
   'Usage: /language output <language>':
     'Использование: /language output <language>',
-  'Example: /language output 中文': 'Пример: /language output 中文',
   'Example: /language output English': 'Пример: /language output English',
   'Example: /language output 日本語': 'Пример: /language output 日本語',
   'UI language changed to {{lang}}': 'Язык интерфейса изменен на {{lang}}',
@@ -1110,8 +1109,6 @@ export default {
   '\n⚠ Matilda OAuth free tier was discontinued on 2026-04-15. Please select another option.\n':
     '\n⚠ Бесплатный уровень Matilda OAuth прекращён 2026-04-15. Выберите другую опцию.\n',
   'Bring your own API key': 'Используйте свой API Key',
-  'Browser-based authentication with third-party providers (e.g. OpenRouter, ModelScope)':
-    'Браузерная аутентификация с использованием сторонних провайдеров (например, OpenRouter, ModelScope)',
   'Authentication is enforced to be {{enforcedType}}, but you are currently using {{currentType}}.':
     'Авторизация должна быть {{enforcedType}}, но вы сейчас используете {{currentType}}.',
   'Matilda OAuth Authentication': 'Авторизация Matilda OAuth',
@@ -1132,16 +1129,8 @@ export default {
     'Ожидание авторизации... (Нажмите Esc или Ctrl+C для отмены)',
   'Missing API key for OpenAI-compatible auth. Set settings.security.auth.apiKey, or set the {{envKeyHint}} environment variable.':
     'Отсутствует API Key для аутентификации, совместимой с OpenAI. Укажите settings.security.auth.apiKey или переменную окружения {{envKeyHint}}.',
-  '{{envKeyHint}} environment variable not found. Please set it in your .env file or environment variables.':
-    'Переменная окружения {{envKeyHint}} не найдена. Укажите её в файле .env или среди системных переменных.',
-  '{{envKeyHint}} environment variable not found (or set settings.security.auth.apiKey). Please set it in your .env file or environment variables.':
-    'Переменная окружения {{envKeyHint}} не найдена (или установите settings.security.auth.apiKey). Укажите её в файле .env или среди системных переменных.',
   'Missing API key for OpenAI-compatible auth. Set the {{envKeyHint}} environment variable.':
     'Отсутствует API Key для аутентификации, совместимой с OpenAI. Установите переменную окружения {{envKeyHint}}.',
-  'Anthropic provider missing required baseUrl in modelProviders[].baseUrl.':
-    'У провайдера Anthropic отсутствует обязательный baseUrl в modelProviders[].baseUrl.',
-  'ANTHROPIC_BASE_URL environment variable not found.':
-    'Переменная окружения ANTHROPIC_BASE_URL не найдена.',
   'Invalid auth method selected.': 'Выбран недопустимый метод авторизации.',
   'Failed to authenticate. Message: {{message}}':
     'Не удалось авторизоваться. Сообщение: {{message}}',
@@ -1650,7 +1639,7 @@ export default {
     'Инструкции по настройке см. в документации',
 
   // ============================================================================
-  // Coding Plan Authentication
+  // API Key Authentication
   // ============================================================================
   'API key cannot be empty.': 'API Key не может быть пустым.',
 
@@ -1662,13 +1651,6 @@ export default {
     'Выберите в зависимости от места регистрации вашего аккаунта',
 
   // ============================================================================
-  // Coding Plan International Updates
-  // ============================================================================
-  'New model configurations are available for {{region}}. Update now?':
-    'Доступны новые конфигурации моделей для {{region}}. Обновить сейчас?',
-  '{{region}} configuration updated successfully. Model switched to "{{model}}".':
-    'Конфигурация {{region}} успешно обновлена. Модель переключена на "{{model}}".',
-  // ============================================================================
   // Context Usage Component
   // ============================================================================
   'Context Usage': 'Использование контекста',
@@ -1752,10 +1734,6 @@ export default {
   Parameters: 'Параметры',
   'No tool selected': 'Инструмент не выбран',
   Server: 'Сервер',
-  '{{region}} configuration updated successfully.':
-    'Конфигурация {{region}} успешно обновлена.',
-  'Authenticated successfully with {{region}}. API key and model configs saved to settings.json.':
-    'Успешная аутентификация с {{region}}. API Key и конфигурации моделей сохранены в settings.json.',
   'Type something...': 'Введите что-то...',
   Submit: 'Отправить',
   'Submit answers': 'Отправить ответы',
@@ -1794,14 +1772,11 @@ export default {
   '  Type: Free tier (discontinued 2026-04-15)':
     '  Тип: Бесплатный уровень (прекращено 2026-04-15)',
   '  Limit: No longer available': '  Лимит: Больше не доступен',
-  '  Region: {{region}}': '  Регион: {{region}}',
   '  Current Model: {{model}}': '  Текущая модель: {{model}}',
   '  Config Version: {{version}}': '  Версия конфигурации: {{version}}',
   '  Status: API key configured\n': '  Статус: API Key настроен\n',
   '  Issue: API key not found in environment or settings\n':
     '  Проблема: API Key не найден в окружении или настройках\n',
-  '  Run `matilda auth coding-plan` to re-configure.\n':
-    '  Выполните `matilda auth coding-plan` для повторной настройки.\n',
   '✓ Authentication Method: {{type}}': '✓ Метод аутентификации: {{type}}',
   '  Status: Configured\n': '  Статус: Настроено\n',
   'Failed to check authentication status: {{error}}':
@@ -1956,8 +1931,6 @@ export default {
   // === Same-as-English optimization ===
   ' (not in model registry)': ' (не в реестре моделей)',
   'start server': 'запустить сервер',
-  '中国 (China)': 'Китай',
-  '中国 (China) - 阿里云百炼': 'Китай - 阿里云百炼',
 
   // Stats Dashboard — Category 2
   'Activity Heatmap': 'Карта активности',

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maincode-ai/matilda-code",
-  "version": "0.21.12",
+  "version": "0.21.13-nightly.20261026.e0eae1d8c",
   "description": "",
   "type": "module",
   "main": "cli.js",
@@ -26,7 +26,7 @@
     "bundled"
   ],
   "config": {
-    "sandboxImageUri": "ghcr.io/maincode/matilda-code:0.21.12"
+    "sandboxImageUri": "ghcr.io/maincode/matilda-code:0.21.13-nightly.20261026.e0eae1d8c"
   },
   "dependencies": {},
   "optionalDependencies": {

package/sandbox-macos-permissive-closed.sb

@@ -13,7 +13,6 @@
     (subpath (param "RUNTIME_DIR"))
     (subpath (string-append (param "HOME_DIR") "/.npm"))
     (subpath (string-append (param "HOME_DIR") "/.cache"))
-    (subpath (string-append (param "HOME_DIR") "/.gitconfig"))
     ;; Allow writes to included directories from --include-directories
     (subpath (param "INCLUDE_DIR_0"))
     (subpath (param "INCLUDE_DIR_1"))

package/sandbox-macos-permissive-open.sb

@@ -13,7 +13,6 @@
     (subpath (param "RUNTIME_DIR"))
     (subpath (string-append (param "HOME_DIR") "/.npm"))
     (subpath (string-append (param "HOME_DIR") "/.cache"))
-    (subpath (string-append (param "HOME_DIR") "/.gitconfig"))
     ;; Allow writes to included directories from --include-directories
     (subpath (param "INCLUDE_DIR_0"))
     (subpath (param "INCLUDE_DIR_1"))

package/sandbox-macos-permissive-proxied.sb

@@ -13,7 +13,6 @@
     (subpath (param "RUNTIME_DIR"))
     (subpath (string-append (param "HOME_DIR") "/.npm"))
     (subpath (string-append (param "HOME_DIR") "/.cache"))
-    (subpath (string-append (param "HOME_DIR") "/.gitconfig"))
     ;; Allow writes to included directories from --include-directories
     (subpath (param "INCLUDE_DIR_0"))
     (subpath (param "INCLUDE_DIR_1"))

package/sandbox-macos-restrictive-closed.sb

@@ -78,7 +78,6 @@
     (subpath (param "RUNTIME_DIR"))
     (subpath (string-append (param "HOME_DIR") "/.npm"))
     (subpath (string-append (param "HOME_DIR") "/.cache"))
-    (subpath (string-append (param "HOME_DIR") "/.gitconfig"))
     ;; Allow writes to included directories from --include-directories
     (subpath (param "INCLUDE_DIR_0"))
     (subpath (param "INCLUDE_DIR_1"))

package/sandbox-macos-restrictive-open.sb

@@ -78,7 +78,6 @@
     (subpath (param "RUNTIME_DIR"))
     (subpath (string-append (param "HOME_DIR") "/.npm"))
     (subpath (string-append (param "HOME_DIR") "/.cache"))
-    (subpath (string-append (param "HOME_DIR") "/.gitconfig"))
     ;; Allow writes to included directories from --include-directories
     (subpath (param "INCLUDE_DIR_0"))
     (subpath (param "INCLUDE_DIR_1"))

package/sandbox-macos-restrictive-proxied.sb

@@ -78,7 +78,6 @@
     (subpath (param "RUNTIME_DIR"))
     (subpath (string-append (param "HOME_DIR") "/.npm"))
     (subpath (string-append (param "HOME_DIR") "/.cache"))
-    (subpath (string-append (param "HOME_DIR") "/.gitconfig"))
     ;; Allow writes to included directories from --include-directories
     (subpath (param "INCLUDE_DIR_0"))
     (subpath (param "INCLUDE_DIR_1"))

package/bundled/mainy/docs/features/channels/dingtalk.md

@@ -1,134 +0,0 @@
-# DingTalk (Dingtalk)
-
-This guide covers setting up a Matilda Code channel on DingTalk (钉钉).
-
-## Prerequisites
-
-- A DingTalk organization account
-- A DingTalk bot application with AppKey and AppSecret (see below)
-
-## Creating a Bot
-
-1. Go to the [DingTalk Developer Portal](https://open-dev.dingtalk.com)
-2. Create a new application (or use an existing one)
-3. Under the application, enable the **Robot** capability
-4. In Robot settings, enable **Stream Mode** (机器人协议 → Stream 模式)
-5. Note the **AppKey** (Client ID) and **AppSecret** (Client Secret) from the application credentials page
-
-### Stream Mode
-
-DingTalk Stream mode uses an outbound WebSocket connection — no public URL or server is needed. The bot connects to DingTalk's servers, which push messages through the WebSocket. This is the simplest deployment model.
-
-## Configuration
-
-Add the channel to `~/.matilda/settings.json`:
-
-```json
-{
-  "channels": {
-    "my-dingtalk": {
-      "type": "dingtalk",
-      "clientId": "$DINGTALK_CLIENT_ID",
-      "clientSecret": "$DINGTALK_CLIENT_SECRET",
-      "senderPolicy": "open",
-      "sessionScope": "user",
-      "cwd": "/path/to/your/project",
-      "instructions": "You are a concise coding assistant responding via DingTalk.",
-      "groupPolicy": "open",
-      "groups": {
-        "*": { "requireMention": true }
-      }
-    }
-  }
-}
-```
-
-Set the credentials as environment variables:
-
-```bash
-export DINGTALK_CLIENT_ID=<your-app-key>
-export DINGTALK_CLIENT_SECRET=<your-app-secret>
-```
-
-Or define them in the `env` section of `settings.json`:
-
-```json
-{
-  "env": {
-    "DINGTALK_CLIENT_ID": "your-app-key",
-    "DINGTALK_CLIENT_SECRET": "your-app-secret"
-  }
-}
-```
-
-## Running
-
-```bash
-# Start only the DingTalk channel
-matilda channel start my-dingtalk
-
-# Or start all configured channels together
-matilda channel start
-```
-
-Open DingTalk and send a message to the bot. You should see a 👀 emoji reaction appear while the agent processes, followed by the response.
-
-## Group Chats
-
-DingTalk bots work in both DM and group conversations. To enable group support:
-
-1. Set `groupPolicy` to `"allowlist"` or `"open"` in your channel config
-2. Add the bot to a DingTalk group
-3. @mention the bot in the group to trigger a response
-
-By default, the bot requires an @mention in group chats (`requireMention: true`). Set `"requireMention": false` for a specific group to make it respond to all messages. See [Group Chats](./overview#group-chats) for full details.
-
-### Finding a Group's Conversation ID
-
-DingTalk uses `conversationId` to identify groups. You can find it in the channel service logs when someone sends a message in the group — look for the `conversationId` field in the log output.
-
-## Images and Files
-
-You can send photos and documents to the bot, not just text.
-
-**Photos:** Send an image (screenshot, diagram, etc.) and the agent will analyze it using its vision capabilities. This requires a multimodal model — add `"model": "matilda3.5-plus"` (or another vision-capable model) to your channel config. DingTalk supports sending images directly or as part of rich text messages (mixed text + images).
-
-**Files:** Send a PDF, code file, or any document. The bot downloads it from DingTalk's servers and saves it locally so the agent can read it with its file tools. Audio and video files are also supported. This works with any model.
-
-## Key Differences from Telegram
-
-- **Authentication:** AppKey + AppSecret instead of a static bot token. The SDK manages access token refresh automatically.
-- **Connection:** WebSocket stream instead of polling — no public IP or webhook URL needed.
-- **Formatting:** Responses use DingTalk's markdown dialect (a limited subset). Tables are automatically converted to plain text since DingTalk doesn't render them. Long messages are split into chunks at ~3800 characters.
-- **Working indicator:** A 👀 emoji reaction is added to the user's message while processing, then removed when the response is sent.
-- **Media download:** Two-step process — a `downloadCode` from the message is exchanged for a temporary download URL via DingTalk's API.
-- **Groups:** DingTalk uses `isInAtList` for @mention detection instead of parsing message entities.
-
-## Tips
-
-- **Use DingTalk markdown-aware instructions** — DingTalk supports a limited markdown subset (headers, bold, links, code blocks, but not tables). Adding instructions like "Use DingTalk markdown. Avoid tables." helps the agent format responses correctly.
-- **Restrict access** — In an organization context, `senderPolicy: "open"` may be acceptable. For tighter control, use `"allowlist"` or `"pairing"`. See [DM Pairing](./overview#dm-pairing) for details.
-- **Referenced messages** — Quoting (replying to) a user message includes the quoted text as context for the agent. Quoting bot responses is not yet supported.
-
-## Troubleshooting
-
-### Bot doesn't connect
-
-- Verify your AppKey and AppSecret are correct
-- Check that the environment variables are set before running `matilda channel start`
-- Make sure **Stream Mode** is enabled in the bot's settings on the DingTalk Developer Portal
-- Check the terminal output for connection errors
-
-### Bot doesn't respond in groups
-
-- Check that `groupPolicy` is set to `"allowlist"` or `"open"` (default is `"disabled"`)
-- Make sure you @mention the bot in the group message
-- Verify the bot has been added to the group
-
-### "No sessionWebhook in message"
-
-This means DingTalk didn't include a reply endpoint in the message callback. This can happen if the bot's permissions are misconfigured. Check the bot's settings in the Developer Portal.
-
-### "Sorry, something went wrong processing your message"
-
-This usually means the agent encountered an error. Check the terminal output for details.

package/bundled/mainy/docs/features/channels/feishu.md

@@ -1,186 +0,0 @@
-# Feishu (Lark)
-
-This guide covers setting up a Matilda Code channel on Feishu (飞书) / Lark.
-
-## Prerequisites
-
-- A Feishu organization account
-- A Feishu application with App ID and App Secret (see below)
-
-## Creating an Application
-
-1. Go to the [Feishu Open Platform](https://open.feishu.cn)
-2. Create a new application (or use an existing one)
-
-![](https://gw.alicdn.com/imgextra/i4/O1CN01ORb10i1JM0MQfhnsV_!!6000000001013-2-tps-2219-931.png)
-
-3. Under the application, enable the **Bot** capability (添加应用能力 → 机器人)
-
-![](https://gw.alicdn.com/imgextra/i4/O1CN01bClpxu1FZxyH4kNjJ_!!6000000000502-2-tps-2219-931.png)
-
-4. In **Event Subscriptions** (事件与回调), select **Long Connection** (使用长连接接收事件)
-
-![](https://gw.alicdn.com/imgextra/i1/O1CN01uIwzbl1ph8Kwq7hTI_!!6000000005391-2-tps-2219-1166.png)
-
-5. Add the event `im.message.receive_v1` (接收消息)
-
-![](https://gw.alicdn.com/imgextra/i2/O1CN01n7sZmV28s6WX0aDhw_!!6000000007987-2-tps-2219-1090.png)
-
-6. Note the **App ID** (Client ID) and **App Secret** (Client Secret) from the application credentials page
-
-![](https://gw.alicdn.com/imgextra/i2/O1CN01ag1yBh1DxfEUb4xmE_!!6000000000283-2-tps-2219-1166.png)
-
-### Required Permissions
-
-Enable the following permissions under **Permissions & Scopes** (权限管理):
-
-- `im:message` — Read and send messages
-- `im:message:send_as_bot` — Send messages as bot
-- `im:resource` — Access message resources (images, files)
-
-### Publish the Application
-
-After configuring permissions and events, create a version and publish it. The bot won't work until the application is published and approved.
-
-![](https://gw.alicdn.com/imgextra/i1/O1CN01GbNRcj1lVuACnkV6M_!!6000000004825-2-tps-2219-1090.png)
-
-## Configuration
-
-Add the channel to `~/.matilda/settings.json`:
-
-```json
-{
-  "channels": {
-    "my-feishu": {
-      "type": "feishu",
-      "clientId": "<your-app-id>",
-      "clientSecret": "<your-app-secret>",
-      "senderPolicy": "open",
-      "sessionScope": "user",
-      "cwd": "/path/to/your/project",
-      "groupPolicy": "open",
-      "collapsible": true,
-      "groups": {
-        "*": { "requireMention": true }
-      }
-    }
-  }
-}
-```
-
-### Configuration Options
-
-| Option                 | Description                                                         |
-| ---------------------- | ------------------------------------------------------------------- |
-| `clientId`             | Feishu App ID                                                       |
-| `clientSecret`         | Feishu App Secret                                                   |
-| `collapsible`          | Collapse long responses into expandable sections (default: `false`) |
-| `collapsibleThreshold` | Character threshold for collapsing (default: `500`)                 |
-| `webhookPort`          | If set, use HTTP webhook mode instead of WebSocket                  |
-| `verificationToken`    | Verification token for webhook mode                                 |
-| `encryptKey`           | Encrypt key for webhook mode                                        |
-
-## Running
-
-```bash
-# Start only the Feishu channel
-matilda channel start my-feishu
-
-# Or start all configured channels together
-matilda channel start
-```
-
-Open Feishu and send a message to the bot. You should see a streaming interactive card with the response.
-
-## Connection Modes
-
-### WebSocket (Default)
-
-WebSocket mode uses an outbound long connection — no public URL or server is needed. This is the recommended mode for most deployments.
-
-### Webhook
-
-If you need webhook mode (e.g., for shared applications), set `webhookPort` in your config:
-
-```json
-{
-  "channels": {
-    "my-feishu": {
-      "type": "feishu",
-      "webhookPort": 9321,
-      "verificationToken": "<from-feishu-console>",
-      "encryptKey": "<from-feishu-console>"
-    }
-  }
-}
-```
-
-Then set the request URL in Feishu Open Platform to `http://<your-server>:9321`.
-
-## Group Chats
-
-Feishu bots work in both DM and group conversations. To enable group support:
-
-1. Set `groupPolicy` to `"allowlist"` or `"open"` in your channel config
-2. Add the bot to a Feishu group
-3. @mention the bot in the group to trigger a response
-
-By default, the bot requires an @mention in group chats (`requireMention: true`). Set `"requireMention": false` for a specific group to make it respond to all messages.
-
-## Features
-
-### Interactive Card Streaming
-
-Responses are rendered as Feishu interactive cards with real-time streaming updates. The card shows a "generating" indicator while the response is being produced, and a **Stop** button to cancel generation.
-
-### Quote/Reply Context
-
-When you reply to (quote) a message, the quoted content is automatically included as context for the agent. This works for:
-
-- Text and rich-text messages
-- Interactive cards (bot's previous responses)
-
-### Images and Files
-
-You can send photos and documents to the bot:
-
-- **Images:** Analyzed using multimodal vision capabilities
-- **Files:** Downloaded and saved locally for the agent to read
-
-### Concurrent Messages
-
-Multiple users can send messages simultaneously in the same group chat. Each message gets its own independent card and response — they don't interfere with each other.
-
-## Key Differences from DingTalk
-
-- **Response format:** Uses Feishu interactive cards (v2 schema) with native markdown rendering, including tables
-- **Streaming:** Card content is updated in-place with throttled PATCH requests (1.5s interval)
-- **Connection:** WebSocket via `@larksuiteoapi/node-sdk` — same outbound-only model, no public URL needed
-- **Working indicator:** An "OnIt" emoji reaction is added while processing
-- **Quote context:** Supports quoting both text messages and interactive cards
-
-## Troubleshooting
-
-### Bot doesn't connect
-
-- Verify your App ID and App Secret are correct
-- Make sure **Long Connection** is selected in Event Subscriptions
-- Check that the `im.message.receive_v1` event is subscribed
-- Check the terminal output for connection errors
-
-### Bot doesn't respond in groups
-
-- Check that `groupPolicy` is set to `"allowlist"` or `"open"` (default is `"disabled"`)
-- Make sure you @mention the bot in the group message
-- Verify the bot has been added to the group
-
-### Card stays in "generating" state
-
-- This usually indicates the response completed but the final card update failed
-- Check terminal logs for API errors (rate limiting, card size limits)
-- Very long responses with many tables may hit Feishu's card element limits
-
-### Quote doesn't include card content
-
-- The bot reads card content via the `card_msg_content_type=user_card_content` API parameter
-- Ensure the bot has `im:message` permission to read messages

package/bundled/mainy/docs/features/channels/weixin.md

@@ -1,106 +0,0 @@
-# WeChat (Weixin)
-
-This guide covers setting up a Matilda Code channel on WeChat via the official iLink Bot API.
-
-## Prerequisites
-
-- A WeChat account that can scan QR codes (mobile app)
-- Access to the iLink Bot platform (WeChat's official bot API)
-
-## Setup
-
-### 1. Log in via QR code
-
-WeChat uses QR code authentication instead of a static bot token. Run the login command:
-
-```bash
-matilda channel configure-weixin
-```
-
-This will display a QR code URL. Scan it with your WeChat mobile app to authenticate. Your credentials are saved to `~/.matilda/channels/weixin/account.json`.
-
-### 2. Configure the channel
-
-Add the channel to `~/.matilda/settings.json`:
-
-```json
-{
-  "channels": {
-    "my-weixin": {
-      "type": "weixin",
-      "senderPolicy": "pairing",
-      "allowedUsers": [],
-      "sessionScope": "user",
-      "cwd": "/path/to/your/project",
-      "model": "matilda3.5-plus",
-      "instructions": "You are a concise coding assistant responding via WeChat. Keep responses under 500 characters. Use plain text only."
-    }
-  }
-}
-```
-
-Note: WeChat channels do not use a `token` field — credentials come from the QR login step.
-
-### 3. Start the channel
-
-```bash
-# Start only the WeChat channel
-matilda channel start my-weixin
-
-# Or start all configured channels together
-matilda channel start
-```
-
-Open WeChat and send a message to the bot. You should see a typing indicator ("...") while the agent processes, followed by the response.
-
-## Images and Files
-
-You can send photos and documents to the bot, not just text.
-
-**Photos:** Send an image (screenshot, photo, etc.) and the agent will analyze it using its vision capabilities. This requires a multimodal model — add `"model": "matilda3.5-plus"` (or another vision-capable model) to your channel config. A typing indicator shows while the image is being downloaded and processed.
-
-**Files:** Send a PDF, code file, or any document. The bot downloads and decrypts it from WeChat's CDN, saves it locally, and the agent reads it with its file tools. This works with any model.
-
-## Configuration Options
-
-WeChat channels support all the standard channel options (see [Channel Overview](./overview#options)), plus:
-
-| Option    | Description                                                                    |
-| --------- | ------------------------------------------------------------------------------ |
-| `baseUrl` | Override the iLink Bot API base URL (default: `https://ilinkai.weixin.qq.com`) |
-
-## Key Differences from Telegram
-
-- **Authentication:** QR code login instead of a static bot token. Sessions can expire — the channel will pause and log a message if this happens.
-- **Formatting:** WeChat only supports plain text. Markdown in agent responses is automatically stripped.
-- **Typing indicator:** WeChat has a native "..." typing indicator instead of a "Working..." text message.
-- **Groups:** WeChat iLink Bot is DM-only — group chats are not supported.
-- **Media encryption:** Images and files are encrypted on WeChat's CDN with AES-128-ECB. The channel handles decryption transparently.
-
-## Tips
-
-- **Use plain text instructions** — Since WeChat strips all markdown, add instructions like "Use plain text only" to avoid the agent producing formatted responses that look messy.
-- **Keep responses short** — WeChat message bubbles work best with concise text. Adding a character limit to your instructions helps (e.g., "Keep responses under 500 characters").
-- **Session expiry** — If you see "Session expired (errcode -14)" in the logs, your WeChat login has expired. Stop the channel and re-run `matilda channel configure-weixin` to log in again.
-- **Restrict access** — Use `senderPolicy: "pairing"` or `"allowlist"` to control who can talk to the bot. See [DM Pairing](./overview#dm-pairing) for details.
-
-## Troubleshooting
-
-### "WeChat account not configured"
-
-Run `matilda channel configure-weixin` to log in via QR code first.
-
-### "Session expired (errcode -14)"
-
-Your WeChat login session has expired. Stop the channel and run `matilda channel configure-weixin` again.
-
-### Bot doesn't respond
-
-- Check the terminal output for errors
-- Verify the channel is running (`matilda channel start my-weixin`)
-- If using `senderPolicy: "allowlist"`, make sure your WeChat user ID is in `allowedUsers`
-
-### Images not working
-
-- Make sure your channel config has a `model` that supports vision (e.g., `matilda3.5-plus`)
-- Check the terminal for CDN download errors — these may indicate a network issue

package/bundled/mainy/docs/integration-jetbrains.md

@@ -1,81 +0,0 @@
-# JetBrains IDEs
-
-> JetBrains IDEs provide native support for AI coding assistants through the Agent Client Protocol (ACP). This integration allows you to use Matilda Code directly within your JetBrains IDE with real-time code suggestions.
-
-### Features
-
-- **Native agent experience**: Integrated AI assistant panel within your JetBrains IDE
-- **Agent Client Protocol**: Full support for ACP enabling advanced IDE interactions
-- **Symbol management**: #-mention files to add them to the conversation context
-- **Conversation history**: Access to past conversations within the IDE
-
-### Requirements
-
-- JetBrains IDE with ACP support (IntelliJ IDEA, WebStorm, PyCharm, etc.)
-- Matilda Code CLI installed
-
-### Installation
-
-#### Install from ACP Registry (Recommend)
-
-1. Install Matilda Code CLI:
-
-   ```bash
-   npm install -g @maincode-ai/matilda-code
-   ```
-
-2. Open your JetBrains IDE and navigate to AI Chat tool window.
-
-3. Click **Add ACP Agent**, then click **Install**.
-
-   ![Install](https://img.alicdn.com/imgextra/i4/O1CN01qNdPCW1y8AcqxRgCy_!!6000000006533-2-tps-2490-1788.png)
-
-   For users using JetBrains AI Assistant and/or other ACP agents, click **Install From ACP Registry** in Agents List, then install Matilda Code ACP.
-
-   ![Add from Agents List](https://img.alicdn.com/imgextra/i2/O1CN01ZyOugP26BOKzNgZXx_!!6000000007623-2-tps-479-523.png)
-
-4. The Matilda Code agent should now be available in the AI Assistant panel.
-
-   ![Matilda Code in JetBrains AI Chat](https://img.alicdn.com/imgextra/i4/O1CN013kAVE41XVzbIZOxyv_!!6000000002930-2-tps-3188-2170.png)
-
-#### Manual Install (for older version of JetBrains IDEs)
-
-1. Install Matilda Code CLI:
-
-   ```bash
-   npm install -g @maincode-ai/matilda-code
-   ```
-
-2. Open your JetBrains IDE and navigate to AI Chat tool window.
-
-3. Click the 3-dot menu in the upper-right corner and select **Configure ACP Agent** and configure Matilda Code with the following settings:
-
-```json
-{
-  "agent_servers": {
-    "matilda": {
-      "command": "/path/to/matilda",
-      "args": ["--acp"],
-      "env": {}
-    }
-  }
-}
-```
-
-4. The Matilda Code agent should now be available in the AI Assistant panel
-
-![Matilda Code in JetBrains AI Chat](https://img.alicdn.com/imgextra/i3/O1CN01ZxYel21y433Ci6eg0_!!6000000006524-2-tps-2774-1494.png)
-
-## Troubleshooting
-
-### Agent not appearing
-
-- Run `matilda --version` in terminal to verify installation
-- Ensure your JetBrains IDE version supports ACP
-- Restart your JetBrains IDE
-
-### Matilda Code not responding
-
-- Check your internet connection
-- Verify CLI works by running `matilda` in terminal
-- [File an issue on GitHub](https://github.com/MaincodeHQ/matilda-code/issues) if the problem persists