feishu-setup-troubleshooting
Set up and troubleshoot Feishu or Lark messaging integration with Hermes Agent, including connection checks, access control, and common failure modes.
- License 许可
- MIT
- 最近更新
- 2026-06-10
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- feishu-setup-troubleshooting
- tags
- [ "feishu", "lark", "messaging", "troubleshooting", "setup", "integration" ]
- version
- 1.2.2
- requires
- { "env": [ "FEISHU_APP_ID", "FEISHU_APP_SECRET", "FEISHU_DOMAIN", "FEISHU_CONNECTION_MODE", "FEISHU_GROUP_POLICY", "FEISHU_ALLOW_ALL_USERS", "GATEWAY_ALLOW_ALL_USERS", "FEISHU_ALLOWED_USERS", "FEISHU_ENCRYPT_KEY", "FEISHU_VERIFICATION_TOKEN" ], "bins": [ "hermes" ] }
- primaryEnv
- FEISHU_APP_SECRET
- description
- Set up and troubleshoot Feishu or Lark messaging integration with Hermes Agent, including connection checks, access control, and common failure modes.
03 SKILL.md 正文
Feishu or Lark Setup and Troubleshooting
When to use
- A user wants to connect Hermes Agent to Feishu or Lark.
- The bot is online but does not reply to messages.
- You need to diagnose permissions, gateway state, or connection issues.
Prerequisites
- Hermes Agent is installed and the
hermesCLI is available. - A Feishu or Lark app exists with bot capability enabled.
- The required App ID and App Secret are available.
Access-control reminder
Feishu access has two separate layers:
FEISHU_ALLOW_ALL_USERSGATEWAY_ALLOW_ALL_USERS
If the gateway layer is still closed, Feishu users will be rejected even when the Feishu layer looks open.
Setup and troubleshooting flow
- Confirm configuration. Check that the required Feishu or Lark variables are present and that the domain and connection mode match the deployment.
- Confirm the gateway is running.
hermes gateway status
- Review recent logs.
hermes logs 2>&1 | grep -i feishu | tail -20
- Test message delivery. Send a direct message and look for an inbound message log followed by a model response.
- Restart after config changes.
hermes gateway restart
Common issues
- Bot does not reply at all: the gateway is not running.
Unauthorized userin logs: the gateway-level allow rule is still blocking access.- Wrong region or domain:
FEISHU_DOMAINdoes not match the deployment. - Messages arrive but there is no answer: the model provider or API key behind Hermes is failing.
Security notes
- Prefer an allowlist for production.
- Never commit App Secret, encrypt keys, or verification tokens.
- Keep the gateway running under a limited user account.
- Review logs for sensitive output before sharing them externally.
04 同仓库更多 Skills
youtube-content
YouTube transcripts to summaries, threads, blogs.
xurl
X/Twitter via xurl CLI: post, search, DM, media, v2 API.
touchdesigner-mcp
Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.
test-driven-development
TDD: enforce RED-GREEN-REFACTOR, tests before code.
teams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.