Cairn
NousResearch/hermes-agent

Plugin hook session_id propagation and tool correlation

Cluster 28961 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
11items grouped
Known?
Yes. 11 related items grouped here, 5 issues already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; 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.

These issues and PRs concern missing or incorrect session_id and tool_call_id fields in pre_tool_call plugin hooks across multiple call sites, including nested tool execution. Related feature work covers request-scoped hooks, tool call correlation IDs, and hook-based blocking of tool execution.

Open issues1

  • Issue#51931[Bug]: Nested tool hooks(on_pre_tool_call and on_post_tool_call) can't get session_id

Open PRs2

  • PR#52000fix(execute_code): forward session_id to nested tool calls via RPC
  • PR#82243feat(tools): compose deferred tools in execute_code

3 PRs closed without merging

From the close comments: done elsewhere 2 · superseded by another PR 1

  • #28982 fix: pass session_id and tool_call_id in pre_tool_call hook · done elsewhere → 0d9b713
  • #34622 fix(plugins): propagate session_id to pre_tool_call hook from all 3 callsites · done elsewhere → d682f32, 36308f0
  • #52001 fix(execute_code): preserve session id for nested tools · superseded by another PR → #52000
Closed issues · 5
  • Closed#28961tool_executor pre_tool_call hook calls omit session_id and tool_call_id (v0.14.0)
  • Closed#34618`session_id` not propagated to `get_pre_tool_call_block_message` from its 3 callsites — `pre_tool_call` plugin hooks that scope by session silently no-op
  • Closed#39728fix: pre_tool_call hook missing session_id in three call sites
  • Closed#44582pre_tool_call plugin hook not invoked during agent tool execution
  • Closed#48311pre_tool_call hooks receive an empty session_id (task_id passed instead) — breaks session-scoped hook policy
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.14: 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
agent
Closed issues
5
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/28961.json
cluster/28961.md