Accept a full chat-completions URL as the base URL - #4
Merged
Merged
Conversation
Configuring Fireworks with the URL from its docs produced a 404: Path not found: /v1/chat/completions/chat/completions Providers document the full endpoint, so that is what gets pasted into a setting labelled "API base URL", and the code appended the path a second time. Accept either spelling, say so in the label, and give the skill a worked Fireworks example. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Configuring Fireworks with the URL from its docs produced a 404 and no briefs:
Providers document the full endpoint — Fireworks publishes
https://api.fireworks.ai/inference/v1/chat/completions— so that is what gets pasted into a setting labelled "API base URL", andchatCompletionsUrlappended the path a second time.Now either spelling works: the API root, the full endpoint, with or without a trailing slash. The setting label says so, and the skill gains a worked Fireworks example (base URL, model id, key).
Tests cover both Fireworks spellings plus the trailing-slash variants. 77 passing.
The live instance is already generating briefs — it needed only the setting corrected to the root form, which is why this is a robustness fix rather than the thing unblocking it.
🤖 Generated with Claude Code