Lansenger Channel

The Lansenger channel lets you talk to LanMate through a Lansenger DM or group chat, so you can direct it remotely even when you’re away from the computer.

One-Tap Connect

When you’re signed in with Lansenger SSO, the channel page offers “Connect Lansenger in one tap”:

1. LanMate uses your login state to create a personal bot “LanMateBot” automatically
2. The avatar is the blueberry icon and the description is this computer’s name (so multiple devices are easy to tell apart)
3. The connection is established automatically once creation finishes

The bot card supports editing (rename / change description / change avatar) and disconnecting (delete the remote bot + clear local configuration).

Note: disconnecting clears all Lansenger channel conversation records, message logs, the outbox, the corresponding kernel .jsonl, and the default channel workspace (a custom cwd is kept), so a new bot doesn’t inherit the old records.

Manual Configuration

When you aren’t signed in, you can also fill in the app credentials manually.

Multi-Platform Channels

Beyond Lansenger, LanMate also supports bot integration with other IM platforms such as Feishu, DingTalk, WeCom, WeChat, and QQ. Select the platform in the channel configuration dialog and fill in the credentials as prompted. All platforms share the same hybrid inbox and conversation settings; Lansenger is still the recommended one-tap option.

Hybrid Inbox

The channel page organizes by inbox:

• Tabs switch platforms (Lansenger/Feishu/DingTalk/WeCom/WeChat/QQ), with an “All” aggregate tab when several are present
• Sessions are sorted by last message time, newest first
• Type filter: All / DM / Group

Sending Messages

In Lansenger:

• DM: message LanMateBot directly
• Group: @LanMateBot to give instructions; group replies depend on the platform-level group policy and that group’s conversation settings

Group Response Rules

Group replies depend on the platform-level group policy (configured on the channel page): “only groups I’ve enabled”, “all groups”, and so on — three tiers. When a whitelist tier is selected, each group must be enabled individually in its conversation settings.

Groups distinguish three identity levels: owner / admin / member. Approvals and context resets can only be decided by owners and admins; regular members get a no-permission notice when they try.

MateBot DM Access

Off by default. Settings → Personal Assistant → DM access, then tick each bound channel. Once ticked, the owner’s DMs go straight into the MateBot session and replies still return to the original DM; group chats are never connected.

If a DM maps to exactly one in-progress item and that item has an assignee, the message goes straight to the assignee without a second relay. See Automation.

Approval Cards

When a channel conversation hits an approval, the card is pushed to Lansenger:

• Approve once / Valid for this chat / Always allow / Deny
• A 660-second timeout counts as deny
• The card updates in place after you click

Conversation Settings

Right-click a channel conversation → Conversation settings:

• Channel behavior: enable this conversation / respond only to @mentions / allowed senders
• Task config: work mode / working directory / custom instructions

Reset Context

Send /reset or pick it from the context menu; the old context is archived and kept, and a fresh session begins.

What You Can Do in Lansenger

The tool surface of the Lansenger channel centers on messages and groups:

• Send messages: text, Markdown, files, images, cards, rich text with images
• Look up conversations: chat list, group list, message history
• Group operations: members and group info
• Message operations: recall, emoji reactions, download media, request location
• Workspace switching: switch between multiple devices and workspaces

Just state the need in a DM or group chat (e.g., “send this file to the department group” or “recall that last message”). Lansenger has no survey, meeting room, video meeting, calendar, or to-do APIs; needs like those go through the local calendar/reminders tools, or through your own internal endpoints.

Channel Commands

Send a message starting with / in a Lansenger chat to trigger a command. Commands marked “owner only” can only be run by the owner; the rest can be run by any identity allowed to drive the bot (owner and admins by default, adjustable with /exec).

Session Control

Conversation Settings

A bare command (no argument) echoes the current value and the numbers you can pick; with an argument it applies the change.

Approval Short Replies

When an operation is awaiting approval, you can reply with text instead of clicking the card buttons:

• /approve or “approve” — approve
• /deny or “deny” — deny