mirror of
https://github.com/anomalyco/opencode.git
synced 2026-07-22 02:05:26 -04:00
No Branch/Tag Specified
dev
mini-terminal-title
location-wait-api
mini-project-commands
resume-prompt
alibaba-images
item-reference-investigation
ai-pdf-support
beta
v2
production
wsl-shell-env
fork-once
wsl-env-load
stream-eof-finish
nvidia-minimax-thinking
pr-38231-assets
shell-mode-style
pr-38224-assets
reject-malformed-hunks
tool-progress-live
codemode-catalog-diffs
model-flicker
default-background
terminal-queries
event-batching
port-plugins
gemini-thinking-level
patch-symlink-policy
session-version-sentinel
client-service
service-channel-config
webfetch-images
search-integration
billing-details
shell-exit-grace
desktop-image-backgrounds
copilot-endpoint
migrate-select-theme
bound-tool-output
workspace-model-block
remove-promo
collapse-model-providers
review-sidebar-hydration
collapse-questions
location-startup-timing
remove-output-paths
shell-output-preview
quark-timeline
raw-tool-recovery
dialog-hover-fix
server-profiles
server-switcher
kimi-mfjs-schema
session-options-hook
interleaved-fields
remote-workspaces-plan
fix-initial-message
undo-git-guard
pr-37575-assets
opentui-binary-repro
startup-lock-release
system-theme-v2
llm-error-types
tui-plugin-load
external-defaults
productionclear
pr-37513-assets
console-auth-refresh
v2-app-api
backend-adapter-v2
oc-clipboard-and-paste
test/hot-reload-regressions
provider-benchmark
shell-progress-tail
model-cycle-palette
theme-toggle-copy
flaky-provider-tests
permission-modal-keyboard
shell-output-alignment
session-http-hook
permission-highlight
activity-panel
workspace-copy
interrupt-not-found
device-org-select
v2-subagent-limit
vertex-xai-default
reasoning-replay
agent-picker-custom
effect-dynamic-tools
patch-empty-hang
fix/empty-assistant-output
favorites-cli-config
simulated-tools
console-analytics-logger
simulation-terminal-frame-capture
feature-defaults
free-model-logo
service-restart
interrupt-stop-race
xai-oauth
background-indicator-inline
home-shortcut-align
compaction-model-marker
provider-config-shape
interface-toggle
install-layout-eligibility
tools-menu
mcp-location-refresh
session-picker-crash
optimistic-submit
dialog-action-focus
llm-terminal-contract
llm-remove-provider-error
remove-subtle-syntax
title-small-model
dialog-empty-states
permission-panel
api-dsl-cleanup
app-backend-v2
free-model-badge
compaction-percent
thought-toggle
home-session-scroll
llm-error-redesign
luna-oauth-fix
tool-flat-draft
v2-shell-utf8
remove-starptech
effort-values-none
config-dialog
update-tsgo
bounded-compaction-prod
stale-form-submit
dismiss-stale-form
bounded-compaction
agent-picker-variants
config-dir-repro
shell-tail-output
v2-integrations
quick-undo
startup-error-cause
subagent-panel-ui
lazy-fff
optimistic-input
zsh-positional
v2-diff-route
plugin-session-rename
gpt56-max
shortcut-screenshots
service-status
context-overflow
random-tool-catalog
review-nav-spacing
architecture-review
duplicate-event-logs
fix-shell-tab
v2-agent-env
plugin-watch-fix
compaction-cleanup
fix-compaction
genai-observability
agent-permission-order
tui-pending
catalog-repros
catalog-cold-start
console-login-logs
fix/tui-fresh-session-prompt
review-terminal
model-reset-repro
reasoning-variants
improve-caching
team-members
promise-chaining
tabs-launch-screenshots
compaction-steer
agent-env-markers
daemon-election
retry-layout
bash-streaming-fix
bash-tool-crash
restore-session-paging
provider-entrypoints
model-input-defaults
fix-initial-message-page-size
background-return
model-capability-defaults
runner-scenario-dsl
location-watch-guard
fix-shell-count
session-model-sync
new-session-commands
interrupt-tool-hang
codemode-service
mcp-attachments
stdlib-gaps
codemode-object-delete
json-callbacks
code-mode-opencode
drive-manifest
firecrawl-search
persisted-suspense
mcp-resource-app
mcp-resource-ui
mcp-resource-api
media-attachment
instruction-rename
destructuring-assign
codemode-audit
schema-reexports
event-subscribe
nxl/vcs-plugin-api
global-forms
revert-prompt
fix-stale-tools
service-version-guard
partial-refund-ledger
sdk-js-imports
jlongster/simulation-improvements
promise-named-types
tool-output
execute-code-mode-v2
compaction-indicator
subagent-command
catalog-readiness
pending-tool-error
zen-body-limit
form-tui
step-settlement
settlement-ledger
provider-packages
elicitation-timeout
codemode-opencode-adapter
optimize-hooks
models-log-leak
zen-accounting-latency
form-elicitation
codemode-opencode-wiring
codemode-opencode-integration
models-refresh-daemon
v2-model-refresh
filesystem-simulation
context-checkpoint
system-context
subagent-notify
subagent-resume
simulation-spec-v2
directory-attachment-expansion
zen-headers-timeout
config-effect-v2
embedded-config-seam
config-ownership
shell-background-notice
compaction-idle-status
session-tab-remount
publish-server
directory-attachments
content-filter-notice
settings-model-clipping
home-autocomplete-location
tabs-restore
plugin-runtime-bridge
simulation-spec
optimistic-prompt
reasoning-model-api
tool-result-api
beta-badge
prompt-submit-clear
prompt-attachments
mcp-prompts
background-shortcut
debug-windows-opentui-standalone-repro-release
fix-empty-sessions-list
core-node-consumers
model-selection
snapshot-otui
pty-env-route
status-frame-fix
daxbox-servers
shell-output-flush
shell-tool-test
auth-list
remove-default-layers
jlongster/opencode-all-tests-more
native-provider-clean
context-tooltip-v2
native-provider-core
native-provider-stack
deferred-tools
delete-email-action
poll-updates
jlongster/test-batch
session-forking
plugin-patterns
anthropic-thinking-variants
merge-dev-into-v2
fix-windows-abbreviate-home
project-edit-update
streaming-prd
zen-refund-accounting
fish-completion
cache-code-highlights
review-session-pane
sdk-generation-dev-check
clean-desktop-deps
clean-http-recorder-deps
clean-opencode-deps
clean-session-ui-deps
clean-stats-app-deps
clean-ui-deps
clean-web-deps
clean-app-deps
clean-cli-deps
clean-console-app-deps
clean-console-core-deps
clean-console-function-deps
clean-console-mail-deps
clean-console-support-deps
clean-core-deps
clean-root-deps
tui-child-picker
core-project-relocation
complete-client
open-auth-url
desktop-relocated
child-session-picker
fix-event-type
typecheck-28263387070
refresh-singleflight
jlongster/location-nodes
home-active-indicator
session-step-interrupted
interrupt-loading
fix/tui-preserve-renderer-error
fix/provider-session-failures
frank-production-validation-20260626
embedded-live-tail
fix/openai-stateless-reasoning-continuation
session-event-stream
responses-stream-retry
mcp-core-skeleton
server-auto-approve
opentui-retry
timeline-scroll-state
protocol-events
published-events
native-provider-config
native-provider-packages
oc-1.17.10-hotfix
new-session-model
tab-custom-color
feat/tui-render-state-dump
fix/tui-palette-question-mode
otui-native-yoga
feature/expand-paste-summary
todo-dock-motion
mcp-search-tool
tab-shrink
session-provider-errors
isolate-oauth-headers
verify-mcp-auth
secure-oauth-api
mcp-reconnect
restrict-mcp-env
redact-config-secrets
atomic-oauth-callback
native-provider-schema
add-model-comparison-pages
question-paste
simplify-target-layouts
fix-mention-mime
tagged-error-lint
websocket-auth
headless-console-login
mobile-utility-ui
ios-pwa-shell
mobile-bottom-nav
mobile-session-layout
mobile-home-layout
plugin-internal
fix/v2-queue-after-terminal-failure
http-recorder-release
custom-image-defaults
consolidate-todo-event
normalize-step-event-versions
fix-session-subpath
simplify/v2-runner-transitions
run-core-tests
feat/v2-terminal-run-failures-dev
filesystem-errors
hide-read-arguments
layer-node-permit
layer-node-projector
layer-node-repocache
layer-node-sprompt
layer-node-projcopy
layer-node-location
layer-node-movesess
layer-node-locfs
layer-node-models
layer-node-locmut
layer-node-instruct
layer-node-cconfig
layer-node-watcher
layer-node-fmutation
layer-node-integrate
layer-node-cevent
layer-node-cspawn
layer-node-cagent
layer-node-cproject
layer-node-command
yolo-flag
layer-node-extdir
layer-node-cprocess
layer-node-cgit
layer-node-cripgrep
layer-node-csearch
figma-mcp-client
stabilize-ci-tests
core-tests-ci
project-copy-migration
mcp-prompt-refresh
mcp-oauth-refresh
workerd
share-listener-runtime
v2-global-nodes
server-node-graph
mcp-resource-content
fix/command-double-file
background-model-refresh
jlongster/project-copy-config
demo/pr-31617-session-location
feat/tui-copy-session-location
reasoning-options
reasoning-options-support
fix/opencode-bundle-fff
refactor/mcp-connection-results
refactor/reference-directory-parts
feat/mcp-resource-updated
fix/mcp-prompts-list-changed
feat/mcp-resource-list-changed
docs-go-pricing-explanation
refactor/tui-http-sdk
fix/v2-read-validation-failure
refactor/v2-session-run-coordinator
refactor/core-provider-turn
feat/v2-terminal-run-failures
fix/v2-session-wake-retry-dev
feat/core-v2-background-agent
fix/http-recorder-release
fix/v2-session-wake-retry
fix/bash-tool-settlement
fix/v2-headless-permission-policy
fix/v2-binary-detection
fix/v2-read-images
fix/v2-read-errors
feat/core-v2-overflow-recovery
feat/jsonl-log-file
feat/core-v2-session-context-epoch
fix-bedrock-1
fix/session-metadata-migration-repair
pr-30929-demo-video
nexxeln-copy-git-worktree-path
fix/tui-worker-rpc-errors
refactor/core-v2-message-identity
fix/core-v2-sequence-index-invariants
refactor/core-account-file-agents
feat/core-command-registry
fix/tui-rpc-errors
fix/openai-codex-route-timeouts
fix/openai-websocket-header-timeout
refactor/remove-aisdk-option-fields
dustin/improve-memory-usage
feat/sdk-oagen-effect-emitter
nxl/consolidate-project-references
fix/prompt-loop-shutdown
feat/stripe-lake-ingest
kit/tui-scenario-frames
test/core-location-filesystem-canonical-paths
fix/zen-provider-sse-errors
dustin/clickable-titles
fix/free-tier-limit-cta
fix-model-selection
kit/pr-30051-screenshots
fix/xai-provider-upstream-pdf-support
chore/opencode-ai-provider-updates
feat/mcp-add-inline-args
refactor/provider-inline-local-helpers
fix/tui-syntax-builtins
fix/tui-question-keybindings
nxl/session-status-parent-id
feat/core-config-service
fix/free-model-sort
jlongster/workspace-v2
server-discovery
nxl/tui-message-keyboard-nav
fix-github-links-and-star
kit/tui-pending-tool-spinner
fix/task-running-continuation-feedback
fix-leader-none
fix/google-vertex-anthropic-auth-message
worktree-fork-toast
feat/request-aware-provider-fetch
fix/session-project-migration-time
kit/tui-optimistic-prompt-render
issue-13770-tool-output-docs
fix/google-vertex-metadata-warning
brendan/fix-e2e
question-endpoint
test/config-effect-dsl
fix-native-llm-options
compaction-adjustments
fix/app-v2-channel-gate
feat/core-database-schema-sync
fix/mcp-oauth-scope-and-callback-port
dustin/fix-structured-output-fields
kit/repro-zod-schema-leak
worktree-dead-exports
worktree-dead-files
nxl/fix-permission-specificity
jlongster/diff-viewer
nxl/v2-deferred-prompt
fix-retries
nxl/compaction-args
dustin/tool-choice-capability-support
cooper/opencode-codex-refresh-dedupe
refactor/native-runtime-prepared-request
storage-v2-service
drop-app-runtime-instance
worktree-test-port-audit
worktree-cli-effect-harness-2
worktree-cli-prewarm
refactor/session-prompt-parts
image-paths
test/config-instance-opencode-files
fix-env-json-parse-guards
test/config-instance-save-update
extract-part-text-helper
test/config-instance-template-loads
test/config-instance-first-slice
test/config-instance-agent-command
test/provider-instance-custom-models
test/provider-instance-model-lookup
worktree-global-bus-unify
test/provider-instance-first-slice
oc-issue-question-stuck
oc-snapshot-subdir
nxl/fix-auto-compaction-progress
fix/edit-project-dialog
brendan/message-timeline-scroll-virtualiser
jlongster/simulation-rebase
thdxr/auth-well-known-service
models-dev-global-snapshot
tui-markdown-h3-muted
debug-windows-opentui-bun-1.3.14
debug-windows-opentui-crash
serve-socket-mode
fix-event-sync
kit/delete-instance-local-context
upgrade-otui-0212
snapshot-npm-native-binary-install
emdash/27458-h7lu6
session-next-delta-events
new-colors
fix/event-stream-context-capture
fix/event-stream-context-27391
effect/session-transport-service
effect/config-paths-service
adjust-perm-array-logic
nxl/remove-http-notfound-fallback
nxl/render-config-json-diagnostics
nxl/render-tagged-config-errors
effect-test-permission-next
fix/desktop-session-status-tui-20260513090340
opencode/storage-engine-repository
effect/define-service-helper
disable-image-resizing-default
effect/util-process-effect-returning
effect-test-plugin-auth-override
effect/kill-tuiconfig-installation-facades
effect/unwrap-run-runtime-facades
effect-test-project-project
jlongster/fuzz-backend
fix-aws-issue
llm-native-inject-client
llm-native-runtime-openai
llm-native-prepare-tests
llm-native-request-adapter
llm-native-event-adapter
effect-test-provider-cluster1
brendan/lazy-init-plugins
kit/drop-project-sandboxes
claude/learn-new-skill-Ji0dn
fix/windows-instance-fixture-cleanup
worktree-draft+llm-usage-additive
styled-skill-errors
cleanup/effectify-remaining-compaction-tests
draft/session-timeline-rewind
worktree-http-recorder-cassette-seam
claude/review-recent-issues-Ck5UO
opencode/happy-cabin
cleanup/localize-id-prefixes
cleanup/openapi-workspace-path-pattern
llm-service-event-seam
kit/config-field-tolerant
kit/migrate-drift-tests-into-exerciser
kit/httpapi-exercise-via-sdk
kit/mcp-tolerate-bad-output-schemas
refactor-provider-model-status-schema
fix/httpapi-query-schema-drift
kit/fix-26435-legacy-session-model
kit/plugin-mutation-reproducers
kit/fix-workspace-time-used-migration
kit/revert-26550-fallback
kit/restore-hono-temporary
kit/fix-empty-bad-request-normalization
nxl/reference-file-mentions
fix/composer-image-preview-click
kit/httpapi-project-skill-repro
kit/httpapi-total-coverage
kit/httpapi-auth-cleanup-base
jlongster/workspace-external
fix-reasoning-efforts
fix/session-negative-output-tokens
make-review-normal
nxl/fix-anthropic-provider-tools
brendan/desktop-electron-refactor
fix/workspace-warp-typecheck
jlongster/warp
nxl/background-subagents
kit/pty-no-auth-parity
thdxr/v2-message-model-failures
kit/server-listen-native
kit/httpapi-listener-proxy-ws
kit/typed-session-not-found-sketch
fix-wellknown-down
kit/httpapi-not-found-shape
effect-drizzle-sqlite
question-lifecycle-effect-tests
kit/instance-loader-service
kit/effect-workspace-adapters
docs-sdk
kit/llm-approval-instance-ref
kit/session-llm-instance-state
effect-sync-event-service
jlongster/pin-session
azure-cognitive-improvements
adapter-rename
nxl/runtime-aware-search-service
deflake-test
moonshot-mfjs
nxl/small-model-subagents
brendan/new-composer-design
kit/httpapi-sdk-smoke-test
simon-reject-failure
kit/httpapi-json-shape-parity
kit/fix-httpapi-session-list-main
kit/httpapi-route-parity
fix-deepseek-reasoner
kit/httpapi-experimental-tools
deepseek-anthropic
fix/usage-chart-local-time
fix-shell-test
fix-config-ordering-issue
fix/beta-lazy-assistant-error
fix/session-event-typecheck-ci-shell
kit/httpapi-route-inventory-current
shell-test
simon-thread-network-defaults
fix-hover-selected
kit/schema-native-cleanup-ts
adjust-retry-logic
kit/session-schema-events
kit/config-permission-effect
Cramer/2026-03-25/bare-repo-bug
opencode-remote-voice
core
fix-zen-2
kit/multiedit-schema-fix-ts
kit/fix-release-publish-effect
kit/file-instance-context
kit/lsp-effect-refactor
kit/tui-terminal-notifications
tui-favorite-sort-on-query
openai-compaction
fix-copilot
opencode/swift-nebula
fix/project-worktree-external-directory-default
kit/tui-go-upsell-shimmer
kit/httpapi-workspace-schema-migration
kit/ns-plugin-loader-redo
kit/ns-plugin-loader
kit/ns-file-watcher
kit/repro-write-lsp-hang
kit/collapse-session
kit/collapse-patch
kit/retrofit-plugin-main
kit/retrofit-skill-main
kit/retrofit-permission-main
kit/retrofit-mcp-main
kit/retrofit-config-main
kit/unwrap-plugin-siblings
kit/unwrap-small-standalone
kit/unwrap-mcp-siblings
kit/unwrap-config-siblings
kit/self-reexport-migration-tooling
claude/verify-pr-comment-UuyAZ
claude/debug-e2e-tests-Hkgdb
kit/ns-heap
kit/ns-bus-event
kit/ns-standalone
kit/config-httpapi
kit/ns-file-3
kit/ns-session-3
kit/project-httpapi-reads
kit/ns-session
kit/ns-share
kit/ns-project
kit/ns-util-color
kit/ns-lsp
kit/ns-util-local-context
jlongster/sync-fenc
anthropic-fixes
feat/request-route-spans
kit/fs-search
kit/fs-tui-state
example-tui-plugin
cli-perf/tui-config
kit/fs-cli-io
kit/fs-plugin-npm
kit/llm-facade-cleanup
fix/snapshot-gitignored-index
kit/tui-facade-cleanup
kit/config-providers-httpapi-spike
kit/file-httpapi-spike
kit/workspace-httpapi-reads
nxl/mount-question-server
fix/session-prompt-permission-draft
fix-effect-context-bridges
followup-question-reply-inline
kit/fix-session-prompt-logger-interop
kit/question-httpapi-spike
kit/httpapi-route-inventory
kit/facade-session-prompt
jlongster/wip
nxl/fff-search-service
brendan/effect-env
kit/facade-project-20260413
kit/ripgrep-schema-source
kit/shell-job-service
fix/lsp-dead-root-prune
2.0
foo
facade/config
facade/lsp
facade/file
facade/provider
kit/ai-sdk-motel-bridge
oc-run
kit/e2e-seed-runtime-scope
brendan/electron-window-state
go-hero-banner-glm51-promo
snapshot-node-shim-stuff
fix/tui-session-diff-summary
oc-release-0.1.98
fix/snapshot-gitignore-respect
oc-basecode
worktree-agent-ab6ff98a
layered-deferred-comp
oc-startup
feat/tui-logo-radial-pulse
claude/effect-migration-review-Qyu6m
fix-anthropic-transform
kit/effect-sync-event
kit/effect-workspace
kit/eliminate-message-v2-roundtrips
worktree-agent-ab5855c0
kit/motel-session-telemetry
kit/tool-effect-multiedit
task-spec-executor-split
kit/tool-effect-invalid
worktree-feat+otel-bridge
kit/effect-native-tool-interrupt
jlongster/tui-workspaces-ux
kit/permission-flow-ux
nxl/deflake-webfetch-memory-test
npmcli-config
brendan/node-server-types
pr-21017
app/startup-splash
no-diff-virtualization
opencode/shiny-cactus
nxl/fix-diffs-header-sticky
nxl/shell-mode-tray
message-v3
opencode/gentle-pixel
oc-run-pinned
kit/prompt-abort-cleanup
opencode-suggest
rankings
copilot/research-opencode-server-plugin-api
kit/console-org-switcher
kit/ci-unit-reporting
figma-tokens
copilot/fix-spawn-error-windows
kit/dev-memory-observe
kit/remove-e2e-url-repro
effect-sync-event
effect/summary
pr-18308
worktree-audit-effect-services
test/processor-mock-server
fix/session-tool-metadata
opencode/glowing-tiger
claude/variant-popover-number-keys-gc6Bo
kit/format-child-process-spawner
jlongster/flaky-plugin-test
timeline-spacing-cleanup
feat/fff-search-tools
pr-18335
refactor/server-route-organization
jlongster/remove-workspace-server
kit/zen-stream-diagnostics
worktree-agent-a682f34a
spinner-concepts
openai-websocket
brendan-cli-codesign
brendan/cli-codesign
kit/windows-session-restore
opencode/cosmic-mountain
opencode/quick-orchid
perf/tool-memory
input-cleanup
opencode/sunny-comet
log-worktree-error-details
remove-context-tooltip-from-tab
tui-experimental-design
kit/effectify-command-review
brendan/better-session-id-handling
fix/lazy-facades
fix/insufferable-cycle-cyclone
kit/effectify-worktree
kit/effectify-tool-registry
kit/effectify-plugin
kit/effectify-pty
kit/effectify-command
kit/effectify-session-status
feat/auto-accept-permissions
kit/skill-lazy-init
fix-plugin-provider-behavior
fix/stale-running-session-ui
opencode-2-0
opencode/quiet-pixel
enterprise-lead-tracking
fix-e2e
kit/effect-bus
gitlab-version
add-model-reconciliation
jlongster/effectify-event-route
fix/zen-openai-response-usage
refactor/effect-pattern-migration
no-projects-empty-state
nexxeln/readme-small-tweak
test-branch
refactor/delete-scheduler
fix/shell-tab-shell-mode
effectify-skill
rhys/fast-mode-toggle
fix/flaky-question-dock-e2e
no-project-empty-state
fix/webkit-diff-viewer-crash
repro/watcher-als-bug
kit/repro-interrupted-text
startup
revert-17354-opencode/mighty-garden
move-status
perf/tui-session-history-cursor
effect-auth-foundation
console-subcommands
title-bar-cleanup
effect-log-compat
node-pty
fix/interrupt-idle-reason-poc
fix/interrupt-double-sound
opencode/proud-rocket
jlongster/automatic-session-routing
refactor/node-server-adapter
add-api-shape
node-build
jlongster/revert-sighup
fix/memory-tui-cache-listeners
auto-accept-permissions
pr-16286
default-explore-models
kit-pr
kit-pr-ahhhh
fix/16323-keyed-show-callbacks
feat/hashline-edit-experimental-v2
fix/git-fsmonitor-cleanup
snapshot-spawn-server-logs
implement-background-agents
opencode/happy-planet
fix/subagent-navigation-inline-click
go-page
fix/daytona-plugin-link-15976
opencode/hidden-orchid
tweaks
sidebar-fade-scroll
migrate-enterprise-to-nextjs
migrate-web-to-nextjs
migrate-app-to-nextjs
migrate-console-app-to-nextjs
fix/beta-stack-aware-sync
feature/tui-assistant-tokens-per-second
opencode/misty-falcon
snapshot-node-pty
update-stats
legal-req
commit-history
mhart/fix-cloning-slowness
chore/duplicate-issues-agent-dev
chore/duplicate-issues-agent
migrate-skill-discovery
migrate-mcp
migrate-config
optimize-apply-patch
temp
test-fields
brendan/nsis-vc-redistributables
chore-cleanup
feat/reference-agent
fix/attach-default-cwd
clean-modified-files
feat/discord-bot
v5-v6
feat/fff-file-search
snapshot-windows-desktop
fix-read-tool-for-webfetch
K-Mistele/dev
provider-optional-fields
feature/session-handoff
models-endpoint
opencode/sunny-harbor
utilize-family-in-dialog
review
tui-claude-style
rm-footer
fix/shiki-highlight-engine
fix/plugin-install-config
fix/plugin-install-location
feat/update-to-include-discord
git-slop-v2
docs-export
app/open-button
feature/workspace-domain
redesign-run-command
git-slop
opencode/clever-falcon
ripgrep-tree-paths
adjust-instructions-logic
fix-tool-ordering
workflow/publish-updates
chore-update-deps
feat/turborepo-caching
trigger-publish-on-beta
add-beta-branch-trigger
remove/nix-desktop-workflow
ci
fix-markdown-parsing
remove-highlights-template
update-to-add-learn-script
release-highlights-template
fixing-changelog-spacing
fixing-changelog-ui
fix-changelog-json
changelog-swr-caching
add-dynamic-agents-resolving
release-notes
fix/claude-pro-max-docs-warning
web-fixing-download-buton-on-changelog
fix/google-vertex-anthropic-thinking
sqlite
fix-azure-issue
desktop-poilsh-styles-ui-ux
desktop-shortcuts-panel
scheduler-module
apply-patch
cleanup-server-routes
fix-tool-outputs
fix-ai-message-issue
updated-black-page-performance
fix-black-page-view-transition-safari
update-design-subscriptions
fix-markdown-parser
fix/mcp-timeout
fix-id-issue
upgrade-bun
black-page-transitions-design-updates
official-copilot-plugin
plan-mode
read-plurals
cli-run-improvements
style-new-tips-layout
codex-auth
disable-auto-server
fix-model-dialog
fix-plugin-hook
feat/question-multiselect
new-toolbar-layout
feature/tui-sidebar-overlay
ui-improvements-some-animations
ask-question-tool
truncate-to-file
update-perms
truncation
snaphot-style-multiple-commands-input
experimental-mentions
queue-on-track
add-ignored
rename-repo-sst-to-anomalyco
permission-rework
ripgrep-tests
variants-docs
fix-custom-model-variants
read-global-claude-skills
changelog-updates
thinking-toggle-wip
style-current-todo
tui-shortcuts-panel
update-toggle-and-model-selection
small-screens
feature/skill-tool
feature/agent-skills
add-tests
llm-centralization
interleaved-fixes
interleaved-thinking
docs
sdk
bash-tweaks
provider-cleanup
fix-issue
blacksmith-migration-0ddfdb5
fix/cli-clean-exit-on-model-errors
pr-38252-videos
pr-37967-screenshots-final
pr-37967-screenshots-v2
pr-37967-screenshots
v1.18.4
v1.18.3
v1.18.2
v1.18.1
v1.18.0
v1.17.20
v1.17.19
pr-36567-inline-evidence
pr-36567-evidence
pr-36516-evidence
v1.17.18
v1.17.17
v1.17.16
v1.17.15
v1.17.14
v1.17.13
v1.17.12
v1.17.11
v1.17.10
pr-33649-assets
v1.17.9
v1.17.8
v1.17.7
v1.17.6
v1.17.5
v1.17.4
v1.17.3
v1.17.2
v1.17.1
v1.17.0
v1.16.2
v1.16.0
github-v1.2.25
v1.15.13
pr-29948-screenshots
v1.15.12
github-v1.2.24
github-v1.2.23
v1.15.11
v1.15.10
v1.15.9
v1.15.7
v1.15.6
v1.15.5
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.15.0
v1.14.51
v1.14.50
v1.14.49
v1.14.48
v1.14.47
v1.14.46
v1.14.45
v1.14.44
v1.14.43
v1.14.42
v1.14.41
v1.14.40
v1.14.39
v1.14.38
v1.14.37
v1.14.35
v1.14.34
v1.14.33
v1.14.32
v1.14.31
v1.14.30
v1.14.29
v1.14.28
v1.14.27
v1.14.26
v1.14.25
v1.14.24
v1.14.23
v1.14.22
v1.14.21
v1.14.20
v1.14.19
v1.14.18
v1.14.17
v1.4.14
v1.4.12
v1.4.11
v1.4.10
v1.4.9
v1.4.8
v1.4.7
github-v1.2.22
github-v1.2.21
github-v1.2.20
v1.4.6
v1.4.5
v1.4.4
v1.4.3
v1.4.2
v1.4.1
v1.4.0
latest
v1.3.17
v1.3.16
v1.3.15
v1.3.14
v1.3.13
v1.3.12
v1.3.11
v1.3.10
v1.3.9
v1.3.8
v1.3.7
v1.3.6
v1.3.5
v1.3.4
v1.3.3
github-v1.2.19
v1.3.2
v1.3.1
v1.3.0
v1.2.27
v1.2.26
v1.2.25
v1.2.24
v1.2.23
v1.2.22
v1.2.21
v1.2.20
v1.2.19
github-v1.2.18
v1.2.18
v1.2.17
v1.2.16
v1.2.15
v1.2.14
v1.2.13
v1.2.12
v1.2.11
github-v1.2.17
v1.2.10
v1.2.9
v1.2.8
v1.2.7
github-v1.2.16
v1.2.6
v1.2.5
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.65
v1.1.64
v1.1.63
v1.1.62
v1.1.61
v1.1.60
v1.1.59
v1.1.58
v1.1.57
v1.1.56
v1.1.55
v1.1.54
github-v1.2.15
v1.1.53
v1.1.52
v1.1.51
v1.1.50
v1.1.49
v1.1.48
v1.1.47
v1.1.46
v1.1.45
v1.1.44
github-v1.2.14
v1.1.43
v0.0.0-ci-202601291718
v0.0.0-ci-202601291635
v0.0.0-ci-202601291626
v1.1.42
v1.1.41
v1.1.40
v1.1.39
v1.1.38
v1.1.37
v1.1.36
v1.1.35
v1.1.34
v1.1.33
v1.1.32
v1.1.31
v1.1.30
v1.1.29
v1.1.28
v1.1.27
v1.1.26
github-v1.2.13
v1.1.25
v1.1.24
v1.1.23
v1.1.21
v1.1.20
v1.1.19
v1.1.18
github-v1.2.12
v1.1.17
v1.1.16
v1.1.15
v1.1.14
v1.1.13
v1.1.12
v1.1.11
v1.1.10
v1.1.8
v1.1.7
v1.1.6
v1.1.5
v1.1.4
v1.1.3
github-v1.2.11
v1.1.2
v1.1.1
github-v1.2.10
github-v1.2.9
github-v1.2.8
github-v1.2.7
v1.0.224
v1.0.223
v1.0.222
v1.0.221
v1.0.220
v1.0.219
v1.0.218
v1.0.217
v1.0.216
v1.0.215
v1.0.214
v1.0.213
v1.0.212
v1.0.211
v1.0.210
v1.0.209
v1.0.208
v1.0.207
v1.0.206
vscode-v0.0.13
v1.0.205
v1.0.204
v1.0.203
v1.0.202
v1.0.201
v1.0.200
v1.0.199
v1.0.198
v1.0.197
v1.0.196
v1.0.195
v1.0.194
v1.0.193
v1.0.192
v1.0.191
v1.0.190
v1.0.189
v1.0.188
v1.0.187
v1.0.186
v1.0.185
github-v1.2.6
v1.0.184
v1.0.183
v1.0.182
v1.0.181
github-v1.2.5
github-v1.2.4
v1.0.180
v1.0.179
v1.0.178
v1.0.177
v1.0.176
v1.0.175
v1.0.174
v1.0.173
v1.0.172
v1.0.171
v1.0.170
v1.0.169
v1.0.168
github-v1.2.3
github-v1.2.2
v1.0.167
v1.0.166
v1.0.165
v1.0.164
github-v1.2.1
v1.0.163
v1.0.162
v1.0.161
v1.0.160
v1.0.159
v1.0.158
v1.0.157
v1.0.156
v1.0.155
v1.0.154
v1.0.153
v1.0.152
v1.0.151
v1.0.150
v1.0.149
v1.0.148
v1.0.147
v1.0.146
v1.0.145
v1.0.144
github-v1.2.0
github-v1.1.0
v1.0.143
v1.0.142
v1.0.141
v1.0.138
v1.0.137
v1.0.134
v1.0.133
v1.0.132
v1.0.131
v1.0.130
v1.0.129
v1.0.128
v1.0.127
v1.0.126
v1.0.125
v1.0.124
v1.0.123
v1.0.122
v1.0.121
v1.0.120
v1.0.119
v1.0.118
v1.0.117
v1.0.116
v1.0.115
v1.0.114
v1.0.113
v1.0.112
v1.0.111
v1.0.110
v1.0.109
v1.0.108
v1.0.107
v1.0.106
v1.0.105
v1.0.104
v1.0.103
v1.0.102
v1.0.101
v1.0.100
v1.0.99
v1.0.98
v1.0.97
v1.0.96
v1.0.95
v1.0.93
v1.0.94
v1.0.92
v1.0.91
v1.0.90
v1.0.89
v1.0.88
v1.0.87
v1.0.86
v1.0.85
v1.0.84
v1.0.83
v1.0.82
v1.0.81
v1.0.80
v1.0.79
v1.0.78
v1.0.77
v1.0.76
v1.0.75
v1.0.74
v1.0.73
v1.0.72
v1.0.71
v1.0.70
v1.0.69
v1.0.68
v1.0.67
v1.0.66
v1.0.65
v1.0.64
v0.0.2-feature-bench
v1.0.63
v0.0.1-feature-bench
v1.0.62
v1.0.61
v1.0.60
v1.0.59
v1.0.58
v1.0.57
v1.0.56
v1.0.55
v1.0.54
v1.0.53
v1.0.52
v1.0.51
v1.0.50
v1.0.49
v1.0.48
v1.0.47
v1.0.46
v1.0.45
v1.0.44
v1.0.43
v1.0.41
v1.0.40
v1.0.39
v1.0.38
v1.0.37
v1.0.36
v1.0.35
v1.0.34
v1.0.33
v1.0.32
v1.0.31
v1.0.30
v1.0.29
v1.0.28
v1.0.27
v1.0.26
v1.0.25
v1.0.24
v1.0.23
v1.0.22
v1.0.21
v1.0.20
v1.0.19
v1.0.18
v1.0.17
v1.0.16
v1.0.15
v1.0.14
v1.0.13
v1.0.12
v1.0.11
github-v1.0.10
v1.0.10
v1.0.9
v1.0.8
v1.0.7
v1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
v1.0.0
v0.15.31
v0.15.30
v0.15.29
v0.15.28
v0.15.27
v0.15.26
v0.15.25
v0.15.24
v0.15.23
v0.15.21
v0.15.22
v0.15.20
v0.15.19
v0.15.18
v0.15.17
v0.15.16
v0.15.15
v0.15.14
vscode-v0.0.12
vscode-v0.0.11
vscode-v0.0.10
v0.15.13
v0.15.12
v0.15.11
v0.15.10
v0.15.9
v0.15.8
v0.15.7
v0.15.6
github-v1.0.9
github-v1.0.8
github-v1.0.7
v0.15.5
v0.15.4
v0.15.3
v0.15.2
v0.15.1
v0.15.0
v0.14.7
v0.14.6
v0.14.5
v0.14.4
v0.14.3
v0.14.1
v0.14.0
v0.13.9
v0.13.8
v0.13.7
v0.13.6
v0.13.5
v0.13.4
v0.13.3
v0.13.2
v0.12.1
v0.12.0
v0.11.8
v0.11.7
v0.11.6
v0.11.5
v0.11.4
v0.11.3
v0.11.2
v0.11.1
v0.11.0
v0.0.0-202509210757
v0.10.4
v0.10.3
github-v1.0.6
v0.10.2
v0.10.1
v0.10.0
v0.9.11
v0.9.10
v0.9.9
v0.9.8
v0.9.7
v0.9.6
v0.9.5
v0.9.4
v0.9.3
v0.9.2
v0.9.1
v0.9.0
v0.8.0
v0.0.0-202509130959
v0.0.0-202509130953
v0.0.0-202509130949
v0.7.9
v0.7.8
v0.7.7
v0.7.6
v0.7.5
v0.7.4
v0.7.3
v0.7.2
v0.7.1
v0.7.0
v0.6.10
v0.6.9
v0.6.8
v0.6.7
v0.6.6
v0.6.5
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.0.0-202509010531
v0.0.0-202509010020
v0.5.29
v0.5.28
v0.5.27
v0.5.26
v0.5.25
v0.5.24
v0.5.23
v0.5.18
v0.5.15
v0.5.13
v0.5.12
v0.5.11
v0.5.10
v0.5.9
v0.5.8
v0.5.7
v0.5.6
github-v1.0.5
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.4.45
v0.4.44
v0.4.43
v0.4.42
v0.4.41
v0.4.40
v0.4.37
v0.4.36
v0.4.34
v0.4.29
v0.4.28
v0.4.27
v0.4.26
v0.4.25
v0.4.24
v0.4.23
v0.4.22
v0.4.21
v0.4.20
v0.4.19
v0.4.18
v0.4.17
v0.4.16
v0.4.15
v0.4.14
v0.4.13
v0.4.12
v0.4.11
v0.4.10
v0.4.6
v0.4.4
v0.4.5
v0.4.3
v0.4.2
v0.4.1
v0.4.0
v0.3.133
v0.3.132
v0.3.131
v0.3.130
v0.3.129
v0.3.128
v0.3.127
v0.3.126
v0.3.124
v0.3.123
v0.0.0-202508031658
v0.0.0-202508031655
v0.0.0-202508031652
v0.0.0-202508031649
v0.0.0-202508031638
v0.0.0-202508031634
v0.0.0-202508031629
v0.3.122
v0.3.121
v0.3.120
v0.3.119
v0.3.118
v0.3.117
v0.3.116
v0.3.115
v0.3.114
v0.0.0-202508022246
v0.0.0-202508022229
v0.0.0-202508022228
v0.0.0-202508022056
v0.0.0-202508022055
v0.0.0-202508022053
v0.3.113
v0.3.112
v0.3.111
v0.3.110
v0.3.109
v0.3.108
v0.3.107
v0.3.106
v0.3.105
v0.3.104
v0.3.103
vscode-v0.0.8
vscode-v0.0.9
v0.3.102
v0.3.101
v0.3.100
v0.3.93
v0.3.92
v0.3.90
v0.3.88
v0.0.0-202507310417
v0.3.87
v0.3.86
v0.3.85
v0.3.84
v0.3.83
v0.3.82
v0.3.81
v0.3.80
vscode-v0.0.7
v0.3.79
v0.3.78
v0.3.77
v0.3.76
v0.3.75
github-v1.0.4
github-v1.0.3
v0.3.74
v0.3.72
v0.3.73
v0.3.71
v0.3.70
v0.3.69
v0.3.68
v0.3.67
v0.3.66
v0.3.65
v0.3.64
v0.3.63
v0.3.62
v0.3.61
v0.3.60
v0.3.59
v0.3.58
v0.3.57
v0.3.56
vscode-v0.0.6
v0.3.55
vscode-v0.0.5
v0.3.54
v0.3.53
v0.3.52
v0.3.51
v0.3.50
v0.3.49
v0.3.48
v0.3.47
v0.3.46
v0.3.45
v0.3.44
vscode-v0.0.4
github-v1
vscode-v0.0.3
github-v1.0.2
github-v1.0.1
github-v1.0.0
vscode-v0.0.2
v0.3.43
v0.3.41
v0.3.42
v0.3.40
v0.3.39
v0.3.38
v0.3.37
v0.3.36
v0.3.35
v0.3.34
v0.3.33
v0.3.32
v0.3.31
v0.3.30
v0.3.29
v0.3.28
v0.3.27
v0.3.26
v0.3.25
v0.3.24
v0.3.23
v0.3.22
v0.3.21
v0.3.20
v0.3.19
vscode-v0.0.1
v0.3.18
v0.3.17
v0.3.16
v0.3.15
v0.3.14
v0.3.13
v0.3.12
v0.3.10
v0.3.11
v0.3.9
v0.3.8
v0.3.7
v0.3.5
v0.3.6
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.2.35
v0.3.0
v0.2.34
v0.2.33
v0.2.31
v0.2.32
v0.2.30
v0.2.28
v0.2.29
v0.2.27
v0.2.26
v0.2.25
v0.2.24
v0.2.23
v0.2.22
v0.2.21
v0.2.20
v0.2.19
v0.2.18
v0.2.17
v0.2.16
v0.2.15
v0.2.14
v0.2.13
v0.2.12
v0.2.11
v0.2.10
v0.2.9
v0.2.7
v0.2.8
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.195
v0.1.196
v0.1.194
v0.1.193
v0.1.192
v0.1.190
v0.1.191
v0.1.189
v0.1.188
v0.1.187
v0.1.186
v0.1.185
v0.1.184
v0.1.183
v0.1.182
v0.1.181
v0.1.180
v0.1.179
v0.1.178
v0.1.177
v0.1.176
v0.1.175
v0.1.174
v0.1.173
v0.1.172
v0.1.171
v0.1.170
v0.1.169
v0.1.168
v0.1.167
v0.1.166
v0.1.165
v0.1.164
v0.1.163
v0.1.162
v0.1.161
v0.1.160
v0.1.159
v0.1.158
v0.1.157
v0.1.156
v0.1.155
v0.1.154
v0.1.153
v0.1.152
v0.1.151
v0.1.150
v0.1.149
v0.1.148
v0.1.147
v0.1.146
v0.1.145
v0.1.144
v0.1.143
v0.1.142
v0.1.141
v0.1.140
v0.1.139
v0.1.138
v0.1.137
v0.1.136
v0.1.135
v0.1.133
v0.1.134
v0.1.132
v0.1.131
v0.1.130
v0.1.129
v0.1.128
v0.1.127
v0.1.126
v0.1.125
v0.1.124
v0.1.123
v0.1.122
v0.1.121
v0.1.120
v0.1.119
v0.1.118
v0.1.117
v0.1.116
v0.1.115
v0.1.114
v0.1.113
v0.1.112
v0.1.111
v0.1.110
v0.1.109
v0.1.108
v0.1.107
v0.1.106
v0.1.105
v0.1.104
v0.1.103
v0.1.101
v0.1.102
v0.1.100
v0.1.99
v0.1.98
v0.1.97
v0.1.96
v0.1.95
v0.1.94
v0.1.93
v0.1.92
v0.1.91
v0.1.90
v0.1.89
v0.1.88
v0.1.87
v0.1.86
v0.1.85
v0.1.84
v0.1.83
v0.1.82
v0.1.81
v0.1.80
v0.1.79
v0.1.78
v0.1.77
v0.1.76
v0.1.75
v0.1.74
v0.1.73
v0.1.72
v0.1.71
v0.1.70
v0.1.69
v0.1.68
v0.1.67
v0.1.66
v0.1.65
v0.1.64
v0.1.63
v0.1.62
v0.1.61
v0.1.60
v0.1.59
v0.1.58
v0.1.57
v0.1.56
v0.1.55
v0.1.54
v0.1.53
v0.1.52
v0.1.51
v0.1.50
v0.1.49
v0.1.48
v0.1.47
v0.1.46
v0.1.45
v0.1.44
v0.1.43
v0.1.42
v0.1.41
v0.1.40
v0.1.39
v0.1.38
v0.1.37
v0.1.36
v0.1.35
v0.1.34
v0.1.33
v0.1.32
v0.1.31
v0.1.30
v0.1.29
v0.1.28
v0.1.27
v0.1.26
v0.1.24
v0.1.25
v0.1.23
v0.1.22
v0.1.21
v0.1.20
v0.1.19
v0.1.18
v0.1.17
v0.1.16
v0.1.15
v0.1.14
v0.1.13
v0.1.12
v0.1.11
v0.1.10
v0.1.9
v0.1.6
v0.1.7
v0.1.8
v0.1.5
v0.1.4
v0.1.3
v0.1.2
v0.1.1
v0.1.0-beta3
v0.1.0-beta2
v0.1.0-beta1
v0.1.0
v0.0.55
v0.0.54
v0.0.53
v0.0.52
v0.0.51
v0.0.50
v0.0.49
v0.0.48
v0.0.46
v0.0.45
v0.0.47
0.0.47
0.0.46
0.0.45
v0.0.44
v0.0.43
v0.0.42
v0.0.41
v0.0.40
v0.0.39
v0.0.38
v0.0.37
v0.0.36
v0.0.35
v0.0.34
v0.0.33
v0.0.32
v0.0.31
v0.0.30
v0.0.29
v0.0.28
v0.0.27
v0.0.26
v0.0.25
v0.0.24
v0.0.22
v0.0.21
v0.0.20
v0.0.19
v0.0.18
v0.0.17
v0.0.16
v0.0.15
v0.0.14
v0.0.13
v0.0.10
v0.0.9
v0.0.8
v0.0.7
v0.0.6
v0.0.3
v0.0.4
v0.0.5
v0.0.2
v0.0.1
Milestone
No items
No Milestone
Projects
Clear projects
No project
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: anomalyco/opencode#4475
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @piotryordanov on GitHub (Jan 8, 2026).
Originally assigned to: @thdxr on GitHub.
Description
As of a few moments ago, usage of claude max stopped with the following error:
I did try to reconnect, but got the same error.
Plugins
No response
OpenCode version
1.1.8
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
mac
Terminal
No response
@github-actions[bot] commented on GitHub (Jan 8, 2026):
This issue might be a duplicate of existing issues. Please check:
Feel free to ignore if none of these address your specific case.
@iloveicedgreentea commented on GitHub (Jan 8, 2026):
Me too. It was working fine 1 hour ago and now I am getting this error. I am on version 1.0.220. Claude status is up, but not sure if its a provider issue. Gpt 5.2 with the oauth plugin works for me
@Manokit commented on GitHub (Jan 8, 2026):
Having the same issue, been using it all afternoon/evening and just got this.
@azizikri commented on GitHub (Jan 8, 2026):
me too, working fine yesterday
@Naomarik commented on GitHub (Jan 8, 2026):
Same. Downgraded my claude plan to $100 immediately because I won't be able to use it as much without opencode.
Honestly using CC is like going back to stone age. Gonna be rough until if/when this gets fixed.
EDIT: I've cancelled my Anthropic subscription completely. Trying to use CC for the last 10 minutes and it's unusuable for the workflows I have and the visibility I need that opencode has enabled me to have. Will explore other models.
@fm1randa commented on GitHub (Jan 8, 2026):
Same
@diasm3 commented on GitHub (Jan 8, 2026):
got a message too
@andrhlt commented on GitHub (Jan 8, 2026):
came here to find exactly this
@arthur404dev commented on GitHub (Jan 8, 2026):
Same here... Can't believe anthropic would shoot themselves in the foot like this...
@piotryordanov commented on GitHub (Jan 8, 2026):
@arthur404dev technically, this has nothing to do with anthropic. I don't believe we are supposed to be able to use the max plan outside of anthropic tools the way we are.
@kandotrun commented on GitHub (Jan 8, 2026):
same ;;
@thdxr commented on GitHub (Jan 8, 2026):
it's likely they blocked it - i don't have time right now to investigate how but it's possible they blocked opencode specifically
@ChristianPavilonis commented on GitHub (Jan 8, 2026):
It seems to work now for me
@piotryordanov commented on GitHub (Jan 8, 2026):
@thdxr FWIW, I have a separate version running with rig that uses the same auth method, and it also gets the same error. Might that they changes the system prompt needed to talk to them.
@norlanp commented on GitHub (Jan 8, 2026):
I had the same error 10 mins ago, it's working again for me.
@cryptobetEU commented on GitHub (Jan 8, 2026):
I had same error, you must do opencode logout and afterwards opencode login and it will work again (doing without logout gies same error)
36% of max(20x) on 14 hours consumed lol
@jander99 commented on GitHub (Jan 8, 2026):
The scopes changed. The "2 minutes ago" is from a fresh opencode, the other is from
claude. So what'suser:sessions:claude_code? Wonder if it can be requested when opencode logs in?Edit: WSL opencode 1.1.8, oh-my-opencode 2.14.0
@cryptobetEU commented on GitHub (Jan 8, 2026):
and same error again. i go sleep I see tommorow
@fm1randa commented on GitHub (Jan 8, 2026):
It is not only opencode that was blocked. Clawdbot also doesn't work anymore.
@Hebububu commented on GitHub (Jan 8, 2026):
for me, it's intermittently repeating works and fails
@rohaanmalik commented on GitHub (Jan 8, 2026):
yes, does not work for either! I even tried logging in and out.
@manishprivet commented on GitHub (Jan 8, 2026):
Same here 😢
@Christopher-R-Perkins commented on GitHub (Jan 8, 2026):
I revoked the authorization tokens on claude's website then readded with /connect and no longer get the error message. I did notice I had 3 access tokens rather than 2, so may be related.
@GukDev commented on GitHub (Jan 8, 2026):
CC taking out the competition
@code-xhyun commented on GitHub (Jan 8, 2026):
same
@iloveicedgreentea commented on GitHub (Jan 8, 2026):
Didnt work for me. I revoked every token, opencode auth logout, then login, same issue. I tried updating to 1.1.8 as well. maybe they updated oauth scopes
@solssak commented on GitHub (Jan 8, 2026):
same
@justcarlson commented on GitHub (Jan 8, 2026):
same
@kilhyeonjun commented on GitHub (Jan 8, 2026):
same
@KFC-original commented on GitHub (Jan 8, 2026):
same
@Does-splab commented on GitHub (Jan 8, 2026):
same
@381181295 commented on GitHub (Jan 8, 2026):
same
@shjeong92 commented on GitHub (Jan 8, 2026):
same
@solssak commented on GitHub (Jan 8, 2026):
I think I'm going to have a panic attack
@grayashh commented on GitHub (Jan 8, 2026):
Sam Hammington
@kandotrun commented on GitHub (Jan 8, 2026):
Indeed, when I restarted Claude Code just now, a token related to
user:sessions:claude_codewas generated.Before launching the latest Claude Code, there were only
user:inferenceanduser:profile.@RovshanMuradov commented on GitHub (Jan 8, 2026):
same
@justcarlson commented on GitHub (Jan 8, 2026):
did Anthropic just ban OpenCode Oauth?
@isomoes commented on GitHub (Jan 8, 2026):
same
@jander99 commented on GitHub (Jan 8, 2026):
My assumption here is that opencode needs to request the additional scope. Anthropic probably shadowbanned non-claude-code access because their API now requires the additional scope.
@ariane-emory commented on GitHub (Jan 8, 2026):
@piotryordanov You said this has 'nothing to do with Anthropic'... but who does the fact that using the CC plan in non-CC tools is a TOS violation have to do with, if not Anthropic? It was Anthropic who wrote that TOS and it was Anthropic who chose to try to enforce it, no one else did that.
@friksa commented on GitHub (Jan 8, 2026):
logout and log back in with Anthropic does not help. Same issue
@popododo0720 commented on GitHub (Jan 8, 2026):
It seems like the new user:sessions:claude_code scope was added to isolate Claude Code sessions from other clients. A dedicated scope was needed to manage CLI sessions separately.
@jonleopard commented on GitHub (Jan 8, 2026):
Well this might be a huge bummer....
@boxpositron commented on GitHub (Jan 8, 2026):
Kudos to the team working on the OAuth patch. I understand you did not plan for this but we need you. The world needs you.
@ForeverAnApple commented on GitHub (Jan 8, 2026):
I attempted to replace my opencode auth and refresh tokens with the newly generated claude-code tokens, but it didn't work. I assume there's some kinda way to inject the new scope into opencode itself and mock the request as if coming from claude-code.
@josephboyd9 commented on GitHub (Jan 8, 2026):
Using the claude sonnet model via Github Copilot key still works, at least. I really hope this is only going to be temporary though.
@friksa commented on GitHub (Jan 8, 2026):
Just canceled my Anthropic Max plan and cited this as the reason. Have to send a message or they will all follow suite, OpenAI, Google, etc.
@hffmnnj commented on GitHub (Jan 8, 2026):
Might've just gave Opencode free advertising for Opencode Black accidentally... lol
@LukasMurdock commented on GitHub (Jan 8, 2026):
Commenting for search visibility (kept trying to search the GitHub issues and this wasn’t showing up), the error is
@chriswritescode-dev commented on GitHub (Jan 8, 2026):
This is bull shit
@Tetrahedrite commented on GitHub (Jan 8, 2026):
I have GitHub Copilot Pro+ subscription, so I gave it a shot. But it seems context window is hardly limited in 120K or 128K level.
@arthur404dev commented on GitHub (Jan 8, 2026):
Seems like they literally shot themselves in the foot
https://github.com/charmbracelet/crush/pull/1783
@pleaz commented on GitHub (Jan 8, 2026):
I tried to add scope manually to have this additional - user:sessions:claude_code for Opencode as well, but still same error.
@hellosmith commented on GitHub (Jan 8, 2026):
same
@stuartbuckell commented on GitHub (Jan 8, 2026):
It was fun while it lasted guys !
@seogi1004 commented on GitHub (Jan 8, 2026):
same...
@ramarivera commented on GitHub (Jan 8, 2026):
Im so mad I missed this one lol
@Klassikcat commented on GitHub (Jan 8, 2026):
same here. seems like i have to cancel my subscription and use other llm providers instead...
@iloveicedgreentea commented on GitHub (Jan 8, 2026):
If this is true, I am cancelling all my anthropic subscriptions and making sure we don't use it anywhere, work or personal
@JakeB-5 commented on GitHub (Jan 8, 2026):
I canceled subscription Claude Max
@diogosalazar commented on GitHub (Jan 8, 2026):
Had just signed up for Claude Max (2 hours ago) --- guess I am going to ask them for a full refund
@manishprivet commented on GitHub (Jan 8, 2026):
Maybe this can help?
https://github.com/anomalyco/opencode-anthropic-auth/pull/9
@manishprivet commented on GitHub (Jan 8, 2026):
Ah my Pr will not work 😞
@arimxyer commented on GitHub (Jan 8, 2026):
This is f**ked.
@justcarlson commented on GitHub (Jan 8, 2026):
Opencode Black Beta can't rollout fast enough
@Mithrillion commented on GitHub (Jan 8, 2026):
This is odd... It seems Opencode is not working but the same key still works in Kilo Code at the moment, so not sure if it is a client side or provider side problem...
@xiliumz commented on GitHub (Jan 8, 2026):
yeah, the time is over hahaha
@spik3r commented on GitHub (Jan 8, 2026):
Same issue with Claude Pro, was working fine until recently.
@Tetrahedrite commented on GitHub (Jan 8, 2026):
What provider are you using with Kilo Code? Based on my memory, there's two option "Claude Code" and "Anthropic".
Claude Code provider doesn't use OAuth method but directly calls 'claude' binary.
@FreeSamples00 commented on GitHub (Jan 8, 2026):
Same issue here. Re-authing with opencode and claude code did not help.
@oomathias commented on GitHub (Jan 8, 2026):
The system prompt seems to be the key.-> It's the tools.With the official system prompt the API answer, with another one it gives the same error.@watzon commented on GitHub (Jan 8, 2026):
@oomathias I figured. This probably got patched https://github.com/anomalyco/opencode/blob/dev/packages/opencode/src/session/prompt/anthropic_spoof.txt
@fm1randa commented on GitHub (Jan 8, 2026):
The system prompt already includes "You are Claude Code, Anthropic's official CLI for Claude." in anthropic_spoof.txt. This is used as the header for all Anthropic providers at system.ts:22.
@a-dmx commented on GitHub (Jan 8, 2026):
I wonder what's their business value with that move.
@sergiotapia commented on GitHub (Jan 8, 2026):
Time to shift to GLM 4.7
I don't mind paying for a proper quantized version of the model. Is the one offered for free a limited or quantized in some way?
What provider should I use for proper GLM 4.7 just z.ai?
@RawToast commented on GitHub (Jan 8, 2026):
Either z.ai, cerebras (fast), or wait and see what Opencode Black brings
@sergiotapia commented on GitHub (Jan 8, 2026):
This is the first time I hear about OpenCode Black what is that?
@azatakmyradov commented on GitHub (Jan 8, 2026):
I got the idea from here but it seems like they banned opencode tools.
This works for me. If I change read_tool to read then I get the error
@oomathias commented on GitHub (Jan 8, 2026):
Yes I can confirm commenting this line is enough to get answers. The system prompt is fine as it is.
https://github.com/anomalyco/opencode/blob/bded900ef7de536faaa791aeffbcbbf727a98432/packages/opencode/src/session/llm.ts#L156
@airtonix commented on GitHub (Jan 8, 2026):
You can actually just change
read_tooltoReadand it still works... the moment you change it toreadthen it errors.also:
read_toolalone worksreadtool errorsread_toolwithreaderrorsread_toolwithreadandReaderrors@MilesNorton commented on GitHub (Jan 8, 2026):
I'm getting this issue with a company plan
@airtonix commented on GitHub (Jan 8, 2026):
it won't matter what kind of plan you use.
@gregkonush commented on GitHub (Jan 8, 2026):
post memes
@sleepybyte23 commented on GitHub (Jan 8, 2026):
Yo bro WTF is happening need claude code to work, best alternatives? Thanks.
@kamafozilov commented on GitHub (Jan 8, 2026):
@gregkonush commented on GitHub (Jan 8, 2026):
@sleepybyte23 commented on GitHub (Jan 8, 2026):
I switched to Codex for now, if this gets drained ill go to Claude API :(
@jksjaz commented on GitHub (Jan 8, 2026):
This would solve it? https://github.com/anomalyco/opencode-anthropic-auth/pull/10
@KimDaehyeon6873 commented on GitHub (Jan 8, 2026):
please check this
@oomathias commented on GitHub (Jan 8, 2026):
This renames all tools with
read→rea_. Use at your own risk.@casparvitch commented on GitHub (Jan 8, 2026):
I use synthetic.new, they have a subscription model. Unsure how they compare to the above. Privacy focused.
@souravrs999 commented on GitHub (Jan 8, 2026):
So what exactly caused Anthropic to do this ?, They worried OC gonna grab a piece of their pie?. As a consumer i would expect to use a TUI i prefer on a product that i purchased. Sorry if i'm being ignorant & not understanding something here, please feel free to educate me.
@harshav167 commented on GitHub (Jan 8, 2026):
Claude Code Pro/Max OAuth tokens now fail in OpenCode with:
Impact
Claude Code Pro/Max subscribers can’t use OpenCode with OAuth tokens.
Evidence (Proxyman)
Claude Code (works)
/v1/messages?beta=trueuser-agent: claude-cli/2.1.2 (external, cli)authorization: Bearer sk-ant-oat…anthropic-beta: oauth-2025-04-20, interleaved-thinking-2025-05-14claude-code-20250219OpenCode (fails)
/v1/messagesuser-agent: ai-sdk/anthropic/2.0.56 … runtime/bun/1.3.5authorization: Bearer sk-ant-oat…anthropic-beta: oauth-2025-04-20, claude-code-20250219, interleaved-thinking-2025-05-14, fine-grained-tool-streaming-2025-05-14400 invalid_request_errorwith the Claude Code–only messageLikely cause
Anthropic now enforces that Claude Code OAuth tokens only work for Claude Code–shaped requests.
OpenCode differs in endpoint/query + client identity (user-agent + beta flags), so the token is rejected.
@rdvo commented on GitHub (Jan 9, 2026):
i renamed all th tools to match the tool names claude code uses (pascal case) works for now
@enk0de commented on GitHub (Jan 9, 2026):
same here
@KBLCode commented on GitHub (Jan 9, 2026):
this works perfectly.
@jksjaz commented on GitHub (Jan 9, 2026):
So this PR got merged. I guess a release coming up for this repo too?
@KwokJay commented on GitHub (Jan 9, 2026):
Same
@Nando-suka commented on GitHub (Jan 9, 2026):
same
@dbnewman commented on GitHub (Jan 9, 2026):
It's def just a temp fix though, better idea would be to rename all the tools to a random string on every new session so pattern detection is avoided
@seogi1004 commented on GitHub (Jan 9, 2026):
I cancelled my ClaudeCode subscription and switched to Gemini Ultra
@harshav167 commented on GitHub (Jan 9, 2026):
https://github.com/anomalyco/opencode-anthropic-auth/pull/11
i just created a pr for a long term fix rather than just renaming tools
@joecervino commented on GitHub (Jan 9, 2026):
Same issue.
I bought Gemini Ultra, can be great but lord have mercy the performance dips vs. Opencode + Claude is undeniable
@navendugoyal19 commented on GitHub (Jan 9, 2026):
doesnt work
@harshav167 commented on GitHub (Jan 9, 2026):
This PR fixes the actual request‑signature mismatch that Anthropic is enforcing for Claude Code OAuth tokens:
@deveworld commented on GitHub (Jan 9, 2026):
The fix has been merged in anomalyco/opencode-anthropic-auth#11.
Until it's published, here's a workaround:
Clone the repo:
git clone https://github.com/anomalyco/opencode-anthropic-auth.gitAdd to
~/.config/opencode/opencode.json:OPENCODE_DISABLE_DEFAULT_PLUGINS=true opencodeWorked for me!
@sahilchouksey commented on GitHub (Jan 9, 2026):
This works! Thanks.
@harshav167 commented on GitHub (Jan 9, 2026):
writing this fix using GPT 5.2 Codex Extra High made me realize how maybe i dont need opus 4.5 🫣
@piotryordanov commented on GitHub (Jan 9, 2026):
@harshav167 lol try using minimax m2. You'd be surprised by how capable (and cheap) it is.
Good thing in opencode, you can just swap models out.
Anthropic clearly doesn't like that!
@jagtesh commented on GitHub (Jan 9, 2026):
Has an integration using ACP (https://zed.dev/acp) been considered? It would use Claude Code under the hood, so it should still be compatible with their definition of intended use.
@axsuul commented on GitHub (Jan 9, 2026):
@harshav167 How did you get access to 5.2 Codex via the API?
@stewnight commented on GitHub (Jan 9, 2026):
According to Claude:
TLDR: Anthropic recently locked down Claude Code authentication tokens so they can't be used with third-party tools like OpenCode. You'll need a separate API key from console.anthropic.com.
TOC
What's happening
Why the change
Your options
What's Happening
Anthropic has recently tightened the authentication for Claude Code. The OAuth token you get when you run claude and authenticate is now scoped exclusively to the official Claude Code CLI. Previously, this token worked as a general API credential — now it doesn't.
This is a deliberate change, not a bug.
Why the Change
Strong opinion: This is Anthropic protecting their usage-based pricing model. Claude Code has different (more generous) rate limits and possibly different billing arrangements than raw API access. By locking the credential, they're preventing:
Third-party tools piggybacking on Claude Code's auth
Potential abuse of the authentication flow
Usage that bypasses their standard API billing
Fair enough from a business perspective, but it does break workflows people had set up.
@jihunkim0 commented on GitHub (Jan 9, 2026):
@Naomarik I'm on a similar boat as well. I'm trying to see if I can adapt to CC. Do you mind sharing at high level that works with opencode but doesn't with CC please?
@AlexZan commented on GitHub (Jan 9, 2026):
I just cancelled my CC max plan also. Was this intentional to force the use of Claude cli? Anyone know?
@deveworld commented on GitHub (Jan 9, 2026):
The fix has been merged in anomalyco/opencode-anthropic-auth#11, and #7432 is open to bump the version.
Until it's released, see the workaround above.
@harshav167 commented on GitHub (Jan 9, 2026):
https://github.com/numman-ali/opencode-openai-codex-auth 🫣👀
@43034r commented on GitHub (Jan 9, 2026):
Same issue.
Looks like Anthropic shot themselves in the foot here. Without the ability to use their models in OpenCode, I'm just gonna cancel my subscription.
@FreeSamples00 commented on GitHub (Jan 9, 2026):
Anyone got a good rec for switching off claude code? Currently considering GLM 4.7 from synthetic.new or similar, or perhaps chatGPT.
I want a ~$20 subscription, not a per token API
@kzhrv commented on GitHub (Jan 9, 2026):
This inconvenient but always solvable as client side can always be made a 1:1 replication of what their client already does on the protocol level. If it gets to the point you have to keep a patched bun repo as well, to keep opencode working with Anthropic models, then it will get if-y.
What cannot be solved also is if they, anthropic, start banning people for not using their client. This situation might be they hope people leave.
It is puzzling behavior as anthropic and any other inference provider is really dependent on scavenging human traces, so what is their end goal, idk. Maybe claude code already is baking in far greater tracing capability?
@leeweisern commented on GitHub (Jan 9, 2026):
I don't think this will hurt them at all, unless you stop using claude models completely.
@StefanIliev545 commented on GitHub (Jan 9, 2026):
No opencode, no subscription. It really is this simple.
@marco-kretz commented on GitHub (Jan 9, 2026):
I’m facing the same issue. It’s clearly another step toward ecosystem lock-in. The subscription provides a significantly higher request volume compared to the API. For $100 on the "Max 5x" tier, you receive a value in requests that would cost several hundred dollars via API.
They are leveraging their current market lead and the surrounding hype to bind users. There is no incentive for them to share their USP with third parties.
From an economic standpoint, this makes perfect sense; from our perspective, it sucks.
@kzhrv commented on GitHub (Jan 9, 2026):
is using another client to their service robbing anthropic, is opencode stealing their platform away?
@leeweisern commented on GitHub (Jan 9, 2026):
Claude code subscription is a loss leader; they want to lock you in with Claude code so that Enterprise will lock in the Team plan. However, if you're using Opencode in your organisation, you will work with Opencode instead.
@kzhrv commented on GitHub (Jan 9, 2026):
People use claude models, the reason for anthropic's platform to exist, because they extract value or they think they extract value. I fail to see what more can anthropic expect from this process in terms of capital exchange: product -> purchase. Who cares you purchased the product with eur or usd?
So people using opencode purchase anthropic, its not like they are not purchasing.
@KimDaehyeon6873 commented on GitHub (Jan 9, 2026):
This is nonsense. Even though I got the point, but still doesn't make sense. After this change, people will no more able to use Opencode(oh-my-opencode) with Claude subscription.
Now only the API key option is available.
@adamkdean commented on GitHub (Jan 9, 2026):
Maybe someone should use CC to look through CC and find how CC authenticates and then put that into OC?
@marco-kretz commented on GitHub (Jan 9, 2026):
Bad idea. That's a violation against their TOS and will likely just get your account suspended.
@b-za commented on GitHub (Jan 9, 2026):
same issue, yesterday it worked today got the error message
@meteyou commented on GitHub (Jan 9, 2026):
got the same issue today. i installed the pre-released fix form here (https://github.com/anomalyco/opencode-anthropic-auth/pull/11) and it works again!
@KimDaehyeon6873 commented on GitHub (Jan 9, 2026):
FR? I think I need to set it up again 👍👍
@jksjaz commented on GitHub (Jan 9, 2026):
I don't know if y'all need to do this (since its not in the patch instructions) but to use that patch, I had to do
bun installotherwise opencode was crashing.@Mithrillion commented on GitHub (Jan 9, 2026):
I believe that Claude appears to hold some advantage because so many agent harnesses are tuned with a bias towards their models (either through developer familiarity, number of raised tickets or even vendor API adoption). With their current policies, hopefully this will discourage people from writing workflows, tools and prompts that are preferentially optimised for Claude. Let us see how much water they hold given truly neutral tooling.
@paolomainardi commented on GitHub (Jan 9, 2026):
Not strictly related, but since Copilot could be the next to violate the TOS, I've asked for an official response here: https://github.com/orgs/community/discussions/183809. If someone can help raise this question, it's more than welcome.
@n2k3 commented on GitHub (Jan 9, 2026):
confirmed working again on opencode 1.1.8 and by adding this to
opencode.json(either globally, or in your repo)@marco-kretz commented on GitHub (Jan 9, 2026):
This may work for now but doesn't safe you from them detecting it tomorrow and suspend your account. Be warned. They seem to NOT want that, clearly.
@dario-valles commented on GitHub (Jan 9, 2026):
They support the ACP protocol, so it may still be usable through that path. https://github.com/zed-industries/claude-code-acp
@n2k3 commented on GitHub (Jan 9, 2026):
Are there known cases like this, users getting banned? (I didn't know this 😕️️️️️️)
@kzhrv commented on GitHub (Jan 9, 2026):
it a scary world.
@mathias-ewald commented on GitHub (Jan 9, 2026):
Clearly a reason to downgrade my subscription or switch entirely if that keeps happening
@ilvez commented on GitHub (Jan 9, 2026):
AFAIK it's gray area at least from terms of service perspective, but I'm pretty sure they will patch it up if they want to pursue this intent of blocking access. Reverse engineering probably is unstoppable force, but keeping people in check with "guns" is another matter. Not sure why they would want to do that to be honest, but since they started it already..
@ionabio commented on GitHub (Jan 9, 2026):
The worst case is they ban people and lose them as a subscriber! And I remember during 4.0 era, when they made a mistake that made their models dumber and they lost many subscribers, they started giving free limitted time Max's to Pro's or some offers to get people back.
@execute008 commented on GitHub (Jan 9, 2026):
Same here
@mmack commented on GitHub (Jan 9, 2026):
same here what a move...
@daonb commented on GitHub (Jan 9, 2026):
I've cancelled my Max subscription.
Claude Code is on its way to being the next CoPilot.
@jagai commented on GitHub (Jan 9, 2026):
Being banned from Antrhopic will also issue an auto refund. Do with this info as you please.
@EdgarSedov commented on GitHub (Jan 9, 2026):
Btw, given the chance, you may want to try out codex-5.2. It's really good
@cryptobetEU commented on GitHub (Jan 9, 2026):
GPT 5.2 or 5.1 (either ones) they only talk for me but make no actuall file changes...
@selectnull commented on GitHub (Jan 9, 2026):
I've just canceled my Claude subscription. opencode is more valuable to me at this point than a model used. I plan to use Gemini for a while and then see how it works and if it's not good enough I'll try others.
@EdgarSedov commented on GitHub (Jan 9, 2026):
GPT-5.2andGPT-5.2 Codexare different, it's a separate model, so maybe worth checking which one you use@d3m1art commented on GitHub (Jan 9, 2026):
The issue with the old auth plugin and it's not merged yet, but you can patch it locally
https://github.com/anomalyco/opencode/pull/7432
@harshav167 commented on GitHub (Jan 9, 2026):
theres a easier way in guide i commented in my pr broski
@n33pm commented on GitHub (Jan 9, 2026):
As a temporary fix, add "plugin": ["opencode-anthropic-auth@0.0.7"] to your .config/opencode/opencode.json file.
@MaxAst commented on GitHub (Jan 9, 2026):
you legend saved my day, thank you! was already starting to pull my hair out with claude code this morning
@angelguillen10 commented on GitHub (Jan 9, 2026):
This worked for me:
@harshav167 commented on GitHub (Jan 9, 2026):
we are also working on a pr where we replicate tool definitions on top of oauth replication to cement opencode stealth behavior when using claude max without being detected
@linkedlist771 commented on GitHub (Jan 9, 2026):
After a bunch of tests, I found that this validation is from the tools filed. If the tools field contains any of the default tool in the Claude Code, and somehow has different schemas, which will trigger this error.
So I suppose a custom rename should fix this?
@execute008 commented on GitHub (Jan 9, 2026):
That fixed it for me, thanks a lot king. God bless you!
@boxpositron commented on GitHub (Jan 9, 2026):
Awesome work on the quick patch everyone. I've been cheering on from the sides but watching this move from issue to fixed was awe inspiring of what we can do together as builders!. 🚀
@shekohex commented on GitHub (Jan 9, 2026):
This awesome, I now see a lot of invalid tool calls and error rates when the agent tires to call (ask user question tool, batch tool ..etc) are you fixing that too? @harshav167
@harshav167 commented on GitHub (Jan 9, 2026):
🫡
@harshav167 commented on GitHub (Jan 9, 2026):
im not having any issues since my pr tho? been using it heavily since and dont see error rates too
@stephenstubbs commented on GitHub (Jan 9, 2026):
Thank you! Adding the plugin works for me too. Life saver.
@ramtinJ95 commented on GitHub (Jan 9, 2026):
I see loads of tool call errors also.
@romankovalov commented on GitHub (Jan 9, 2026):
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
For everyone who is trying to hack the system using the plugin, please notice that you are risking to be banned.
"there are confirmed cases of accounts being detected and permanently banned"
https://www.reddit.com/r/opencodeCLI/comments/1q7yggk/psa_using_claude_code_oauth_in_thirdparty_tools/
https://github.com/anomalyco/opencode/issues/6930
@shekohex commented on GitHub (Jan 9, 2026):
Can you enable the experimental batch tool? also the try the new askuserquestion tool?
@ThomsenDrake commented on GitHub (Jan 9, 2026):
Worked like a charm!
@a-dmx commented on GitHub (Jan 9, 2026):
are they giving refunds after they ban you?
@romankovalov commented on GitHub (Jan 9, 2026):
@a-dmx I don't think so :)
@kzhrv commented on GitHub (Jan 9, 2026):
What for the time you spent on uploading trajectories to them? They aren't! Hell no.
For the money? Probably.
@harshav167 commented on GitHub (Jan 9, 2026):
Honestly if they do it's the nail in the coffin. As long as they don't see who made the fix specifically 💀
@kzhrv commented on GitHub (Jan 9, 2026):
I think they do, bud. But have you checked?
Check and tell us.
@romankovalov commented on GitHub (Jan 9, 2026):
I don't want to be banned
@kzhrv commented on GitHub (Jan 9, 2026):
Somebody braver thannus will try. Until then we dont spread fud.
@angelguillen10 commented on GitHub (Jan 9, 2026):
I think the bans are happening to users who changed their plan while using OAuth in OpenCode. Does that make sense? I've had Max for 4 months and I've been using OpenCode for 1 month, and so far everything's been fine.
Should I be careful now that Claude has been updated to version 2.1.2?
@n2k3 commented on GitHub (Jan 9, 2026):
I upgrade to from Pro to Max 5x on January 7th, I'm using opencode before that as well. Who knows what will happen, would suck to get banned though. I'm using it as intended, just not through their harness 😁
@harshav167 commented on GitHub (Jan 9, 2026):
For those who are worried about getting banned, on a technical level if all tools are renamed to match Claude code's signature it'll be lower chance for anthropic to detect abuse or usage outside of Claude code as mentioned in my pr
https://github.com/anomalyco/opencode-anthropic-auth/pull/11#issuecomment-3727524416
@marco-kretz commented on GitHub (Jan 9, 2026):
This will not do it the long run. As if they are unable to do heuristic pattern analysis on HOW OC is hitting the endpoints.
@kzhrv commented on GitHub (Jan 9, 2026):
@marco-kretz Are they? And why? You seem to know the why.
@marco-kretz commented on GitHub (Jan 9, 2026):
Okay, I don't know how legally safe this is, but I filed a complain on the support chat(-bot). Here is the translated (from German) transscript:
anthropic_2026_01_09_215472611486066.txt
@marco-kretz commented on GitHub (Jan 9, 2026):
This is pure speculation. It would make sense for them to lock users into their ecosystem after baiting them with Opus 4.5.
@kzhrv commented on GitHub (Jan 9, 2026):
@marco-kretz Users are already using their model. Users are already training their future models. Users are already paying. What is claude code in this frame, but a worse version of opencode? Why insist? Ego?
Now if they couple deeper analytics in tracing in claude code, and future tracing is a must, then this cuts all agents.
@adamkdean commented on GitHub (Jan 9, 2026):
It would be better for @anthropics to offer a Claude as a Subscription regardless of whether you use Claude Code or not. Usage is usage at the end of the day, is Claude Code the product or are Haiku/Sonnet/Opus the models?
@PauloDevelo commented on GitHub (Jan 9, 2026):
@selectnull commented on GitHub (Jan 9, 2026):
@rdvo commented on GitHub (Jan 9, 2026):
Cat and mouse can work but if they start sending c&d to Opencode and others it gets ugly , they won't legally be allowed to keep PR like this on the repo
Just depends if Anthropic would go that far, would be bad PR for developers and kinda against the whole ethos of "hacker" eng culture. They have a decision to make, on one end they want to keep CC as the primary tool, but in that same regard: just ship a better product and cream rises to the drop.
Let's see why they do next
Also as for the tool calling issues in frontend, need to make sure you transform back the tool names to what the desktop / frontend app is excepting before it hits the frontend
@eliziario commented on GitHub (Jan 9, 2026):
I had great success using GLM 4.6 on Cerebras Inference with Open Code. Just FYI.
@rickbassham commented on GitHub (Jan 9, 2026):
Issue is back after it was working with the updated plugin.
@paulp-o commented on GitHub (Jan 9, 2026):
Issue is back with new opencode-anthropic-auth applied.
@nullStack65 commented on GitHub (Jan 9, 2026):
opencode.json fix no longer works :(. at least i got a few hours in first! any news on new fix in this cat and mouse game to get it working for now?
@lucaschallamel commented on GitHub (Jan 9, 2026):
Same here, the quick fix from this morning does not work anymore, so I am seriously considering cancelling my CLAUDE MAX 200 subscription, with such a racketing attitude from ANTHROPIC !
@paulp-o commented on GitHub (Jan 9, 2026):
maybe the approach to using claude code headless commands, or using claude code sdk or even ACP might be the way. They're being too stubborn like hell
@nrminor commented on GitHub (Jan 9, 2026):
Same here. Sad the whackamole is already happening this quickly. I was hoping we'd at least get a Friday of work out of it!
@nullStack65 commented on GitHub (Jan 9, 2026):
This fix no longer works :(. at least i got a few hours in first! any news on where the repo is going from here? Hopefully will keep playing cat and mouse while allowed to do so (no legal letters)?
@Jeremie-m commented on GitHub (Jan 9, 2026):
The flow broke again as of right now
@moinulmoin commented on GitHub (Jan 9, 2026):
agree
@malhashemi commented on GitHub (Jan 9, 2026):
They added support for GLM 4.7 yesterday I heard
@Altamimi-Dev commented on GitHub (Jan 9, 2026):
same
This credential is only authorized for use with Claude Code and cannot be used for other API requests.
@nullStack65 commented on GitHub (Jan 9, 2026):
crazy they already patched the workaround
@angelguillen10 commented on GitHub (Jan 9, 2026):
Same here, it's not working for me anymore. Any updates? @harshav167
@Linkk93 commented on GitHub (Jan 9, 2026):
I mean, they are probably also reading this
@angelguillen10 commented on GitHub (Jan 9, 2026):
If they read this, they should know that they are losing customers.
@UltraInstinct0x commented on GitHub (Jan 9, 2026):
Why would someone work relentlessly to prevent their users from logging in to a better open source project with their paid subscriptions instead of making their product actually as good as the open source one?
Go to hell Anthropic, really..
@nullStack65 commented on GitHub (Jan 9, 2026):
lol for sure. but for them to care that much and roll it out that quickly is still wild to me. was expecting at least the rest of the day to work fine. But i guess they are actively monitoring it which shows its important enough to them for them to do so.
@blost-fyi commented on GitHub (Jan 9, 2026):
And an army of Claude Code instances doubling down on the patches... a heads up or an email explaining the changes would have been nice but I guess that's why the gave us 2x credits on christmas
@nullStack65 commented on GitHub (Jan 9, 2026):
anyone thats using Anthropic and reading this should cancel their subscription. even if you still plan on using it through claude code, you will have the rest of your payment period to continue using your plan. once it gets close to ending or ends, you can always resubscribe. its about sending the message to anthropic.
@paulp-o commented on GitHub (Jan 9, 2026):
If so, I just want to assert Anthropic guys that this is a worst move that you would make as an AI comany and effectively admitting you're destined of not being competitive starting in this year.
I get that they're essentially scared that when they lose lead to another AI model, people would just switch out Claude to something else and stop paying. so you'd want to lock in people.
But this move would just make people decide such switch earlier, which is NOW.
@shawnyeager commented on GitHub (Jan 9, 2026):
FWIW: https://github.com/anthropics/claude-code/issues/17118
@nullStack65 commented on GitHub (Jan 9, 2026):
everyone should comment in this claude-code thread too!
@ten3roberts commented on GitHub (Jan 9, 2026):
Thank you ❤️
Agree, this is inconvenient, and not nice.
We pay for the usage for a reason, to use Claude for coding, and shutting out competitors this way only hurts, as it reduces innovation and stifling expirementation that can be learnt, so it is a loss-loss.
OpenCode has a serious UX improvement over ClaudeCode, and while using both, OpenCode (especially with my neovim integration) simply beats it by miles, and is much easier to configure, with better and much faster calls and UI overall.
@nullStack65 commented on GitHub (Jan 9, 2026):
If only ram prices weren't crazy, id just go full local :(
@kiyoakii commented on GitHub (Jan 9, 2026):
canceled my Claude max subscription. No opencode, no subscription.
@wolfeweeks commented on GitHub (Jan 9, 2026):
Just cancelled my claude max subscription. I hope they are reading this
@Davincible commented on GitHub (Jan 9, 2026):
The funny thing is that they are doing this while CC is more broken than ever. Its literally not even a viable alternative. Makes every request double (with and without streaming) and a shit ton of background activity. If CC was actually good to use we could consider but its absolute vibe coded trash
@kzhrv commented on GitHub (Jan 9, 2026):
I cancelled as well. Cheeky buggers.
edit: Max 20x.
@dragomirweb commented on GitHub (Jan 9, 2026):
Just cancelled my claude max subscription as well (was using around 5-10% of it anyway). I think the majority of us are using it normaly . Consumer hardware prices are now insane, they want us bound to the cloud
@43034r commented on GitHub (Jan 9, 2026):
Nobody knows how to get a refund for the remaining months of the subscription or their support email?
@stephengolub commented on GitHub (Jan 9, 2026):
Anybody writing a plugin to make the claude code cli work like any other model inside opencode?
@a-dmx commented on GitHub (Jan 9, 2026):
someone did, stopped working within few hours :(
@rdvo commented on GitHub (Jan 9, 2026):
Yea if someone just wraps the Claude code CLI jsonl output mode then treats that as the harness in opencode for any model from Anthropic provider could be viable, will be kinda annoying to do tho
@co-l commented on GitHub (Jan 9, 2026):
How could we manage the context to make this work? I'm happy to contribute to this, but this is where I don't see how we can overcome this.
@spiffytech commented on GitHub (Jan 9, 2026):
Kilo Code does this but it's not reliable. Claude Code runs its own business logic over the model inputs/outputs and often swallows the tool calls, especially with Haiku.
@rdvo commented on GitHub (Jan 9, 2026):
Would have to pull the logs from Claude code into the session logs that open code stores locally etc
Could be done just need to parse all the output from Claude code headless and transform it to fit what open code expects then basically sidecar it into the main app so the frontend just thinks it's coming from the Claude code harness
@dburkland commented on GitHub (Jan 9, 2026):
Not a great way to start the morning, guess I'm cancelling my subscription (AGAIN)
@43034r commented on GitHub (Jan 9, 2026):
@matty-cakes commented on GitHub (Jan 9, 2026):
He make uh duh proxy 🇮🇹
@CastAIPhil commented on GitHub (Jan 9, 2026):
If you paid with a credit card you could dispute the charges due to the service not being functional during the period of the subscription.
@henrythor commented on GitHub (Jan 9, 2026):
Cancelled my team seat for Claude, I expect other coworkers to follow suit. Using Opencode Zen now
@apereiracvo commented on GitHub (Jan 9, 2026):
Can't believe I was just installing OC today to switch from CC and this happens :'()
@remy90 commented on GitHub (Jan 9, 2026):
Cancelled my max sub.
@willian commented on GitHub (Jan 9, 2026):
How are you using Zen? Are you using it with Claude API or another provider?
@henrythor commented on GitHub (Jan 9, 2026):
https://opencode.ai/docs/zen/
@daut commented on GitHub (Jan 9, 2026):
@UltraInstinct0x commented on GitHub (Jan 9, 2026):
I love Apple's Refund Policy.
@a-dmx commented on GitHub (Jan 9, 2026):
But there's no subscription with renewable limits, only crude token billing?
@a-dmx commented on GitHub (Jan 9, 2026):
@LicketySpliket commented on GitHub (Jan 9, 2026):
Another quick fix is to title case
idin tool calls:You can patch your tool.ts to automatically convert all
idto title case.@JoshuaDietz commented on GitHub (Jan 9, 2026):
I requested a refund over their chatbot, took 2 minutes, they already confirmed the refund.
Go to https://claude.ai/new, click on your profile in the bottom left, click "request help", chat with the bot and request a refund (I used the refund reason "other").
Not sure if maybe it only worked for me because I've made the subscription less than 24 hours ago. Wishing everyone luck that the refund works
@kommen commented on GitHub (Jan 9, 2026):
pi-agent is working it around (for now) like this: https://github.com/badlogic/pi-mono/pull/594/changes
@mathisto commented on GitHub (Jan 9, 2026):
Thanks @JoshuaDietz
I did the same. I hope Anthropic will consider engaging vs gimping us.
@ariasfx commented on GitHub (Jan 9, 2026):
Did the same @JoshuaDietz. Refund request of my week-old account went through surprisingly fast. CC was a good tool while it lasted, but I'd rather keep my workflow and bring inferior models into the mix.
@amanhigh commented on GitHub (Jan 9, 2026):
Subscription Cancelled and Voted here on Claude Code Issue.
@paulp-o commented on GitHub (Jan 9, 2026):
can you please elaborate?
@UltraInstinct0x commented on GitHub (Jan 9, 2026):
Steps:
Cancel your subscription via the iOS app (Settings → Apple ID → Subscriptions)
Go to reportaproblem.apple.com
Select "Request a refund" and then "Other"
Select the Claude subscription charge
Submit a refund request using the template below
Template:
@marco-kretz commented on GitHub (Jan 9, 2026):
Unsubbed Max too. At least I got the full 90€ back.
@cdnsteve commented on GitHub (Jan 9, 2026):
Has anyone heard back officially from the @claude team on this? Feel like the unsubs are not really justified until there is an official response? Teams are moving fast everywhere, lets give them more than 15 hours? 👍
@CastAIPhil commented on GitHub (Jan 9, 2026):
It seems the fact they deliberately patch defeated the Opencode workaround that was created after their first change is a pretty loud message. The silence since then is deafening while they figure out if 1. damage control is warranted, the people complaining here might be such a small chunk of revenue they don't care. 2. How to message damage control if it is warranted.
The issue posted to Anthropic's GH has a few hundred votes, even if you call it 1k people complaining that's only around $200k/mo of revenue, $2.4Million ARR, that's not even noticeable considering they are a $9Billion/ARR company...
@khallmark commented on GitHub (Jan 9, 2026):
@cdnsteve
Perhaps they should move faster to handle this PR nightmare.
@chrissm79 commented on GitHub (Jan 9, 2026):
I see some other comments regarding ACP and I'm ignorant to what the differences are compared to using the CC API directly, but ACP is how Zed is able to use Claude Code in their product. OpenCode supports ACP itself so I'm sure the devs are pretty well versed on what the capabilities are. I just wonder what the limitations are that would prevent making a move like this?
@cdnsteve commented on GitHub (Jan 9, 2026):
Hmm - have reference to the first occurrence where this happened? Is this is the second time that definitely feels like a pattern...
I'm building automation that is highly integrated to the Claude ecosystem as well for my Sugar project. If Claude is taking more of a defensive stance on protecting their CLI space and tooling I have concerns.
@JoshuaDietz commented on GitHub (Jan 9, 2026):
If a tool that you pay hundreds of euros for every month suddenly stops working without any pre-notice, I think an unsub is completely justified, even if in the end it turns out that all of it was just an accident (which I don't think, especially since the workaround also stopped working within a few hours). If you don't cancel you risk to pay for time that you can not use and you also risk that they think you accept that kind of behavior and that level of unreliability.
@duaneking commented on GitHub (Jan 9, 2026):
So from the sound of everything I've been able to find, it just feels like maybe Anthropic had a simple security bug that they've since patched in the API in that previously Oauth2 token validation on the API was incorrectly not asserting account types correctly after validating that it was valid for an account of some kind, and that has since been fixed, So it now checks that you have an account but also checks that you have a specific type of account that is allowed to use the API.
If I understand the change correctly (tell me if I am wrong, please, I don't want to have the wrong idea about all of this), after the changes you are now all up in arms about, it now asserts that you have the correct kind of account to be allowed to access the API.. and as a result now People are angry because they're no longer allowed to get $800+ dollars worth of extra API access every month on a subscription that only costs them $100? Because I saw posts online from people that were claiming to run CC pro for $20/month and then running up bills for thousands of dollars of API usage.
What am I missing? If I'm not missing anything then what is actually wrong about this? Because it seems to me like Anthropic is actually acting really good here and letting you guys off of the hook instead of sending you to jail like they could. So it really seems to me like they're being nice to you, as somebody who wasn't using this backdoor because I felt it was unethical.
Because previously, many of you you were paying for a $20-$200 subscription and then using $1,000+worth of tokens, if some of the stuff I've seen posted online is true. That simply wasn't sustainable, cant be for any company, any organization, and they were forced to do this to survive because you were abusing them before.
We as a community need to stick together and hold ourselves ethically accountable, and that's against what most of you guys are doing... because you're all calling yourself out as somebody who was abusing the API before, which I must remind you is technically illegal under the American based Computer Fraud and Abuse Act, so if they have records of you going through the API and abusing it, then they have at their discretion, the ability to send you to jail for many years under current federal law.
So maybe you guys should just be easier on them, because right now they're being EXTREMLY nice to you by simply forcing you to write your code yourself by denying you access , Instead of taking back the pound of flesh that you stole from them from excessive API usage for an account that you knew wasn't supposed to give it.
Edit: Hacker News Sent Me.. I suspect the traffic to this thread will get higher.
@brendandebeasi commented on GitHub (Jan 9, 2026):
@duaneking Yes, but also what do you expect from the OSS community in general :P FWIW I see both sides here. I'd be happy to pay 1-2x more for my max20x sub because of how much I am able to get done with it if it means OpenCode (and others) can auth subscription users.
@andrhlt commented on GitHub (Jan 9, 2026):
If this is the issue then they will continue to lose money if everyone migrates to claude code; this is insinuating that the abuse is the usage limits and not the allowed frontend.
Yes they can do whatever they want, they're just going to lose a lot of dev business from this, who are the customers paying $200/mo each.
@duaneking commented on GitHub (Jan 9, 2026):
That's my key point: if you want the access then pay for it like everyone else. If you bought a Claude code subscription and you got an API Key specific to that subscription to that agent, it is not reasonable to expect that you can just pass that API key around like a bottle at a frat party through every open port you can find.
Every person that was massively abusing this for multiple months is at legal risk, and they need to understand that before they complain too loudly. Anthropic was being nice by simply denying their access; they could have sent them an invoice, or simply filed charges for the amount lost under the Computer Fraud and Abuse Act.
Anthropic is being extremely chill about this.
@crottolo commented on GitHub (Jan 9, 2026):
edit ~/.zshrc adapt to you
@UltraInstinct0x commented on GitHub (Jan 9, 2026):
you don't know what you are talking about. "legal risk" my ass. lol
@UltraInstinct0x commented on GitHub (Jan 9, 2026):
why would people pay for a rigged 'product' that is shoved down thru their throats?
@elad12390 commented on GitHub (Jan 9, 2026):
@duaneking Your legal analysis is fundamentally incorrect and spreading this kind of misinformation helps no one.
Re: Computer Fraud and Abuse Act
The CFAA requires either unauthorized access or exceeding authorized access to a protected computer. Users here:
Using a different client to access a service you're paying for is not "unauthorized access." By your logic, using Firefox instead of Chrome to access Gmail would be a federal crime.
Re: "Stealing" API usage
If I pay for a subscription with 5x rate limits and use 3x of that capacity, I haven't stolen anything regardless of which interface I used. The whole point of a subscription model is you pay for a defined amount of usage.
Re: "$1000+ of API usage on $20 subscriptions"
This is the entire value proposition of subscription models vs pay-per-token. Anthropic chose to offer these plans. If they're unprofitable, that's a business model problem, not users "abusing" anything.
The Actual Situation
This is a TOS/contract issue at most. Anthropic can:
They cannot retroactively claim users committed federal crimes for using a paid service with a different client.
Bottom Line
Stop fear-mongering about "jail time" and "legal risk." Users are rightfully frustrated that a service they paid for suddenly stopped working with their preferred tools, with no advance notice. That's a legitimate complaint, not a confession to federal crimes.
@JoshuaDietz commented on GitHub (Jan 9, 2026):
@duaneking I think the technical part of your explanation does not make any sense. If they were not able to correctly identify the subscription type before, then how is it possible that they correctly enforced and displayed their usage limits when Opencode was used? Obviously the requests were counted against the subscription.
Your explanation that people get thousands of dollars of "value" and that it's clear that was not sustainable also does not make any sense because when using Claude Code (for which they have to pay the same amount of money as the Opencode users are paying) they can still get these thousands of dollars of "value". The reason why I quote value is because you just use their API prices to determine the "value" but the truth is that they also have huge cost advantages when having subscribers who pay up front no matter how much they use, who do not enforce SLAs from you and where you can randomly change limits if it fits you. So just taking the token price to determine the "value" of a Claude Code subscription is ridiculous.
And regarding your legal explanation I will not say more than that after reading it I'm pretty you're not a lawyer.
And regarding your problem with understanding the outrage: Anthropic has accepted that kind of usage for a long time now. It's completely fine if they want to change the rules. But if you want paying customers not to get upset you should maybe announce the change before instead of just cutting people off in the middle of their work.
@Tyler-widd commented on GitHub (Jan 9, 2026):
Same
@0xPT commented on GitHub (Jan 9, 2026):
@duaneking commented on GitHub (Jan 9, 2026):
You are confused.
The ability to track the number of web requests et cetera is completely different from login.
These are different concerns by design especially in code that's written to be DRY and SOLID; Cross domain concerns like this are typically the ones that need to be worked on explicitly. Accounts and login are different domains In most systems because that helps with security validation.
False. Anybody that can do math can see that removing more money from a bank account than is added is not sustainable.
False. When open code is using those models it's through a different mechanism and thus a different line of business for anthropic so the numbers don't match. This is just basic business studies knowledge, But if you're an engineer it makes sense that you wouldn't understand stuff normally only known by MBA's.
And they should be paying for it, Not buying an account that's artificially cheap as a faint and then going around and trying to trick or get extra value out of the account that is explicitly not intended in the agreement they consented to.
I agree that token prices are ridiculous and artificially inflated. What you're arguing against is their pricing model. I'm against per token pricing as well. But it's the reality that we live in. It will only change when the hardware is cheap enough and cannot be used as a gate to keep everyone out as part of their business plan of maintaining a blue sea business environment by using Artificially unavailable hardware to artificially restrict access. That was because they bought out all the silicone and created the current RAM price spikes as well, So it's really just about them limiting hardware production to artificially spike software prices for AI. That is a separate issue.
I am not a lawyer. But I have taken a few classes on law and I know what moral hazard is, as well as what a tort is (I actually enjoyed my tort classes) so I could explain this in more detail if I wanted to... but it's just not worth it to me.
Maybe they didn't know they were being injured? Maybe they didn't know they were being abused? Maybe this was a bug that they weren't aware of until it had to get fixed because a budget thing found it? A victim not telling you to stop - For any reason - doesn't mean it's OK to keep hurting them.
But that's not what's happening here. Paying customers that were following the rules were not impacted by this.
@doodhout commented on GitHub (Jan 9, 2026):
@duaneking They are a multibillion dollar valued company. They could at least spend some of those dollars on PR and try not offending people by sneakily banning the use of third-party tools like they just did without any sign or warning.
You might have all your MBA prowess and classes on law, but you're lacking basic empathy.
@antonpetrovwork commented on GitHub (Jan 9, 2026):
Thanks!
I just asked Claude Code to add it to my opencode config.
And it works!
@duaneking commented on GitHub (Jan 9, 2026):
I believe that you the one lacking basic empathy; If anything I see myself as being somewhat over-empathetic here. And I never said I had an MBA. Just that I'm trying to understand this from all sides... out of empathy. And that leads me to believe that Anthropic is being extremely chill here when they otherwise don't have to be.
@aymennasri commented on GitHub (Jan 9, 2026):
Can people recommend alternatives with their specific use cases? It would be great to guide people to the best direct competitors in order to support them and create a more competitive spirit where losing customers is actually important.
@a-dmx commented on GitHub (Jan 9, 2026):
Anyways, it's completely legal to use their $200 subscription $1000 worth of token just by using their buggy claude-code cli? Please be serious about things here. What they did was just cutting competetive cli out of spite it delivers better features and has better ecosystem. By the way, I'm Polish, there's a nice Polish saying "Nie strasz, nie strasz.." :)
@bimawa commented on GitHub (Jan 9, 2026):
Guys after update on 1.1.9 by
curl -fsSL https://opencode.ai/install | bashlooks like issue disappear?
@JoshuaDietz commented on GitHub (Jan 9, 2026):
@aymennasri
Pretty happy with Minimax 2.1 and GLM 4.7. Quality a still a bit lower than the Anthropic Models, but not that far off and since the models are open and cheap to run no one can take them away because you can just switch providers. And their subscriptions are waaayy cheaper than Anthropics.
@duaneking commented on GitHub (Jan 9, 2026):
That's a misrepresentation of the facts; The only reason people were using their Claude Code Specific API key outside of Claude code was to get around those limits. Use open code if you want, but use an API key that isn't artificially constrained to a lower price for you at the expense of a higher price that you know someone else is going to have to pay if you do not.
Have some empathy, people. ;)
@H0llyW00dzZ commented on GitHub (Jan 9, 2026):
yall need to switch to an alternative AI provider
@iamthemediagit commented on GitHub (Jan 9, 2026):
Which one do you recommend?
Updated for max a few days ago ;(
@a-dmx commented on GitHub (Jan 9, 2026):
as
That sounds as complete manipulation. So you say using cli that lets you utilize your limit in more effective way, the limit you LEGALLY paid for, is a kind of lack of empathy. I say they knew what they do while selling people those subscriptions (expected that people won't use it much) and now they are unhappy that people started using the service to the limit of allowance. The answer is - do not offer subscription with limits so then you don't have to blame people, so it's lack of empathy but on the other side. :)
@H0llyW00dzZ commented on GitHub (Jan 9, 2026):
If you're looking for a cheap one, there are a lot of options.
For example: Grok, GLM, and MiniMax
@deveworld commented on GitHub (Jan 9, 2026):
@duaneking The business logic is fine. Subscription = money + data, API = just money. We get it (if they'd admit it)
But, the real problem is Anthropic framing it as "telemetry helps debugging" when they have server logs, or "we want third-party harnesses" while banning them in ToS.
If they just said "subscriptions require our client for data collection, use API otherwise", that's honest and defensible. The PR-speak and contradictions are what's frustrating, not the policy itself.
@duaneking commented on GitHub (Jan 9, 2026):
I'm just thankful I've seen so many LLM powered responses talking about empathy from what are clearly accounts held by non-technical people who have never done anything without an LLM holding their hand. It gives me hope that someday robots can actually perform that as a service as well.
From my perspective, the people that abused the API key and intentionally set up their stuff knowing that they were going to go over their limit to intentionally commit fraud by abusing the open code platform to throw the entire open code community under the bus are the problem here, because they did so simply so they could get free token usage and did not care that by doing that they were making the opencode community look like it was adversarial to the model providers that it depends on.
My honest guess guess is a lot of you are going to get banned from using Anthropic models if you haven't been already. Most of you have no empathy and that's why you're not thinking about how this impacts the relationship with opencode and other providers, or how it could limit the ability to gain access to models or the goodwill to allow opencode to simply have a provider for a service in the future with it being a problem that harms Access for everybody else down the line.
In simple english, The fact that Anthropic even had to do this severely hurts the reputation of the opencode community and makes it seem more darknet friendly than it should be. The opencode leadership needs to dramatically sway away from this, be public about the problem, and actively support what Anthropic did or it will lose legitimacy with every other provider.
This is one of the reasons why you should all be thinking about empathy and trying to be a good and collaborative player in the ecosystem instead of forcing things or trying to extract value forcefully. You are critically dependent on API access to access their models and this time all they did was cut off one client they didn't remove your entire account like they could have.
Like I said, Anthropic is being very chill about this and you should be appreciative and empathetic of that.
It's easy to ask other people to be empathetic when you're not the one being harmed, But I challenge you all to be more empathetic when you're the one losing out, And I challenge you to understand that if this makes opencode adversarial with anthropic, it could create bad blood with other providers and that's not what you want, either. Yes, it's open source, and open source can be good, but it needs to be maintained legitimacy, in order to maintain itself, because if it becomes this rogue software project that attempts to extract free resources from API's as a dark client (as is currently being claimed by some of you) when it's not allowed to be, then it will just be declared a hacking tool and deleted by GitHub, and at that point Anthropic will stop being so chill.
Every single one of you that's trying to get past the security that anthropic has put up is actively putting the open source community and this project at risk, and need to stop.
I don't think anybody wants Anthropic to show their teeth here; It's not like they don't know who owns the API keys that are being billed.
Just accept that this was a security hole that has since been fixed, and move on with your life, is my greatest advice here, and that is why I'm going to be muting this thread.
Because I know a lot of you are just angry that your toy was taken away, and you're too busy having a tantrum to think about this rationally or logically, so you're going to downvote, you're going to insult, your going to let your emotions control you irrationally, your going to either misunderstand or just flat out going to misrepresent the facts that you don't like or cant accept, you're going to do all those things. Most of them have already happened for many of you. Some of you are already at the point where you've had your panic attack and you've broken down and now you're feeling tired and fatigued because of the energy it took out of you. Many of you have already tried to psychologically manipulate others into agreeing with you because in your mind that makes you feel safer to be around people who agree with you, and it's uncomfortable to have other people have different facts or different data or different perspectives... but I assure you, interacting with other people that have different perspectives makes you a better engineer.
@Linkk93 commented on GitHub (Jan 9, 2026):
wtf is that wall of text? I just want to keep opus in opencode lmao
@Srivathsav-max commented on GitHub (Jan 9, 2026):
seems working now with new 1.1.9 version
@enesahn commented on GitHub (Jan 9, 2026):
Thanks! It works
@humblecoder commented on GitHub (Jan 9, 2026):
...
Perhaps I misunderstand the intent of this post, but it seems to paint the community with an incredibly broad brush while ignoring a massive segment of the user base: those of us who are paying Anthropic customers.
I have been a developer since the late 90s, and I’ve seen the industry evolve through several paradigm shifts. Today, tools like Claude are transformative because they allow me to operate as an architect and orchestrator rather than being bogged down strictly with the syntax of every line of code. To maintain that level of high-level orchestration, I've come to enjoy a flexible interface that fits my workflow . . . which is exactly why I use OpenCode.
I pay $100+ a month for a Max-tier subscription. I am not trying to "extract free value" or "commit fraud." I am trying to use the compute I pay for through a tool that supports my professional output. The idea that using a third-party client is somehow "adversarial" or "darknet-adjacent" is a bizarre take that fundamentally mischaracterizes why many of us are here.
Again, apologies if I completely misunderstand your intent, but, at an initial read-through, I completely disagree.
@ramtinJ95 commented on GitHub (Jan 9, 2026):
man anthropic should be appreciative and empathetic to us for not raging harder. They have stolen everything their model is built on. They should appreciate society and all users not demanding governments to bring them in line. Now they have the audacity to stop paying users from using a different client.... Take that wall of text down and stop embarrassing yourself. Telling us to be appreciative and empathetic, the things i want to say to you, but lets stay civil.
@bitgineer commented on GitHub (Jan 9, 2026):
confirm.
@ClaudiuBogdan commented on GitHub (Jan 9, 2026):
It definitely feels like losing a fun toy. I was enjoying using the Max subscription with OpenCode. But now that it is gone, I'm considering the subscription from Zen. We should support the development of OpenCode in some way.
@a-dmx commented on GitHub (Jan 9, 2026):
Are you sure anyone who tries that isn't banned? (on the other hand, who cares)
@arthur404dev commented on GitHub (Jan 9, 2026):
Opus 4.5 from antigravity's sub works like a charm btw, yielding better results than I was getting directly from anthropic
@ChristDev commented on GitHub (Jan 9, 2026):
Any recommendations for using another provider that works with the Opus model (with the same context)?
@bitgineer commented on GitHub (Jan 9, 2026):
Can confirm this is working! Currently on Opus 4.5 latest using the opencode-anthropic-auth plugin.
edit: (sent via opencode)
@bitgineer commented on GitHub (Jan 9, 2026):
I'd recommend using the anti-gravity uh plugin. Setting up multiple Google accounts if you have 'em. I currently have three set up, and I rarely hit my limits. You can use all the Opus models, along with the Gemini models.
@huynle commented on GitHub (Jan 9, 2026):
but it's not a TUI. Opencode is awesome at this! and i can confirm the opencode-anthropic-auth plugin is working also.
@bitgineer commented on GitHub (Jan 9, 2026):
I don't know if it was misunderstood, but you could use anti-gravity's models within opencode using
antigravity Opencode Plugin
@arthur404dev commented on GitHub (Jan 9, 2026):
Yeah, it's a plugin for opencode:
@huynle commented on GitHub (Jan 9, 2026):
Totally did not see that coming! Opencode is even better now.
@arthur404dev commented on GitHub (Jan 9, 2026):
TBH google's AI ultra is a way better package and it gives you better specialist models (gemini 3 pro for any visual task).
Dunno how much google will be offering claude models for in antigravity, but seeing that they have way more money than Anthropic to burn maybe they stick with it.
@a-dmx commented on GitHub (Jan 9, 2026):
Yeah I'm trying out that just now. 😃 Btw. here you can see their usage limit https://antigravity.google/docs/plans.
@Tetrahedrite commented on GitHub (Jan 9, 2026):
Just tried it on 1.1.10 and it’s been patched. It feels like a total cat-and-mouse game. I wonder if they have any defenses left.
@nullStack65 commented on GitHub (Jan 9, 2026):
At least Codex oauth support has been merged into opencode 🎉
https://github.com/anomalyco/opencode/pull/7537
@ekkyarmandi commented on GitHub (Jan 9, 2026):
Upgrading my opencode to v1.1.10 resolved the anthropic claude auth issue
@adiled commented on GitHub (Jan 10, 2026):
This has served as a decent opportunity to explore other models, and that wouldn't have been possible without opencode's exceptionally brilliant make and form that has captured multiple developer personas. This is a productive lock-in exemplified.
Model lock-ins are unlockable, anthropic is catching up to exactly that as global model wars commence. UI lock-in is hardly unlockable.
The TOS, violations, CC the subscription, CC the CLI, suit and ties is mere froth. LLM scale like any innovative industry is a tribal environment, where these open-closed federated-proprietary frictions play to its growth.
The end-to-end lock-in is a 20th century reality, but 21st century fantasy. It's fair play for anthropic to position the brand as a fantasy and still survive, so the move overall is self-fulfilling. Such is the nature of tribal period, it's good to see the OC community by large embraces it, that's demonstration of a solid community.
@jimmy3574 commented on GitHub (Jan 10, 2026):
CC auth is working fine for me today (ran command, obtained auth token, all fine) however I'm getting this on all the models..
@deveworld commented on GitHub (Jan 10, 2026):
I think it's about context problem, not oauth.
Opencode doesn't contain context about the model and version when send llm requests.
I confirmed with Cluade Developer Platform (API).
@aymennasri commented on GitHub (Jan 10, 2026):
Just a heads up, they actually collect your data/prompts by default :)
"Interactions are collected and used in accordance with this Agreement and the Privacy Policy. Google employees and contractors may access, view, review and use Interactions. If you don't want your Interactions used in this way, navigate to settings to change your preference on how such data is used."
Source
@ten3roberts commented on GitHub (Jan 10, 2026):
Thank you for all the brilliant and lovely minds in this thread, as well as all of opencode (the questions feature is the only feature Claude has had that I've missed from Opencode, but now that is in, and even more amazing and intuitive than in Claude)
What has been your experience with other models/providers?
I.e; which other models, like the Gemini or GPT family would you recommend as alternatives that are decent?
GLM 4.7 is quite good, and exceptional for lighter work, due to its cost, and you can also self-host these if you really want to (having many tools in your tool box is always a good idea)
@cryptobetEU commented on GitHub (Jan 10, 2026):
how you work with codex ? if I use codex it's only planning and talking and thinking but not even ONE fucking change
@huynle commented on GitHub (Jan 10, 2026):
opus-4.5 for sure for development tasks. But I have opencode components that allow the model to do what it needs on my labs and complete access to all my network to fix any issue, and it does so most of the time one-shot. I haven't worked with other models enough to "trust" it.
@lozanobosch commented on GitHub (Jan 10, 2026):
Upgrading OpenCode to v1.1.12 has resolved the Anthropic Claude authentication issue, at least for now.
@frntn commented on GitHub (Jan 10, 2026):
I see people telling an upgrade may fix the auth issue but that doesn't seems to be an auth issue but a ban/unban on their side trying to figure out what they consider a fair setup :
https://x.com/trq212/status/2009689809875591565
@the-vampiire commented on GitHub (Jan 10, 2026):
ya i'm weary of it now that they are making it obvious that it's a ToS violation when authenticating. it may work, but they can easily ban you with no opportunity for recovery of refund.
it's clear that the telemetry data is used for more than debugging and support. they want it for training. that makes sense considering how deeply they subsidize the plans. for that reason it's doubtful they will be allowing OC to continue using it.
i'll be watching to see if they start banning again but in the mean time i'm not risking it.
@cryptobetEU commented on GitHub (Jan 10, 2026):
perhaps but I cannot use opus it's all models but not opus
@diwu-sf commented on GitHub (Jan 10, 2026):
So what's the current verdict? Even if the latest version still works, if we get our Claude account banned for ToS violation, it's still unusable, and I'd rather NOT even have the option to "connect anthropic" if that eventually leads to an account ban.
Can we get an official statement on whether this will cause account bans or not?
@michaelnew commented on GitHub (Jan 10, 2026):
What a line. Cancelled my Max plan today.
@joshribakoff commented on GitHub (Jan 10, 2026):
Anthropic account ban?! Don’t threaten us with a good time! 🪦 wont anyone here show sympathy to the multi billion dollar company implicated in lawsuits for doing the same?
—-
To:
Support@Anthropic.com
Message:
To Whom It May Concern at Anthropic,
I am writing to express my serious frustration and disappointment regarding your recent actions warning users against using alternative clients to access Claude.
Let me be direct: the reason users seek out alternative clients is because your own official client has significant usability issues and, from what I can observe, appears to be actively degrading in quality. Rather than addressing these problems, you are choosing to penalize users who are simply trying to get value from a service they are paying for.
This approach is unacceptable. When I subscribed, I entered into an agreement to access Claude’s capabilities. If your official interface is inadequate and you simultaneously prevent me from using alternatives that would allow me to actually use what I’m paying for, you are effectively interfering with my ability to receive the service I contracted for. I consider this a potential breach of our agreement.
I want to make my position clear:
1. If you continue to obstruct users from accessing the service through functional means while failing to provide a usable official client, I am prepared to file a credit card dispute on the grounds that I am not receiving the service as reasonably expected.
2. I am requesting that you clarify Anthropic’s official position on this matter so I can make an informed decision about whether to continue my subscription.
I would appreciate a prompt response addressing these concerns.
@bchewy commented on GitHub (Jan 10, 2026):
+1
@osirishorus commented on GitHub (Jan 10, 2026):
I got it working by proxying directly through claude code itself. It's not as fast but seems to be working good so far.
@execute008 commented on GitHub (Jan 10, 2026):
this fixes the problem @osirishorus
~/.config/opencode/opencode.jsonc
{
"$schema": "https://opencode.ai/config.json",
"autoupdate": true,
"plugin": [
"opencode-anthropic-auth@0.0.8",
],
}
@isomoes commented on GitHub (Jan 10, 2026):
it fixed in v1.1.12, see https://github.com/anomalyco/opencode/commit/de286b08f6b4955af4d23c217232fbf3d26f756b & https://github.com/anomalyco/opencode-anthropic-auth/commit/499ec92cdab93533a833f5f6994b6fd1faced583
@cryptobetEU commented on GitHub (Jan 11, 2026):
Does opus work with this ? Or does it still use/call claude sonnet ?
@iamthemediagit commented on GitHub (Jan 11, 2026):
Opus 4.5 working
@cryptobetEU commented on GitHub (Jan 11, 2026):
Did you ask/verify? Because i am only getting sonnet 4 when i ask (or even lower)
@iamthemediagit commented on GitHub (Jan 11, 2026):
yes i did :)
@cryptobetEU commented on GitHub (Jan 11, 2026):
This is what you did ?
1. Rename all tools
LC_ALL=C sed -i ''
-e 's/Tool2.define("bash"/Tool2.define("bas_"/g'
-e 's/Tool2.define("read"/Tool2.define("rea_"/g'
-e 's/Tool2.define("edit"/Tool2.define("edi_"/g'
-e 's/Tool2.define("glob"/Tool2.define("glo_"/g'
-e 's/Tool2.define("grep"/Tool2.define("gre_"/g'
-e 's/Tool2.define("task"/Tool2.define("tas_"/g'
-e 's/Tool2.define("write"/Tool2.define("writ_"/g'
-e 's/Tool2.define("batch"/Tool2.define("batc_"/g'
-e 's/Tool2.define("patch"/Tool2.define("patc_"/g'
-e 's/Tool2.define("question"/Tool2.define("questio_"/g'
-e 's/Tool2.define("todowrite"/Tool2.define("todowrit_"/g'
-e 's/Tool2.define("todoread"/Tool2.define("todorea_"/g'
-e 's/Tool2.define("webfetch"/Tool2.define("webfetc_"/g'
-e 's/Tool2.define("websearch"/Tool2.define("websearc_"/g'
-e 's/Tool2.define("codesearch"/Tool2.define("codesearc_"/g'
-e 's/Tool2.define("skill"/Tool2.define("skil_"/g'
-e 's/Tool2.define("invalid"/Tool2.define("invali_"/g'
-e 's/Tool2.define("lsp"/Tool2.define("ls_"/g'
-e 's/Tool2.define("list"/Tool2.define("lis_"/g'
/opt/homebrew/Cellar/opencode/1.1.8/bin/opencode
2. Re-sign the binary
codesign --force --sign - /opt/homebrew/Cellar/opencode/1.1.8/bin/opencode
@jonathan-purnomo commented on GitHub (Jan 11, 2026):
yes
yes this work for me I got opus
@iamthemediagit commented on GitHub (Jan 11, 2026):
i only brew reinstall and then /connect
I m on osx
@cryptobetEU commented on GitHub (Jan 11, 2026):
Well when I ask which model it is, he cannot tell anymore I will do some planning/working see if sonnet increases or not
@cryptobetEU commented on GitHub (Jan 11, 2026):
@cryptobetEU commented on GitHub (Jan 11, 2026):
Can you share what you made/built ?
@neyb commented on GitHub (Jan 12, 2026):
This video (french) show that the identification is made on the system prompt...
The question is "should a game of cat and mouse be started?".
Also it's contrary to cluf (I believe people should boycott Claude for these cluf but believing that it can work is another topic).
@cryptobetEU commented on GitHub (Jan 12, 2026):
Since no reply I am building one myself will be released later it's a proxy wrapper/forwarder for offical client
@n33pm commented on GitHub (Jan 12, 2026):
That's normal. Claude Code adds it in its system prompt.
So if you remove that and leave everything else, even the Claude Code CLI will respond with Sonnet.
I don't know if it's because Opus doesn't know about himself and it's based on Sonnet, or if they're trying to fool us.
I tested it for the last 2 hours and the usage for Sonnet does not go up.
@cryptobetEU commented on GitHub (Jan 12, 2026):
They are fooling you. I finally seem to get it working let me see how it will work
@osirishorus commented on GitHub (Jan 12, 2026):
I can release it, just need to put it together for release ready first. Should have time later today or tomorrow
@n33pm commented on GitHub (Jan 12, 2026):
If I look at your image, I can see you are routing it through Claude Code CLI, which already has the mentioned system prompt! So it's not proof that it's working or that it's the correct model.
@cryptobetEU commented on GitHub (Jan 12, 2026):
I have it working but doesn't operate as opencode normally does, did you manage to get it operate like opencode normally did ?
@lubikx commented on GitHub (Jan 12, 2026):
I've cancelled my Claude subscription. There are different providers. Show that the companies will pay for being hostile. Money and how it is spent are two of the last things we can still control.
@skhaz commented on GitHub (Jan 12, 2026):
The problem is only in Claude? Other companies allows?
@mxmzb commented on GitHub (Jan 13, 2026):
@Naomarik Genuinely curious and would love to learn: How exactly do your workflows look like that they become so unusable with CC, or rather how exactly does OpenCode enable them?
@Naomarik commented on GitHub (Jan 13, 2026):
@mxmzb
Several things. I've iteratively developed a "workflow" for specifications, which I consider to be major features that builds up to creating N number of task files that are orchestrated by a main agent. These are just markdown files I've been able to gradually steer into producing results I really like. This isn't something I've cloned off other people or some ralph wiggums variant, just me encoding my will on how I'd like things built given the constraints of using LLMs effectively into markdown files and repeatedly using it to build features over time. That has slowly got me building extremely specific features that can take a full hour for Opus 4.5 to build.
I also am not completely blind as to what the LLMs are working on. Opencode makes it extremely easy to see what's going on, so I can halt the process, or undo, and decide to edit my prompt or markdown files. It has taught me, just due to the fact that it's always present, that the context window and the kinds of tasks I'm working on let me decide on what gets delegated to subagents, when to clear, when to compact, or when to keep pushing even if I'm 75% full.
I've used Claude Code in the past heavily to create a PWA I host on Cloudflare pages that is pure JS no dependencies, and I had to interrupt it a lot. I spent a full week with that, and during that time it did not teach me much about how to be more effective. I honestly kind of hated myself at the end of it. Opencode makes you better naturally because it shows you things that actually matter, and you can see way more on the screen about what it's doing.
If Opencode is like having a large crisp 4k monitor, Claude Code in comparison is like using an old Nokia Phone to read text messages. I know a lot of people just drop their prompt into the TUI and let it rip, but I need a lot more than that.
@MartinVerges commented on GitHub (Jan 14, 2026):
Not the author, but I tried switching back to CC, and things that just work and produce good results in opencode lead to non working output and lots of token wasted in CC to begin with. The configuration structure inside projects and on a userlevel helps as well. Using multiple models with the same tool, for example having a codex reviewing something that sonnet wrote is simply better in opencode than using 20 different tools, just because they don't like their paying customers and force on their CLIs. CC often has bugs where the shell scrolls up/down very fast for a few seconds and lots of other reasons why CC is not even close to be as good as opencode. For me personally, I'm interested to pay for their model, not for the crappy CLI and I never saw their CLI as a mandatory requirement when paying for a usage limit (plan). I rather switch away from paying them money than going back to stone age CC.
@ejj commented on GitHub (Jan 14, 2026):
Seems to be working for me as of 2025-01-14 on Version 1.1.20. I don't see anything in the release notes ... Did anthropic back track? Does it work for anyone else?
@nullStack65 commented on GitHub (Jan 14, 2026):
just broke again 1/14/26 3:36PM Eastern
@enesahn commented on GitHub (Jan 14, 2026):
The cat and mouse game continues
@ejj commented on GitHub (Jan 14, 2026):
Broken again for me as well. I wonder if this was just a hiccup on Anthropic's end.
@itsmylife44 commented on GitHub (Jan 14, 2026):
rip x2
@JuliaBonita commented on GitHub (Jan 14, 2026):
Theo sums up Anthropic's stupidy well here: https://www.youtube.com/watch?v=gh6aFBnwQj4
We know Anthropic is watching this thread. So to them: Keep doing this dictatorial BS and watch how fast you lose market share. Other cheaper models will soon be as good as CC. As soon as that happens, all the goodwill you're destroying now will accelerate your demise.
When that happens, you will be forced to beg daddy Bezos to bail you out. Then you will be trapped with nowhere to go but to the darkest corners of Amazon. No soul. No options. Just lifelong slavery to your corporate overlords. Enjoy your freedom while it lasts.
@camme commented on GitHub (Jan 14, 2026):
Our entire company began using Claude a couple of months ago and we bought Claude Premium (Team) for all developers. But after this past week with this issue, I'm thinking about canceling all subscriptions. Already checking and testing Gemini 3, z.ai, and more to look for alternatives. But more importantly, making sure that we are never dependant on Anthropics clients like CC.
@rickbassham commented on GitHub (Jan 14, 2026):
I'm getting the same, but also getting errors in the Claude Desktop app using CoWork and Code there. Tool naming issues.
@thomastthai commented on GitHub (Jan 14, 2026):
Designing our workflow around a particular company's tool(s) or service(s) is risky and gives the company too much control over us.
@skhaz commented on GitHub (Jan 14, 2026):
If OpenCode can't work with Claude Max, I'll cancel my subscription and use another model.
At that point, AI models are no longer a novelty, it's a commodity.
Claude Code is pure vibe-coded crapware.
@alikinir commented on GitHub (Jan 14, 2026):
What model can you suggest that can perform similar to Opus 4.5 for coding?
@ejj commented on GitHub (Jan 14, 2026):
FWIW in my personal experience ChatGPT 5.2 is basically as good as Opus particularly with higher thinking budgets. Larger context window, some awkward style choices, but it's really a preference thing.
@rcdailey commented on GitHub (Jan 14, 2026):
the choice is unfortunately a $20 or $200 plan though, right? I'm not aware of a $100 plan. I wonder if their $20 version is more generous.
@ejj commented on GitHub (Jan 14, 2026):
You can always use zen, though of course you're taking responsibility for cost management ...
@jetm commented on GitHub (Jan 14, 2026):
API usage will be more costly than using a subscription. It would be nice if Zen OpenCode offered a subscription to use any of those models. But I don't know if that is currently possible. I know there are several solutions out there like OpenRouter with API usage, but there is none to use a subscription allowing you to select any of the well-known current models.
@skhaz commented on GitHub (Jan 14, 2026):
Last time I was using pay per token I ended 50 dolars per day.On 14 Jan 2026, at 19:46, Javier Tia @.***> wrote:jetm left a comment (anomalyco/opencode#7410)
You can always use zen, though of course you're taking responsibility for cost management ...
API usage will be more costly than using a subscription. It would be nice if Zen OpenCode offered a subscription to use any of those models. But I don't know if that is currently possible. I know there are several solutions out there like OpenRouter with API usage, but there is none to use a subscription allowing you to select any of the well-known current models.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>
@jetm commented on GitHub (Jan 14, 2026):
Yes, that has been my experience too.
@NazmiAltun commented on GitHub (Jan 14, 2026):
I started to face this issue again on opencode. F.U Anthropic!
@momomo commented on GitHub (Jan 14, 2026):
Aside from all the complaining ... this can't be impossible to get around can it?
I bet Anthropic will keep adjusting their software to block any new implementations, but mimicking an existing Claude Code installation from my computer to make the calls, can't be impossible, can it?
Whatever the Claude Code application is doing, maybe even refreshing tokens every 1 minute, we should be able to do that too, right? If we start off with a logged in token, it must be the headers or similar that they have introduced some detection mechanism for on their backend, but this should be possible to mimic, no?
Of course, whenever they change the way inevitably something would break until someone again looks at it, but perhaps adding a little snitch network monitor and forcing a claude code installation to be present and snooping on it and sending it to opencode, if they are refreshing tokens.
Of course there are 100's of ways this can be made difficult on their end, but not impossible ...
@westito commented on GitHub (Jan 15, 2026):
@momomo Workaround is literally mimick Claude Coude. Specific headers in query, specific text in system prompt. Specific tool naming. Anthropic always change this a bit, update Claude Code with new changes, but other tools can't follow.
From a business perspective, Anthropic's behavior is understandable. The "Pro/Max" subscription is fundamentally loss-making for the company. As many have pointed out, using the pure API costs significantly more—that's the real price. This is product bundling for them, steering users toward Claude Code and their own services. Subscribers who don't fully utilize their plan essentially subsidize those who use it constantly. Anthropic can afford to do this, but Zen couldn't finance a subscription package the same way. They can only purchase tokens at the same API price as anyone else, and this model only works if there are enough subscribers who don't max out their quota to cover the heavy users—or if you have investors backing you.
Pro tip by the way: you can also use Opus 4.5 in GitHub Copilot. Sure, the context is smaller and you'll hit rate limits sooner, but ChatGPT 5-mini is free. If you set it as a subagent, you can offload a lot of tasks that won't count against your quota. Also worth setting up Sonnet as a custom subagent for specific tasks—makes your quota last longer.
(
@westito commented on GitHub (Jan 15, 2026):
Update to version
1.1.21, it is already fixed!@pranshuchittora commented on GitHub (Jan 15, 2026):
But the older sessions can't be resumed.
/sessions: (@mehow28 commented on GitHub (Jan 15, 2026):
I just upgraded and opened up yesterdays session on claude sonnet 4.5 succesfully, both win11 desktop and linux
@pranshuchittora commented on GitHub (Jan 15, 2026):
Works when Anthropic says “yes.” 🤣
@momomo commented on GitHub (Jan 16, 2026):
Here's a cleaned-up version that keeps your voice and all your points:
Thanks for the tips. I'm still early in my journey with these tools and figuring out the best way to utilize them.
Right now, I spend a lot of time analyzing responses and crafting replies back, which feels inefficient. I'm not certain yet whether I want to move toward more automation, but I can see how using multiple tools strategically would help.
As for GitHub Copilot: if you mean inside VS Code, unfortunately that's not a great fit for me. I'm an IntelliJ user, and the refactoring tools in VS Code and Cursor feel clunky or are missing features I rely on. So for now, I'm primarily using other agents through the browser for feedback.
I noticed your answer was polished with an agent, while mine isn't ( (yet, yes em dashes gave it away while writing my reply and realizing i had dots ... everywhere, but i guess its a good thing now as we don't try to pretend we are always perfect, last one was me typing freely). I was hesitant to use Claude to clean up my reply, worried something might get lost in translation... but let me try.
Oh, its pretty good, but i kind of hate those em dashes just looks so fake when applied to me! So I told Claude to remove them! I wonder how this process can become more automated inside the browser in the future. Fixing texts and dots ... and grammar as we type ... instead of running it through afterwwards and then reeading it back.
@westito commented on GitHub (Jan 16, 2026):
I mean you can login to Copilot and use Copilot subscription in OpenCode, not in IntelliJ/VSCode. It's not polished, I simply translate from my own language. My thought was too long and too complex, and I afraid of can't write it down properly in English. Anyways, I like dashes - often makes the flow of thought more articulated 😄 -, and I use regularly regardless of using model to translate or not.
@momomo commented on GitHub (Jan 19, 2026):
Route opencode through a local Claude instance CLI instead of the API.
Rather than calling Anthropic’s API directly, opencode could communicate only with a user-installed Claude (e.g. via Claude CLI). Prompts, context, and tool output are piped to the local Claude process, and responses are read back from stdout or IPC.
At that point, opencode is no longer an API client — it’s automation layered on top of a user-controlled Claude installation.
Why this is hard to block:
Blocking this would require detecting or limiting automation inside Claude itself, which would break legitimate power-user workflows.
Tradeoffs:
Bottom line:
Once interaction is local, the API enforcement boundary disappears. This pattern is hard to prevent without collateral damage and is likely to persist across agents and models.
@jetm commented on GitHub (Jan 19, 2026):
I am doing a similar approach but using Claude SDK. Code is at https://github.com/jetm/tooling and put a table to compare the pros and cons of using API vs. Claude SDK.
Edit: Adding the link to the table https://github.com/jetm/tooling?tab=readme-ov-file#architecture-claude-sdk-vs-api
@westito commented on GitHub (Jan 19, 2026):
You can't just proxy OpenCode or any other agentic tool through Claude Code CLI. OC has its own toolset and system messages. That's the point which distinguishes OC from CC. So basically its impossible to do that, or if you do it, it will be a CC labeled as OpenCode with no advantage over CC.
@westito commented on GitHub (Jan 19, 2026):
Claude SDK is just a wrapper around HTTP API thats works only with token, it won't solve the SSO problem.
Edit: The Python Claude SDK you pointed out is a CC wrapper - not the raw API - but the problem is the same. You can send user messages as like you use CC, but you CAN'T change built-in tools or system massage that the most important part for a custom agent.
@phil65 commented on GitHub (Jan 19, 2026):
Not exactly true. The SDK exposes options to replace the builtin system prompt, claude codes internal tools can get disabled, and own tools can get injected using an in-process MCP server as a bridge. The "real" issues popping up with that approach are more how claude code sdk is tied to its own storage system.
@westito commented on GitHub (Jan 19, 2026):
I see... true. But I still think it won't allow SSO, because as message say "only for Claude Code" and not "only for Claude SDK". Claude SDK is still a helper lib that wraps Claude API, not the actual product that SSO allowed for. Claude API checks for system message and tool names to authorise Claude Code. If you change any of these, Claude will block even you are using Claude SDK.
@phil65 commented on GitHub (Jan 19, 2026):
The Claude Agent SDK directly uses the Claude code binary, and also uses Claude codes auth.
I have coded exactly that, an OpenCode compatible server which allows running "agent sdks" as well as ACP agents natively while injecting tools to replace the builtin ones. That appraoch wasnt and isnt affected in any way.
@thomastthai commented on GitHub (Jan 25, 2026):
I wrote a simple Go CLI program to use Claude's OAuth with my Max 200 plan. The CLI program can send prompts and get responses including tool use. There isn't anything unique about this CLI program. Why is it not blocked?
@westito commented on GitHub (Jan 25, 2026):
Are you use fully customised system message with "OpenCode" in it? It's funny but Anthropic blocks request when system message contains the "opencode" phrase 😂
@thomastthai commented on GitHub (Jan 25, 2026):
Output
❯ ./tmp/oauth_working_implementation
=== Claude Max OAuth - Working Implementation ===
Based on anthropic-oauth-max-plan CLI
🔐 Starting OAuth flow...
Opening browser to:
https://claude.ai/oauth/authorize?client_id=9d1c250a-...
======================================================================
After authorizing, the page will show a code and state.
Copy them and paste in this format: code#state
Example: abc123xyz...#def456uvw...
Paste code#state here: gJzKzzSUrDl5O...
✅ Authorization code received!
🔄 Exchanging for tokens...
✅ Tokens obtained successfully!
Access Token: sk-ant-oat01-t-fN_...
Refresh Token: sk-ant-ort01-Ln5cA...
Scope: user:inference user:profile
Expires In: 28800 seconds (8 hours)
🧪 Testing token with API call...
📝 Request 1:
Prompt: Say 'OAuth works!' if you receive this.
Response 1: OAuth works!
📝 Request 2:
Prompt: What is the maximum context window for Claude models?
Response 2: The maximum context window varies by Claude model:
The latest Claude models can handle approximately 200,000 tokens in their context window, which is one of the largest available among major AI models. This allows for processing entire books, long documents, or extended conversations in a single interaction.
Note: The actual usable context may be slightly less depending on the API, system prom
📝 Request 3 (WITH TOOLS):
Prompt: List files in the current directory
Tools: Bash, Read (like Claude Code uses)
Response 3 Status: 200
✅ Tool call ALLOWED! Response:
{
"content": [
{
"text": "I'll list the files in the current directory for you.",
"type": "text"
},
{
"id": "toolu_015oY9G2bffHKdAruFVXPVeQ",
"input": {
"command": "ls -la"
},
"name": "Bash",
"type": "tool_use"
}
],
"id": "msg_01RK4Tay8nctq9c5siVbtR8E",
"model": "claude-sonnet-4-5-20250929",
"role": "assistant",
"stop_reason": "tool_use",
"stop_sequence": null,
"type": "message",
"usage": {
"cache_creation": {
"ephemeral_1h_input_tokens": 0,
"ephemeral_5m_input_tokens": 0
},
"cache_creation_input_tokens": 0,
"cache_read_input_tokens": 0,
"input_tokens": 665,
"output_tokens": 67,
"service_tier": "standard"
}
}
🎉 SUCCESS! OAuth authentication working!
✅ Token exchange successful
✅ API authentication successful
✅ Claude Max OAuth tokens work with Anthropic API!
@momomo commented on GitHub (Jan 28, 2026):
@thomastthai
Great job! But I had to ask claude to explain the go code, hopefully its ok, but i thought it might be useful for others that might be working on a solutions for the future.
This Go code implements an OAuth 2.0 authentication flow with PKCE (Proof Key for Code Exchange) to obtain access tokens for the Anthropic API. Here's how it works:
The Authentication Flow
1. PKCE Setup
PKCE is a security extension that prevents authorization code interception attacks.
2. Authorization Request
The code builds a URL to
https://claude.ai/oauth/authorizewith parameters including:org:create_api_key user:profile user:inference— permissions being requestedThe user's browser opens this URL, they log in to Claude, and approve the permissions.
3. Token Exchange
After authorization, the user pastes back a
code#statepair. The code then POSTs tohttps://console.anthropic.com/v1/oauth/tokenwith:This returns access and refresh tokens.
4. API Calls
The tokens are used to call
https://api.anthropic.com/v1/messages:The
anthropic-betaheaders indicate this uses OAuth authentication (rather than API keys) and enables Claude Code features.Key Insight
This appears to reverse-engineer how Claude Code CLI authenticates—using OAuth tokens from a Claude Max subscription rather than requiring separate API credits.
@todiap commented on GitHub (Jan 28, 2026):
is it doing again??? This credential is only authorized for use with Claude Code and cannot be used for other API requests.
@Steffen025 commented on GitHub (Jan 28, 2026):
✅ Workaround confirmed working
Added
modeoverride inopencode.jsonto bypass the pattern matching:Tested with: Anthropic Max Subscription + claude-opus-4-5 and claude-sonnet-4-5
This replaces the system prompt identifier that Anthropic is blocking. Works as of 2026-01-28.
Copy-paste ready: See commit with full opencode.json
Reference: https://github.com/anomalyco/opencode-anthropic-auth/issues/17#issuecomment-3752059576
@skhaz commented on GitHub (Jan 28, 2026):
I canceled my Claude Max subscription, I am using Codex now.
@cryptobetEU commented on GitHub (Jan 28, 2026):
? in the .config directory opencode.json I do not see where to add or put
@thamrx commented on GitHub (Jan 28, 2026):
@cryptobetEU, see https://opencode.ai/docs/modes/#json-configuration
@Steffen025 commented on GitHub (Jan 28, 2026):
@cryptobetEU
Actually, looking at your config again - you already have
opencode-anthropic-auth@0.0.8installed.Easiest fix for you: Just change
@0.0.8to@latest:That's it. No need to add the
modeblock - the plugin does the same thing under the hood.Hope that helps you :)
@thamrx commented on GitHub (Jan 28, 2026):
The best temporary fix is to add the following to
~/.config/opencode/opencode.json:@johnmalek312 commented on GitHub (Jan 29, 2026):
@thamrx does this make it match claude code exact system prompt and tooling?
@Cyb3rDudu commented on GitHub (Jan 30, 2026):
For me, it works even with the integrated oauth. I do not need to add anything into my opencode.json
however, I realized that opencode burns my claude max tokens in a way that I saw the first time the wait some hours message.
When I work with Claude Code, the tokens are much less and I basically have multible instances of it in parallel running on different projects and I never reach that limit.
Is anyone else experiencing opencode also as token burner?
@ilbarone87 commented on GitHub (Jan 30, 2026):
@Cyb3rDudu i also have noticed the same issue. It burns to my limit very quickly. I thought that was due to get-shit-done plugin, but seems i’m not the only one to experience a higher than normal usage of tokens
@cedws commented on GitHub (Feb 1, 2026):
I believe Claude Code switches between Haiku/Opus automatically for efficiency. In OpenCode I can't see any way to use the automatic mode, if it's using Opus 4.5 for everything that would explain why it burns usage so quickly.
@Christopher-R-Perkins commented on GitHub (Feb 1, 2026):
Claude code has their Explore agent specifically use Haiku, along with their statusline-setup using Sonnet and Claude Code Guide using Haiku, everything else inherits.
Opencode doesn't have set models, so you need to set up your subagents yourself(the builtin ones inherit)
@cantalupo555 commented on GitHub (Feb 1, 2026):
@Cyb3rDudu @ilbarone87 @cedws
You need to set in the
opencode.jsonfile:You can set any model, or even a different provider, as OpenRouter:
@cryptobetEU commented on GitHub (Feb 2, 2026):
I use google gemini antigravity high for explore and general
@dearkafka commented on GitHub (Feb 6, 2026):
@Cyb3rDudu @ilbarone87 its totally expected behaviour. native claude code is "dumber" partly because it relies more on cached tokens. and it is the reason why they from time to time ban max accounts using opencode. If Im not mistaken API (not pro/max sub) has control for caching.