Lord1Egypt 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.