docs: say direct instances can't be pinned reliably - #55
Conversation
Indexed hostnames exist, but they map to a position among healthy instances that changes as instances come and go.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
lloydmak99
left a comment
lloydmak99
left a comment
There was a problem hiding this comment.
Single-line wording refinement in cloud/experimental/direct-completions.mdx that softens "clients can't choose the instance" to "there is no stable way to choose the instance." This better reflects reality — indexed hostnames exist but map to unstable positions among healthy instances — and the sentence stays grammatical and consistent in context. No MDX structure or links changed; nothing here can affect production, data, or state. Looks good to merge.
Checks: reviewed the full changed page and PR diff/context; git diff --check passed and GitHub broken-links/broken-links CI passed. Local mint validate was skipped (mint not installed); negligible risk for a plain-prose one-line edit.
2 participants
The Experimental direct completions page (#54) says clients can't choose the serving instance. That's too strong: indexed hostnames such as
{slug}-i0.completions.near.aido reach specific instances. But the index is a position among the currently healthy instances, so it changes whenever one is added or removed. This PR changes the sentence to say there is no stable way to choose the instance.mint validatepasses.