Repository navigation
Releases: YogaSakti/cpa-opencode-enhancer
Release list
v0.6.1
Fix direct OpenCode requests that select IPv6 and receive FreeUsageLimitError despite an otherwise valid request. Native direct connections now use IPv4 through normal DNS, without hardcoded upstream IPs. Explicit HTTP/HTTPS/SOCKS proxies keep their own routing. The measured Go/uTLS profile remains in use.
Remove the additional model router so shared model IDs use CPA's normal provider priority, rotation, and cooldown behavior. Auth, model registration, execution, and lifecycle support remain native plugin capabilities.
Upgrade with Free Model Sync v0.10.1. Free chat credentials need type: opencode-enhancer; see native setup. Unique aliases such as opencode-free/mimo-v2.6-flash select this provider explicitly while other providers retain their shared aliases.
Validated using GitHub release libraries on unchanged CPA 8.0.43: native Chat HTTP 200, OK, one [DONE], billing_source free and cost 0. Free Model Sync catalog, probe, and selection save passed without losing keys or aliases. Unit tests, race tests, and go vet passed. No CPA core patch or relay is required.
Native upstream execution currently supports Chat Completions; Muse's upstream Responses path remains separate. OAuth login, token counting, and arbitrary HTTP requests are not implemented by the native provider.
v0.6.0
Free chat requests can now use the plugin's native Go/uTLS executor instead of CPA's built-in OpenAI-compatible transport. This fixes the matched-request TLS failure observed on the tested Linux host, without a CPA core patch or relay.
Create an auth JSON with type: opencode-enhancer, an OpenCode key, and selected free chat models. See native credential setup. The matching Free Model Sync release can monitor and update this auth file. Existing compatibility entries retain their interceptor behavior and need migration to use the native transport.
Validated on unchanged CPA 8.0.43: real Chat Completions HTTP 200, text OK, and [DONE]; Responses, Claude, Gemini client streams and non-streaming Chat also passed. Unit tests, race tests, and go vet passed.
Native upstream execution currently supports Chat Completions models; Muse requires upstream Responses and remains on the legacy path. OAuth login, token counting, and arbitrary HTTP requests are not implemented by the native provider.
v0.5.7
v0.5.6
v0.5.5
v0.5.4
What's Changed
- fix: declare the tool quartet in the client's protocol by @YogaSakti in #5
Full Changelog: v0.5.3...v0.5.4
Contributors
Assets 4
v0.5.3
What's Changed
- fix: target codex-api-key Muse by model; drop dead base_url matching by @YogaSakti in #3
- fix: stop auto-fingerprinting Go Muse; document endpoints from source by @YogaSakti in #4
Full Changelog: v0.5.2...v0.5.3
Contributors
Assets 4
v0.5.2
What's Changed
- feat: strip Codex additional_tools on the Responses free tier by @YogaSakti in #2
Full Changelog: v0.5.1...v0.5.2
Contributors
Assets 4
v0.5.1
What's Changed
- feat: support OpenCode Go Muse fingerprinting by @YogaSakti in #1
New Contributors
- @YogaSakti made their first contribution in #1
Full Changelog: v0.5.0...v0.5.1