Token导航 LogoToken导航TokenDH.com
研究检索敏感数据clawhub未标认证来源可访问clear审计通过

unified-session统一会议

Agent Skill

unified-session 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

5,459

周安装

223

GitHub Stars

公开资料未说明

下载量

1,766
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:unified-session(统一会议)
来源仓库:https://github.com/1052326311/unified-session
安装命令:
openclaw skills install unified-session
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install unified-session

简介

unified-session 用于跨设备同步 AI 对话状态,适合在 OpenClaw 中实现连续交互体验。

  • 将不同终端(如手机与电脑)的会话合并至统一内存空间。
  • 保持上下文连贯性,支持中途切换设备继续任务。
  • 需启用会话持久化和加密传输以确保数据安全。
  • 建议用户明确告知数据同步范围和隐私保护策略。

SKILL.md

name
unified-session
description
|

Unified Session

One agent. All your devices. Zero context loss.

  Before                              After
┌──────────┐  ┌──────────┐     ┌──────────────────────┐
│ Telegram │  │ Webchat  │     │    agent:main:main    │
│ Session A│  │ Session B│     │                       │
│ "Buy milk│  │ "What was│     │  Telegram ──┐         │
│  tomorrow│  │  I doing?│     │  Webchat ───┤ shared  │
│  ..."    │  │  🤷"     │     │  DingTalk ──┤ context │
└──────────┘  └──────────┘     │  Feishu ────┘         │
     ❌ Context lost            │                       │
                                └──────────────────────┘
                                     ✅ Full continuity

The Problem

You connected multiple channels to OpenClaw. Each one starts a separate conversation. You research something on your laptop via webchat, grab your phone, message from Telegram — and the agent has no idea what you were talking about.

This is the #1 pain point for single-user OpenClaw setups. The default config isolates channels for multi-user safety, but most people just want one personal AI that works everywhere.

The Fix

One config value: dmScope: "main". That's it.

┌─────────────────────────────────────────────────┐
│  session.dmScope: "main"                        │
│                                                 │
│  All DMs from all channels → one session        │
│  Replies auto-route back to source channel      │
│  No manual switching. No context loss.          │
└─────────────────────────────────────────────────┘

Quick Reference

SettingValueEffect
session.dmScope"main"All DMs → one shared session ✅
session.dmScope"per-channel-peer"Each channel isolated ❌ (default)

Who Should Use This

✅ You're the only person talking to your agent ✅ You use 2+ channels (webchat + phone app) ✅ You want one continuous conversation across devices

⚠️ Do NOT use if multiple people DM your bot — context would leak between users

Setup

Step 1: Diagnose

cat ~/.openclaw/openclaw.json | python3 -c "
import json, sys
cfg = json.load(sys.stdin)

session = cfg.get('session', {})
dm_scope = session.get('dmScope', 'NOT SET')
print(f'Global dmScope: {dm_scope}')

channels = cfg.get('channels', {})
for name, ch in channels.items():
    if not ch.get('enabled', True): continue
    ch_dm = ch.get('dmScope', 'inherits global')
    ok = '✅' if (dm_scope == 'main' and ch_dm in ('main', 'inherits global')) else '❌'
    print(f'  {ok} {name}: dmScope={ch_dm}')

if dm_scope == 'main':
    bad = [n for n,c in channels.items() if c.get('enabled',True) and c.get('dmScope') not in (None,'main')]
    if not bad: print('\\
✅ Unified session is already working!')
    else: print(f'\\
❌ Fix these channels: {bad}')
else:
    print(f'\\
❌ Set session.dmScope to \"main\"')
"
openclaw sessions  # should show 1 session per agent

If the diagnosis says ✅, skip to Step 4 (Verify). Otherwise continue.

Step 2: Configure

Edit ~/.openclaw/openclaw.json:

{
  // Add or update this:
  "session": {
    "dmScope": "main",
    "mainKey": "main"
  }
}

For each enabled channel, add "dmScope": "main":

// Only touch channels that exist in YOUR config
"channels": {
  "telegram":           { "dmScope": "main" },
  "discord":            { "dmScope": "main" },
  "dingtalk-connector": { "dmScope": "main", "routing": [{"agent": "main"}] },
  "feishu":             { "dmScope": "main", "routing": [{"agent": "main"}] },
  "whatsapp":           { "dmScope": "main" },
  "signal":             { "dmScope": "main" },
  "slack":              { "dmScope": "main" }
}

Step 3: Restart

openclaw gateway restart

Step 4: Verify

Send a test message from each channel. After each one:

openclaw sessions  # still 1 session? token count growing? ✅

The real test: tell the agent something from Channel A, then ask about it from Channel B. If it remembers — you're done.

Reply Routing

Replies go back to wherever the message came from. Automatic.

You message from Telegram  → reply goes to Telegram
You message from webchat   → reply goes to webchat
You message from DingTalk  → reply goes to DingTalk

For cron/announce: output goes to the channel you last messaged from (lastRoute).

Troubleshooting

ProblemFix
Bot forgets when switching channelsRun diagnostic in Step 1. Likely dmScope not set to "main"
Messages from a channel don't arriveopenclaw gateway restart — connections silently drop
Multiple sessions still showingOld sessions expire naturally. New messages use unified session
Cron output goes to wrong channelSet delivery.channel explicitly in cron config

Channel-Specific Notes

  • DingTalk: Stream SDK connects to dynamic endpoints. Network changes (VPN, Wi-Fi) can break it silently. Gateway restart fixes it.
  • Feishu: Ensure app is published and event subscription includes im.message.receive_v1.
  • Telegram/Discord/WhatsApp: Generally stable. If messages stop, restart gateway.

Reverting

Want isolated sessions back? One change:

{ "session": { "dmScope": "per-channel-peer" } }

Then openclaw gateway restart.

Security

  • This skill does NOT send data anywhere
  • This skill does NOT modify system files outside OpenClaw config
  • This skill does NOT require API keys or credentials
  • All changes are to ~/.openclaw/openclaw.json only
  • Fully reversible

The only security consideration: with dmScope: "main", anyone who can DM your bot shares the same session. Fine for single-user. Switch to per-channel-peer if you add users.

Run openclaw security audit after setup to verify.

Feedback

  • If useful: clawhub star unified-session
  • Stay updated: clawhub update unified-session

🇨🇳 中文说明

统一会话 — 一个 Agent,所有设备,上下文零丢失

在电脑上开始对话,拿起手机继续聊——同一个上下文,同一份记忆,无缝切换。

痛点

你给 OpenClaw 接了钉钉、飞书、Telegram、Discord、网页版……但每个渠道都是独立的对话。你在电脑上让 Agent 查个东西,出门掏出手机用钉钉问进度——它完全不记得你说过什么。

这是单用户 OpenClaw 部署的头号痛点。默认配置为了多用户安全做了渠道隔离,但大多数人只是想要一个随时随地都能用的私人 AI 助手

解决方案

clawhub install unified-session

然后对你的 Agent 说:

"帮我设置统一会话,让所有渠道共享同一个对话"

一个配置项 dmScope: "main",重启一次 Gateway,搞定。

你会得到

  • 多端无缝衔接 — 电脑 ↔ 手机 ↔ 平板,任意 App
  • 共享记忆 — 不管从哪个 App 发消息,Agent 都记得所有上下文
  • 自动回复路由 — 从钉钉发消息 → 回复自动回钉钉;从飞书发 → 回飞书
  • 全渠道支持 — 钉钉、飞书、Telegram、Discord、WhatsApp、Signal、Slack、网页版
  • 一次配置,永久生效
  • 完全可逆 — 随时切回独立会话
  • 零外部依赖 — 不需要 API Key,不需要额外服务,不发送网络请求

适用场景

✅ 你是 Agent 的唯一用户(个人部署) ✅ 你用了 2 个以上渠道(网页版 + 手机 App) ✅ 你想要一个连续的对话跨所有设备

⚠️ 多人使用的机器人不适用 — 如果多人给你的 Agent 发私信,请保持渠道隔离(per-channel-peer),防止上下文泄露。

安全性

  • 不连接外部服务,不需要 API Key,不发送网络请求
  • 只修改 ~/.openclaw/openclaw.json
  • 一个配置项即可完全回退
  • 设置完成后建议运行 openclaw security audit 检查

安装

clawhub install unified-session

详细步骤见上方英文部分的 Setup 章节,Agent 会自动引导你完成全部流程。

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

76.15%
按下载量换算1,345

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills