Skip to content

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
magpie-community:mainfrom
DaBinBinah:add-magpie-aws-quick-bridge
Open

DaBinBinah wants to merge 1 commit into
magpie-community:mainfrom
DaBinBinah:add-magpie-aws-quick-bridge

Conversation

@DaBinBinah

Copy link
Copy Markdown

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 for aws-quick.

The channel. Amazon Quick isn't in registry.json yet, 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 through auth.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:

  • it speaks Anthropic Messages and OpenAI Responses as well as Chat Completions, so Claude Code and Codex can point at it directly;
  • npx magpie-aws-quick-bridge login signs in for it in the browser, and it renews the token itself;
  • npx magpie-aws-quick-bridge ccswitch makes CC Switch import links for Claude Code, Codex and OpenCode, each with the API format that app speaks.

It listens on 127.0.0.1 only 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.

  • With my own personal account against the real service: sign-in, streaming chat, the system prompt, the tool loop, thread reuse, a long tool result as an attachment, quota; and through the local API, Claude Code, Codex and OpenCode reading and writing a file.
  • Against a stand-in for the service only: enterprise sign-in, the advanced mode and image attachments.
  • 65 tests (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.

Co-Authored-By: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant