You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Claude Auth needes manual command "claude" after some time #11
Hey @CoderLuii amazing work!
The claude auth plugin seems to have a bug were a user has to manually bash into the container and run claude after some hours.
While this is a problem of the plugin and not yours, It would be nice if you could fix this.
There are some issues connected to that on the Plugins repo, but they havnt been patched yet.
Thanks for reporting this. I am looking into the refresh failure. Which HolyCode image version or digest and Claude Auth plugin version are you running? Please also share the error shown when it stops working, whether plugin updates are manual or automatic, and whether the Claude credentials mount is writable. Redact tokens and account details, and please do not post credential files. This will help distinguish failed token refresh from a session that genuinely needs a new login.
Thanks. Those messages point to the plugin's credential-refresh path; they do not show a Paperclip or OpenCode service restart.
HolyCode v1.2.2 is now available, but it still carries opencode-claude-auth 2.2.0 because no released upstream correction is available. This maintenance release does not fix the issue. For now, running docker exec -it holycode claude and signing in again when requested remains the workaround.
Please also confirm that /home/opencode/.claude is writable inside the container and share whether plugin updates are set to manual, automatic, or disabled. Redact tokens and account details; do not post credential files.
Quick update: upstream Claude Auth 2.2.1 is out, but its release changes Claude Code model compatibility, not token refresh. I’m keeping this issue open; upgrading that plugin alone would not verify a fix.
If this happens again, before running claude, please capture a redacted CLAUDE_AUTH_DEBUG trace, the HolyCode image version or digest, and your HOLYCODE_PLUGIN_UPDATE mode. Please do not post tokens or credential files. The trace should let us distinguish a temporary refresh lock/cooldown from an expired or revoked login. For now, docker exec -it holycode claude remains the reauthentication workaround when prompted.
Thanks for sharing what worked for you. HolyCode v1.2.3 can discover all models from an externally managed CLIProxyAPI endpoint when the model settings are empty, so the single-model limit should no longer get in your way.
I have not evaluated or bundled the linked opencode-cliproxyapi plugin as a replacement for Claude Auth. The two integrations use different authentication paths, and v1.2.3 does not establish a fix for Claude Auth's proactive refresh failure. I’ll keep this issue open for that specific problem. If you try Claude Auth again and can share a redacted CLAUDE_AUTH_DEBUG trace before reauthenticating, that would help pinpoint the failure; please omit tokens and credential files.
Activity
CoderLuii commentedon Sep 14, 2026
Thanks for reporting this. I am looking into the refresh failure. Which HolyCode image version or digest and Claude Auth plugin version are you running? Please also share the error shown when it stops working, whether plugin updates are manual or automatic, and whether the Claude credentials mount is writable. Redact tokens and account details, and please do not post credential files. This will help distinguish failed token refresh from a session that genuinely needs a new login.
TIGamingTV commentedon Sep 14, 2026
To resolve the error momentarily I sometimes just need to run "claude" and exit or i need to login again.
These are the erros i get sometimes:
opencode-claude-auth: Proactive token refresh failed. Runclaude` to re-authenticate.opencode-claude-auth: Proactive token refresh failed. Run
claudeto re-authenticate.opencode-claude-auth: Proactive token refresh failed. Run
claudeto re-authenticate.opencode-claude-auth: Claude credentials are expired and could not be refreshed. Run
claudeto re-authenticate.opencode-claude-auth: Claude credentials are expired and could not be refreshed. Run
claudeto re-authenticate.opencode-claude-auth: Claude credentials are expired and could not be refreshed. Run
claudeto re-authenticate.opencode-claude-auth: Claude credentials are expired and could not be refreshed. Run
claudeto re-authenticate.opencode-claude-auth: Claude credentials are expired and could not be refreshed. Run
claudeto re-authenticate.opencode-claude-auth: Claude credentials are expired and could not be refreshed. Run
claudeto re-authenticate.`As for the versions:
I use the latest Holycode docker image and the latest plugin version shipped with the container (v.2.2.0)
The plugin repo has the following issues that might be connected:
griffinmartin/opencode-claude-auth#281
griffinmartin/opencode-claude-auth#272
griffinmartin/opencode-claude-auth#270
CoderLuii commentedon Sep 18, 2026
Thanks. Those messages point to the plugin's credential-refresh path; they do not show a Paperclip or OpenCode service restart.
HolyCode v1.2.2 is now available, but it still carries
opencode-claude-auth2.2.0 because no released upstream correction is available. This maintenance release does not fix the issue. For now, runningdocker exec -it holycode claudeand signing in again when requested remains the workaround.Please also confirm that
/home/opencode/.claudeis writable inside the container and share whether plugin updates are set to manual, automatic, or disabled. Redact tokens and account details; do not post credential files.CoderLuii commentedon Sep 24, 2026
Quick update: upstream Claude Auth 2.2.1 is out, but its release changes Claude Code model compatibility, not token refresh. I’m keeping this issue open; upgrading that plugin alone would not verify a fix.
If this happens again, before running
claude, please capture a redactedCLAUDE_AUTH_DEBUGtrace, the HolyCode image version or digest, and yourHOLYCODE_PLUGIN_UPDATEmode. Please do not post tokens or credential files. The trace should let us distinguish a temporary refresh lock/cooldown from an expired or revoked login. For now,docker exec -it holycode clauderemains the reauthentication workaround when prompted.TIGamingTV commentedon Sep 24, 2026
I replaced this plugin with CLIProxyAPi.
I also fixed the models and thinking effort not showing with this plugin: https://github.com/DarknessKiller/opencode-cliproxyapi
Might be a replacement for claude auth
CoderLuii commentedon Sep 24, 2026
Thanks for sharing what worked for you. HolyCode v1.2.3 can discover all models from an externally managed CLIProxyAPI endpoint when the model settings are empty, so the single-model limit should no longer get in your way.
I have not evaluated or bundled the linked
opencode-cliproxyapiplugin as a replacement for Claude Auth. The two integrations use different authentication paths, and v1.2.3 does not establish a fix for Claude Auth's proactive refresh failure. I’ll keep this issue open for that specific problem. If you try Claude Auth again and can share a redactedCLAUDE_AUTH_DEBUGtrace before reauthenticating, that would help pinpoint the failure; please omit tokens and credential files.v1.2.7
v1.2.7