Repository navigation
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.
Adds
@magpie-community/opencode-floatboat-auth(folderpackages/floatboat) and itsregistry.jsonentry, so Floatboat shows up in magpie's Discover as a provider.Why this package exists: the upstream plugin
baijiu666//magpie-Floatboatis installed from GitHub — there is no npm package, and its own README documents thatmagpie plugin add xxx.tgzis broken, so it ships a manual folder install. Aregistry.jsonentry has to name an npm package, so the registry had nothing to point at.What it is: the upstream
index.mjsandsrc/vendored byte-for-byte from v0.1.5 (MIT, Copyright (c) 2026 baijiu,LICENSEcarried over), with onlypackage.jsonmetadata and a new README changed. That README says so, and says how to pull an upstream update (copyindex.mjsandsrc/, bump the version).What the plugin does: signs in to a Floatboat account the way the desktop app does (a one-off Chromium profile catches the
aoe://…?code=…deep link,POST /api/desktop/auth/exchange, thenPOST /api/desktop/newapi/keyfor the gatewaysk-key), and forwards chat throughnewapi.aoe.chat. 13 model ids, the account's credit balance as a wallet window, and the two signup bonuses claimed automatically. It injects no system prompt.Checked:
bun scripts/check.mjs floatboat→✓ registry.json,✓ floatboat(OpenCode 1.x and 2.x loading;opencode.mjs/opencode2.mjsfollow the package pattern,opencode2.mjsis the byte-identical shared copy)bun test ./packages/floatboat→ 2 pass (hooks shape and the 13-model table, offline)magpie plugin add github:baijiu666/magpie-Floatboat+magpie plugin login floatboatagainst a real account →floatboat (Floatboat, 13 models) signed in,GET /v1/modelslists the 13floatboat/*idsNot upstream-compatible on purpose: this is a vendor copy, not a fork; bug reports about the plugin's behaviour belong upstream.
There is also #1460, a skill for the same provider. The two are independent — say if you'd rather have only one of them.