typespec authoring agentic search improvements#15841
Conversation
| 4. **Iterate** — if initial results are insufficient, refine the query or fetch additional pages/URLs until the information satisfies the query. Respect the total time budget. | ||
| 5. **Return** — provide the extracted guidance to the caller. | ||
|
|
||
| ## Fallback |
There was a problem hiding this comment.
could we put the fallback part to thttps://github.com/Azure/azure-sdk-tools/blob/main/.github/skills/azure-typespec-author/references/authoring-plan.md?
And let the agentic search instructions focusing on agentic search itself.
There was a problem hiding this comment.
I saw there is a fall back added here: https://github.com/Azure/azure-sdk-tools/pull/15840/changes#diff-ca1df672aae30ef5d37ee71419674b77f4813b1169025e86a4c2b50baf1e3f16R16
could we remove the fallback part in agentic search?
|
|
||
| 1. **Select URLs** — read [reference-document-links.md](reference-document-links.md). Select only the URLs relevant to the user's request and Step 1 result. If unsure, select all. | ||
| 2. **Fetch** — `web_fetch` each selected URL. Extract content as markdown. | ||
| - **Timeout**: Allow at most 30 seconds per URL fetch. If a fetch times out or fails, skip it and continue with the remaining URLs. |
There was a problem hiding this comment.
Just curious on the cases that timeout happen? Because from my previous perf test, web_fetch avg time is 0.55s. And I did not encounter timeout case before.
There was a problem hiding this comment.
I'm fine with holding off on this pr until we have more data/feedback. This came up when I was working on the evals with copilot and it was analyzing how long it took to process a request, however I wouldnt say there's enough data to strongly push to get this into the skill right now.
3 participants
Protect against hanging for network issues or unreachable links