A2A tools config path read from wrong layer

NousResearch/hermes-agent · cluster 109011 · gateway

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

A bug where _a2a_tools_available() reads the wrong configuration layer, causing A2A client tools to remain disabled despite the documented gateway.platforms.a2a.enabled setting. The accompanying fixes address reading the nested platform config correctly across all config layers.

Open issues1

  • Issue#109011[Bug]: A2A client tools stay gated off with the documented `gateway.platforms.a2a.enabled` config — `_a2a_tools_available()` reads the wrong config layer

Open PRs2

  • PR#109022fix(a2a): honor documented nested platform config
  • PR#130359fix(a2a): read the inbound platform from every config layer
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
gateway
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.