Repository navigation
Add a custom endpoint and OpenCode Go key to Review settings, and lower Go traffic - #30
Merged
Merged
Conversation
Review settings can save an OpenCode Go key and one OpenAI-compatible endpoint, and choose the model for Initial Review. A custom endpoint runs on this computer only, its key never reaches the cloud, and redirects are refused so drawings go only to the chosen server. Go now runs 3 sheet reviewers at 60 requests a minute, never resends a usage-limit refusal, and sends one session per 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.
MOKE could only reach a custom server or a new OpenCode Go key through a hand-made credential file, and Go traffic was far above what its owner wanted. "We don't want to violate their traffic policy," but
mainlet one review run 16 sheet reviewers at up to 300 requests a minute. This adds both connections to Review settings and lowers Go's traffic. The work sat uncommitted while #28 landed a competing Go provider, so it was reworked onto #28's design rather than rebased.Lower Go traffic
moke-review/1.0moke/<version>andx-opencode-client: mokeOpenCode publishes no request or concurrency limit, so 3 and 60 are our own ceilings. They do not establish that this use complies with its terms. Per-conversation sessions will likely change Go's prompt-cache share, which has not been re-measured.
In Review settings
Kept from #28: unprefixed Go model ids, so stored reviews still decode. Muse Spark 1.3 Contributor stays the default and Go stays the only chat route once connected, except that a connected custom endpoint also stays on offer. Go reviews can still run in the cloud.
Worth checking in review
docs/deployment.mdsaid renderer RPC excludes keys. Pasting needs this one exception, so the doc now states it: the key crosses once as a redacted value and never comes back.safeStorageand itsv10guard. A session-only launch still starts when the keyring is down, and Remove also clears a key imported through the File menu.Not tried: a review on a real Go key, and the save-and-restart flow on Windows. The key test sends Chat Completions even for models Pi lists as Responses, so if OpenCode does not translate for them, a good key would show a warning though saving still works.
Proof:
bun run check,bun run buildand the full smoke suite pass, 585 of 585. Desktop and packaged-app tests, including the new custom endpoint flow, pass in CI on Linux, Windows and macOS; they could not run locally because this machine has no Xvfb.Council review
Rounds: 3
Round 3 rechecked only the test fix Opus asked for; Sol and Grok had already approved and were not asked again.
Created with Claude Opus 5.5 in T3 Code through OpenCode, with Claude Opus, gpt-6.1-sol and Grok 4.7 reviewing.