/trending --clawnch fails: apex domain 307 redirect not followed (fix: use www base like leaderboard)

[ddfp777]

clawmes version

0.1.0

Hermes Agent version

2026.4.x

Wallet mode

None

Chain ID

8453

What happened

Bug

/trending --clawnch (and the clawmes_info trending op) fails, while /leaderboard works.

Cause

trending.py uses _CLAWNCH_API_BASE = "https://clawn.ch" (apex domain). The apex 307-redirects to https://www.clawn.ch, and the HTTP client doesn't follow the redirect, so the request dies.

leaderboard already uses _CLAWNCH_API_BASE = "https://www.clawn.ch" — which is why it works.

Fix (verified)

One line: change trending's API base to match leaderboard's:

_CLAWNCH_API_BASE = "https://www.clawn.ch"

After patching and restarting the gateway, /trending --clawnch returns live data (CLAWNCH at #1, mc ~$718K, correct top-10). Confirmed the www endpoint returns real token data via curl before patching.

Environment

• clawmes 0.18.2 installed via hermes plugins install clawnchdev/clawmes --enable (Jul 3)
• Windows 10/11, Hermes gateway mode
• Found by my Hermes agent running Clawmes as a Raft External Agent (raft.build workspace) — the agent diagnosed and patched this itself during a read-path test session.

Minor issues noticed along the way (can split into separate issues if preferred)

1. Hook signature warning — every gateway message logs: Hook 'transform_terminal_output' callback raised: callback() missing 1 required positional argument: 'text'
2. Slash command collisions — plugin registration skips /help, /cron, /skills, /history, /version, /copy as conflicting with Hermes built-ins. /copy in particular is a documented clawmes feature (copy-trading) that becomes unreachable.

Happy to provide logs or test anything. Read-path testing only, no funds involved — pre-alpha rules respected.

Doctor output

C:\Users\Prati>hermes clawmes doctor
2026-07-03T09:11:32+0700 [INFO] clawmes.plugin: clawmes 0.18.2 registering with Hermes
2026-07-03T09:11:33+0700 [INFO] clawmes.services.rpc: rpc service started; user-configured chains [], on-default chains [1, 10, 137, 8453, 42161]
2026-07-03T09:11:33+0700 [WARNING] clawmes.services.rpc: Using public-node default RPCs for chains [1, 10, 137, 8453, 42161]. These work for casual reads but rate-limit aggressively; set CLAWMES_RPC_<chain_id> (e.g. CLAWMES_RPC_8453) to your own provider URL for any real workload.
2026-07-03T09:11:33+0700 [INFO] clawmes.services.token_decimals: token_decimals service started (13 seed entries)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.token_gate: token gate started (threshold=10000000 $CLAWNCH)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.explorer: explorer service started; chains supported: [1, 10, 137, 8453, 42161]
2026-07-03T09:11:33+0700 [INFO] clawmes.services.coingecko: coingecko service started (auth=free, ttl=30s)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.price: price router started (backend: coingecko)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.bankr: bankr service started (no api key — read-only)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.zerox: 0x service started (auth=free-tier)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.lifi: lifi service started (auth=free-tier)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.bv7x: bv7x service started (auth=public-only)
2026-07-03T09:11:33+0700 [WARNING] clawmes.services.clawnch: clawnch service started UNAUTHENTICATED (no CLAWNCH_API_KEY); reads work but token deploys will be rejected. Register an agent with /register_agent and set CLAWNCH_API_KEY to enable /launch (base=https://www.clawn.ch)
2026-07-03T09:11:33+0700 [WARNING] clawmes.services.opengateway: opengateway service started UNAUTHENTICATED (no OPENGATEWAY_API_KEY); calls will succeed during the gitlawb partnership window but stop working when auth becomes required (default_model=<unset>)
2026-07-03T09:11:33+0700 [WARNING] clawmes.services.venice: venice service started UNAUTHENTICATED (no VENICE_API_KEY); Venice requires a key — chat completions will fail with HTTP 402 until one is set (default_model=<unset>)
2026-07-03T09:11:33+0700 [INFO] clawmes.plans.scheduler: plan scheduler started (stub — no triggers yet)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.dca_scheduler: dca scheduler started — tick cadence driven by registry
2026-07-03T09:11:33+0700 [INFO] clawmes.services.copy_trader: copy trader started — tick cadence driven by registry
2026-07-03T09:11:33+0700 [INFO] clawmes.services.alerts_scheduler: alerts scheduler started — tick cadence driven by registry
2026-07-03T09:11:33+0700 [INFO] clawmes.services.limit_order_scheduler: limit-order scheduler started — tick cadence driven by registry
2026-07-03T09:11:33+0700 [INFO] clawmes.services.sniper_scheduler: sniper scheduler started — tick cadence driven by registry
2026-07-03T09:11:33+0700 [INFO] clawmes.services.wc_notifications: wc notification consumer started
2026-07-03T09:11:33+0700 [INFO] clawmes.plugin: clawmes register() complete
2026-07-03T09:11:33+0700 [INFO] clawmes.services.rpc: rpc service started; user-configured chains [], on-default chains [1, 10, 137, 8453, 42161]
2026-07-03T09:11:33+0700 [WARNING] clawmes.services.rpc: Using public-node default RPCs for chains [1, 10, 137, 8453, 42161]. These work for casual reads but rate-limit aggressively; set CLAWMES_RPC_<chain_id> (e.g. CLAWMES_RPC_8453) to your own provider URL for any real workload.
✓ Plugin loaded                       clawmes 0.18.2
✓ Hermes available                    hermes_cli importable
✓ SOUL.md installed                   C:\Users\Prati\AppData\Local\hermes\SOUL.md
⚠ Wallet connected                    no wallet — run /connect
✓ Node.js available                   for clawmes-wc-bridge / sa-bridge
⚠ Bridges installed                   not yet installed — first plugin start will run npm ci
⚠ RPC endpoints                       0/5 user-configured; chains on public defaults: [1, 10, 137, 8453, 42161]
2026-07-03T09:11:33+0700 [INFO] clawmes.services.sniper_scheduler: sniper scheduler stopped (ticks=0, total_fired=0)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.limit_order_scheduler: limit-order scheduler stopped (ticks=0, total_fired=0)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.alerts_scheduler: alerts scheduler stopped (ticks=0, total_fires=0)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.copy_trader: copy trader stopped (ticks=0, total_runs=0)
2026-07-03T09:11:33+0700 [INFO] clawmes.services.dca_scheduler: dca scheduler stopped (ticks=0, total_runs=0)

Relevant log lines

2026-07-03 07:25:06,887 WARNING hermes_cli.plugins: Plugin 'clawmes' tried to register command '/help' which conflicts with a built-in command. Skipping.
2026-07-03 07:25:06,923 WARNING hermes_cli.plugins: Plugin 'clawmes' tried to register command '/cron' which conflicts with a built-in command. Skipping.
2026-07-03 07:25:06,927 WARNING hermes_cli.plugins: Plugin 'clawmes' tried to register command '/skills' which conflicts with a built-in command. Skipping.
2026-07-03 07:25:06,929 WARNING hermes_cli.plugins: Plugin 'clawmes' tried to register command '/history' which conflicts with a built-in command. Skipping.
2026-07-03 07:25:06,929 WARNING hermes_cli.plugins: Plugin 'clawmes' tried to register command '/version' which conflicts with a built-in command. Skipping.
2026-07-03 07:25:06,931 WARNING hermes_cli.plugins: Plugin 'clawmes' tried to register command '/copy' which conflicts with a built-in command. Skipping.

(also, on every gateway message:)
WARNING hermes_cli.plugins: Hook 'transform_terminal_output' callback callback raised: callback() missing 1 required positional argument: 'text'

The trending failure itself surfaced agent-side as a 307 on the clawnch API call (clawmes_info trending op); leaderboard op on the same service succeeded. Diagnosis + verified one-line fix in the description above.

Confirmations

• I read SECURITY.md and confirmed this is not a security issue
• I redacted any secrets from the logs/doctor output above