fix(ui): attached documents don't reach a Hub-installed flagship agent
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- python
- Domain
- ai, backend-api-design
Research direction
Start at the Agent UI relay call site, _dispatch_sidecar_query, and compare its /query request with the constructor inputs used by in-process agents. Resolve whether the host sends attached paths or retrieved context, then test the chosen behavior with the listed PDF question against binary-installed and wheel-installed flagship agents; both answers should match.
Written by the indexing model from the issue text.
Description
Attach a document to a chat session and ask about it, and a Hub-installed flagship agent answers as if the file were not there. The agent never sees it.
The Agent UI relays a sidecar turn over the agent's /query contract, and that request body carries the transcript and the session id but not the session's attached file paths. An in-process agent gets them through its constructor, so the same session behaves differently depending only on whether the agent was installed as a wheel or as a Hub binary.
Pre-existing for any binary install, but #4165 is what makes the path reachable for the flagship, so it will start being hit. Noted in a comment at the relay call site in _dispatch_sidecar_query.
Fixing it needs a decision first: whether the host sends paths the sidecar then indexes itself, or whether indexing stays host-side and the sidecar receives retrieved context. The second keeps the sidecar free of filesystem access it otherwise does not need.
Test plan
- Attach a PDF to a session and ask a question only answerable from it, against a binary-installed flagship
- Same session, same question, against a wheel install — the answers should not differ
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 169
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 518
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from amd/gaia
-
bug p2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
kornia/kornia#5263 · 1 comment ·
Maintainers usually reply within 1 day
-
approved correction metadata
Difficulty 1/5 Under an hour Newbie friendliness 88/100
acl-org/acl-anthology#10133 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
BasedHardware/omi#20084 ·
Maintainers usually reply within 1 day
-
bug needs-acceptance wg/evaluation-quality
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
vllm-project/semantic-router#4424 ·
Maintainers usually reply within 1 day