Hermes Agent processes parameter loss after handling the link, first checking the desensitization rule. v0.15.1 fixed a practical issue: some web link parameters looked like credentials, but the Redaction rule would delete them, resulting in originally accessible links becoming 401, 403, or directly redirecting to the wrong page.
Which links are most prone to problems?
Login callbacks, temporary downloads, sharing links, payment rebounds, and OAuth authorization links may all depend on parameters. If a code, state, signature, token, or key is missing, the link may become invalid. Don't just check if the domain name is correct; you must compare the full parameters.
Troubleshooting methods
- Compare the original link with the Hermes output link.
- If the parameters decrease, upgrade to v0.15.1 first and then retest.
- During testing, use low-permission, short-term links to prevent real credentials from entering the logs.
- If the parameter still fails after upgrading, check browser plugins, short link services, or reverse proxies.
The goal of the anonymization rule is to protect sensitive information but not to damage legitimate web links. When encountering these issues, first check the version and Redaction, which is more effective than repeatedly switching browsers.
Safety advice
Don't leave long-term valid key links to automated tasks. When you need to open the Hermes Agent, it's best to use a one-time link or a low-privilege token, and let the link expire after the task ends. This way, parameters can be preserved while reducing the risk of leaks.
