hermes - 💡(How to fix) Fix Tirith security wrapper warns on legitimate .app domains [2 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Observed locally through check_command_security(...): Tirith can return a warn verdict with a lookalike_tld finding for .app. Legitimate .app domains should not trigger a noisy warning by themselves. Other findings on the same command must still warn/block normally.

Root Cause

Problem

Hermes' Tirith command-security wrapper currently treats legitimate .app domains as suspicious because Tirith reports a lookalike_tld finding like:

Fix Action

Fixed

Code Example

curl https://example.app
RAW_BUFFERClick to expand / collapse

Problem

Hermes' Tirith command-security wrapper currently treats legitimate .app domains as suspicious because Tirith reports a lookalike_tld finding like:

Domain uses '.app' TLD which can be confused with file extensions

This creates noisy warnings for normal commands against real .app services.

Reproduction

Run a command that references a legitimate .app domain, for example:

curl https://example.app

Observed locally through check_command_security(...): Tirith can return a warn verdict with a lookalike_tld finding for .app.

Expected behavior

Legitimate .app domains should not trigger a noisy warning by themselves. Other findings on the same command must still warn/block normally.

Notes

A previous implementation attempt was closed in favor of tracking this as an issue first: https://github.com/NousResearch/hermes-agent/pull/23809

Possible approaches:

  • handle this via local/configurable security policy instead of hardcoding behavior;
  • or apply a narrow allowlist for Tirith lookalike_tld findings where the only finding is .app.

Acceptance criteria

  • .app-only lookalike_tld findings no longer interrupt normal command flow.
  • Mixed findings still preserve the non-.app warning/block behavior.
  • Regression tests cover both .app-only and mixed-finding cases.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

Legitimate .app domains should not trigger a noisy warning by themselves. Other findings on the same command must still warn/block normally.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix Tirith security wrapper warns on legitimate .app domains [2 pull requests]