ACP file context parsing and attachment fixes
NousResearch/hermes-agent · cluster 21733 · acp
Data as of
2 open items. Fix attempted, not merged.
The short answer
2open issues
0open PRs
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
- 2 issues and 0 PRs. Broad area: open items may be separate problems.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and pull requests concern the ACP protocol's handling of file attachments, embedded context, and line-range references (e.g. @file#L15-21), including cases where referenced file content is silently dropped. Related work also touches on surfacing the active file and selected lines from VS Code as context.
Open issues2
Open PRs0
1 PR closed without merging
From the close comments: duplicate 1
-
#56772 fix(acp): support embedded_context, parse line ranges, fix resource-only prompt has_content check · duplicate →
#16494
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.45: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- acp
- Closed issues
- 0
- Attempts
- 1 PR closed without merging