Skip to content

feat(qoder): sign chat in-process instead of through workers - #276

Merged
caigee-cmd merged 4 commits into
mainfrom
feat/qoder-inprocess
Oct 7, 2026
Merged

caigee-cmd merged 4 commits into
mainfrom
feat/qoder-inprocess

Conversation

@caigee-cmd

Copy link
Copy Markdown
Owner

Summary

  • Qoder chat decrypts the existing CLI user credential and signs requests in the Go process, then calls the regional agent_chat_generation gateway directly.
  • Login, model catalog, and quota still use the per-account Node worker. Chat no longer loads the CLI bundle.
  • Custom Base64 padding uses $, which the gateway decoder requires. OpenAI Chat, Anthropic Messages, and convertible Responses requests share this chat path.

Test plan

  • go test ./...
  • Live CN account: single-turn and multi-turn qwen3.8-flash both return content after the padding fix
  • Reviewer: replay one existing logged-in account through /v1/chat/completions and one multi-turn client session

Qoder chat now decrypts the existing CLI credential and calls the gateway directly, so accounts no longer load the CLI bundle on the request path. Login, catalog, and quota stay on the per-account worker.
A machine id without the official runtime-info identity made the gateway hide the claimable credit campaign. Send the desktop machine headers only when that identity exists.
The overview resources order note shipped with v0.6.17. Leaving the fragment would publish it again.
@caigee-cmd
caigee-cmd merged commit ea5079b into main Oct 7, 2026
6 checks passed
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