Repository navigation
Add OpenAI, Claude, and DeepSeek API key support - #36
Merged
Merged
Conversation
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.
Summary
Let users bring OpenAI, Claude (Anthropic), and DeepSeek keys for debriefs. Release the CLI as
getownit@0.1.9.Adds hidden key setup, provider environment variables, model reporting, provider-specific error handling, and setup documentation.
claudeandanthropicselect the same provider. Existing key priority and the Nebius default are preserved.Evidence
nebiusandnvidiawere accepted in the CLI and worker provider registries.After: Tests cover saving each new key, environment selection, endpoint/authentication routing, Claude text extraction, and complete mocked question/grade flows for each provider.
npm test: 149 worker tests and 91 CLI tests passed.npm run typecheck,npm run build, andgit diff --checkpassed./modelsbefore triggering the npm release.Merge Danger
Door: two-way
Worker changes can be rolled back. Existing clients and provider defaults remain supported. An npm release requires a subsequent version to correct any published defect.
Blast Radius: providers
New provider requests and CLI key setup. No schema migrations. Merging triggers the existing production Deploy workflow; the
v0.1.9tag triggers npm publishing after deployment verification.