Repository navigation
List magpie-aws-quick-bridge (Amazon Quick, with a local API for CC Switch) in the registry - #1458
Open
DaBinBinah wants to merge 1 commit into
Open
DaBinBinah wants to merge 1 commit into
DaBinBinah wants to merge 1 commit into
Conversation
Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.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.
Adds
magpie-aws-quick-bridge(npm, maintained by me at https://github.com/DaBinBinah/magpie-AWS-Quick-bridge, GPL-3.0) as a provider entry foraws-quick.The channel. Amazon Quick isn't in
registry.jsonyet, but two open pull requests propose it: #1455 (magpie-aws-quick) and #1452 (packages/aws-quick). So I'm saying how this one differs, as the README asks for a channel that already has an entry. The difference is also in the summary here and at the top of the package's README.What it signs in to. Your own Amazon Quick (QuickWork) account. Unofficial: it speaks the desktop app's chat protocol, not a public AWS API.
How it signs in. Browser OAuth (OIDC + PKCE with a localhost callback), for personal accounts and for IAM Identity Center. On a remote machine you paste the callback link instead. The refresh token is kept by magpie and renewed through
auth.refresh.What it supports. The account's own modes as models (fast / balanced / smart / auto, and advanced where the account has it), streaming,
reasoning_content, OpenAI-style tool calls, server-side thread reuse, quota throughauth.usage, and the 64 KB frame limit: tool definitions are compacted first, and what still doesn't fit (long prompts, long tool results, images) is uploaded as an attachment.How it differs from the other two. Inside magpie the three do much the same. The difference is outside magpie. Both of the others carry a standalone OpenAI-compatible (Chat Completions) proxy,
bin/serve.mjs. This package's local API is made for agents that aren't behind magpie's gateway:npx magpie-aws-quick-bridge loginsigns in for it in the browser, and it renews the token itself;npx magpie-aws-quick-bridge ccswitchmakes CC Switch import links for Claude Code, Codex and OpenCode, each with the API format that app speaks.It listens on
127.0.0.1only and every request needs its key.What it doesn't do. It doesn't read the desktop app's saved sign-in (both of the other two do); sign-in is always in the browser. No Gemini CLI.
How far it's tested.
bun test) on Bun 1.3.11 and 1.4.5; 0.3.0 installs from npm and loads in a sandboxed magpie.Checked with
bun scripts/registry.mjs(no problems). The package ships the OpenCode 2.x entry (opencode2.mjs) unchanged.