Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Bug]: honcho_profile tool returns "No profile facts" on self-hosted Honcho v3.0.7+ [1 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

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Fix Action

Fixed

Code Example

Report       https://paste.rs/hE87V
agent.log    https://paste.rs/OD14E
gateway.log  https://paste.rs/mrjvg

---
RAW_BUFFERClick to expand / collapse

Bug Description

The honcho_profile tool incorrectly returns "No profile facts available yet" for peer cards on self-hosted Honcho v3.0.7+, despite peer cards being fully functional via the v3 API. The tool appears to have a hardcoded check that assumes self-hosted instances are always <v3.x.

Environment:

  • Honcho (self-hosted): 3.0.7
  • Hermes Agent: Latest (updated 2025-05-23)
  • Installation: ~/.hermes/plugins/honcho

Configuration: Peer name set properly in ~/.hermes/honcho.json

Steps to Reproduce

  1. Create peer card via API (successful): curl -X PUT "https://localhonchoinstance/v3/workspaces/hermes/peers/tezgno/card"
    -H "Content-Type: application/json"
    -d '{"peer_card": ["Name: Tezgno...", ...]}' ✅ Returns peer card successfully

  2. Verify via API: curl "https://localhonchoinstance/v3/workspaces/hermes/peers/tezgno/card" ✅ Returns full peer card with 7 facts

  3. Attempt via Hermes tool: honcho_profile(peer="user") ❌ Returns "No profile facts available yet"

Expected Behavior

Should return the peer card data stored in the database.

Actual Behavior

Returns outdated hint: "self-hosted Honcho < 3.x does not support peer cards at all"

Affected Component

Agent Core (conversation loop, context compression, memory)

Messaging Platform (if gateway-related)

Telegram

Debug Report

Report       https://paste.rs/hE87V
agent.log    https://paste.rs/OD14E
gateway.log  https://paste.rs/mrjvg

Operating System

macOS 26.5

Python Version

3.11.15

Hermes Version

v0.14.0 (2026.5.16)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

The hint message reveals a hardcoded version check that blocks peer card reads on self-hosted instances, incorrectly assuming all self-hosted deployments are <v3.x.

Proposed Fix (optional)

  1. Remove the hardcoded "self-hosted = no peer cards" check
  2. Add version detection for v3.x+ self-hosted instances
  3. Allow tool to attempt v3 API calls and fail gracefully
  4. Update hint message to reflect current capabilities

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

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…

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 [Bug]: honcho_profile tool returns "No profile facts" on self-hosted Honcho v3.0.7+ [1 pull requests]