When the Hermes Agent clicks the dangerous command approval button in Feizu/Lark to report 200340, it is usually not that the Hermes itself is broken, but that the interactive card callback configuration is missing on the Feishu side. The official Feishu documentation has written the reason: one less step, the card can be issued, but it will be reported as 200340 at the click of the button.
3 steps that must be completed
- Subscribe to
card.action.triggerin Event Subscriptions . - Open Interactive Card in the App Features > Bot.
- Configure the correct Card Request URL so that the button click takes you back to Hermes.
How to judge if this is the problem
A typical phenomenon is: the card is sent out normally, it looks like it can be used, but when you press Allow Once / Session / Always to report 200340, the task stops in place and does not continue. Both the official documentation and the public issue state that this is not a "card issuance authority" issue, but a "card interaction callback" that has not been opened.
If you are still running Feishu in webhook mode, check if FEISHU_VERIFICATION_TOKEN and FEISHU_ENCRYPT_KEY are consistent with the developer backend. Just because the button can be sent doesn't mean that the callback verification is definitely correct.
In a word: 200340 Don't reinstall Hermes Agent first, go back to the Feishu developer background to complete the 3 steps of the interactive card.
Official open source address: https://github.com/NousResearch/hermes-agent; Official document entry: https://hermes-agent.nousresearch.com/.
