What are you trying to do?
Written by a person. Last read by a person on 2026-09-05, 3 days ago. Its facts were checked by the eval suite on 2026-09-07.
You know what you are trying to do but not what it is called here, and you would rather describe the problem than guess at a heading.
Written in the words you would use, not the words the documentation uses.
That distinction is the whole point of this page. A table of contents lists topics, which helps if you already know the name of the thing you need. The reader who most needs an index is the one who does not have that word yet — they have a symptom, or a goal, and no idea what it is called here.
Every line below is phrased the way someone says it out loud.
- My requests work, then randomly stop working, then work again
- It keeps retrying and never succeeds, and I do not know why
- My response stops halfway through
- I got a 200 but there is nothing in the response
- I want to show output as it arrives instead of making people wait
- It works on my machine and fails in CI
- I am moving from another AI provider and want to know what will bite me
- I changed a file and I do not know how to get it to the others
- I think I have lost my work
- I want to undo something but I am scared of making it worse
- Someone told me to make a pull request and I do not know what that means
- How do I know any of this documentation is still true?
If none of these is you
Bring us your situation — it starts from where you got to rather than from what you were trying to do, which is the better entry point when something has already gone wrong.
That is worth telling us, and it is more useful than it sounds: a symptom nobody wrote down is a gap in this index, and the index is revised from exactly that evidence.
How this list gets better
Each entry records why it maps where it does. That reasoning is not decoration — it is what makes a wrong mapping revisable rather than replaceable, and it means a revision can name what the original claim was and why it turned out to be wrong.
When readers routed to a destination leave immediately, the mapping is a candidate for revision, and revisions are logged in public. The routing is expected to improve before the documentation grows, because a larger corpus with the same routing is just a bigger place to be lost in.