hermes - 💡(How to fix) Fix [Bug] Hindsight plugin warns wrong port (8080/8081) while service runs on 8888

Bug Description

When the Hindsight memory plugin is configured with a local service running on port 8888, Hermes emits a misleading warning message during hindsight_retain() calls:

⚠️ 注意: hindsight_retain() 函数本次未检测到可用实现（Hindsight 服务 localhost:8080/8081 无法连接）。建议检查 helicone 或 hindsight-python 包是否正确加载，或确认 Hindsight 服务地址。当前 session 发现已存入 memory（若后续 memory 工具可用）。

The actual Hindsight service is running correctly on 8888, and hindsight_retain() actually succeeds (data IS stored), but the warning message:

• Reports the wrong port (8080/8081 instead of 8888)
• Suggests checking helicone or hindsight-python packages which are unrelated
• Creates false alarm that misleads users into thinking the service is down

Root Cause

The warning is generated by Hermes's Hindsight plugin availability detection logic, which probes fallback ports 8080 and 8081 instead of the correctly configured port 8888.

In plugins/memory/hindsight/__init__.py, the _DEFAULT_LOCAL_URL constant is correctly set to http://localhost:8888, and the HindsightProvider._api_url is properly initialized from config/env. However, the availability detection logic appears to use hardcoded fallback ports (8080/8081) that do not match the actual configured port.

Key evidence:

• curl http://127.0.0.1:8888/health → {"status":"healthy","database":"connected"}
• hindsight-client 0.6.0 installed
• hindsight_retain() actually succeeds (data stored)
• Warning incorrectly cites ports 8080/8081

Expected Behavior

The warning message should:

1. Report the actual configured port (8888) instead of the wrong fallback ports (8080/8081)
2. Not mention helicone which is irrelevant to Hindsight
3. Accurately reflect the actual service connectivity status

Environment

• Hermes Agent ( NousResearch/Hermes-Agent )
• Hindsight service: local mode on http://127.0.0.1:8888
• hindsight-client: 0.6.0
• Config: ~/.hermes/hindsight/config.json with mode: local_external, api_url: http://127.0.0.1:8888

Suggested Fix

The Hindsight plugin's availability check should use the configured api_url from config.json / HINDSIGHT_API_URL env var when generating warning messages, not hardcoded fallback ports. The probe logic should also prefer the actual configured URL over generic defaults when reporting connectivity issues.