mirror of
https://github.com/dtzp555-max/ocm.git
synced 2026-07-22 21:45:07 +00:00
64 lines
1.9 KiB
Markdown
64 lines
1.9 KiB
Markdown
# OCM FAQ
|
||
|
||
## Q: Telegram 群里经常显示 typing，但不回消息？
|
||
|
||
Most common cause is **BotFather Group Privacy** being ON.
|
||
|
||
Fix:
|
||
- BotFather → Your bot → Bot Settings → **Group Privacy** → **Turn off**
|
||
|
||
Also check:
|
||
- `openclaw status` (gateway healthy?)
|
||
- provider auth/rate limits (OCM → Auth page, and gateway logs)
|
||
|
||
## Q: 如何获取 Telegram Group ID（Peer ID / -100...）？
|
||
|
||
Typical workflow:
|
||
|
||
```bash
|
||
openclaw gateway logs --follow
|
||
```
|
||
|
||
Send a message in the target group; the gateway logs usually contain the peer id.
|
||
|
||
## Q: 模型下拉列表为什么没有我想要的模型？
|
||
|
||
OCM sources model options from the real CLI output:
|
||
|
||
```bash
|
||
openclaw models list
|
||
```
|
||
|
||
So if it doesn't show up in OCM, make sure it's registered/available in your OpenClaw environment.
|
||
|
||
## Q: Dashboard 里 Gateway HTTP Ping 显示 Unreachable？
|
||
|
||
Common reasons:
|
||
- Gateway not running
|
||
- Gateway binds to a different interface/port than OCM expects
|
||
- Local firewall/proxy interference
|
||
|
||
Try:
|
||
- `openclaw status`
|
||
- `openclaw gateway restart`
|
||
|
||
## Q: OCM 会把我的 token/个人信息上传出去吗？
|
||
|
||
OCM is designed as a **local** dashboard.
|
||
|
||
That said, your local OpenClaw config contains sensitive information. Follow the safety guidance:
|
||
- keep agent Telegram groups private
|
||
- don't share raw screenshots without redaction
|
||
|
||
See: `docs/SECURITY.md`.
|
||
|
||
|
||
## Q: 为什么 OCM 暂时不支持 WhatsApp 的 sub-agent 工作流？
|
||
|
||
WhatsApp 在 bot/group 自动化能力上有较多平台限制（接入方式、权限与路由粒度、稳定性等）。
|
||
|
||
OCM 的 sub-agent 模式依赖清晰的“会话边界 + 路由 + 最小权限”来保证安全和可维护性。
|
||
因此我们目前不把 WhatsApp 作为 sub-agent 的推荐渠道，暂不支持该模式。
|
||
|
||
如果未来支持 WhatsApp，更可能是 **单聊通知/轻量交互** 方向，而不是多 sub-agent 的群聊拓扑。
|