Cairn
NousResearch/hermes-agent

LINE image attachment reply token handling

Cluster 123435 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR 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 1 PR.

These items concern a bug in LINE messaging where media attachments and text replies consume the reply token in the wrong order, causing metered push usage. The work involves folding image attachments into the final text's reply call to use the token correctly.

Open issues1

  • Issue#123435[Bug]: LINE turns with a MEDIA attachment always burn a metered push — the final text spends the single-use reply token first

Open PRs1

  • PR#123465fix(line): fold image attachments into the final text's reply call

1 PR closed without merging

From the close comments: other 1

  • #123604 fix(line): ride the reply token with the image attachments (fixes #123435) · other
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/123435.json
cluster/123435.md