Claude Code chat client aborts agent threads with AuthRequiredException at token resolution — CLI credentials missing on memex-portal
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 24/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- csharp
調査の方向性
Start with MeshWeaver.AI.ClaudeCode/ClaudeCodeChatClient.cs, especially ResolveToken around line 185 and RunProcessAsync around line 364. The issue reports missing CLI credentials and points to earlier incident #4988, so first compare its remediation and confirm credentials on the affected deployment. Done means the incident is handled without duplicating #4988; the payload does not establish that a code change is needed.
索引モデルが issue の本文から書いたものです。
説明
What is failing
Agent thread execution on the memex-portal deployment fails with AuthRequiredException before any Claude Code CLI round can run: ClaudeCodeChatClient.ResolveToken throws "Not logged in to Claude Code. Run /login to connect your Claude subscription." (ClaudeCodeChatClient.cs:185), aborting the thread ([ThreadExec] ERROR) with no agent reply.
Probable cause
High confidence: the Claude Code CLI credential store on the affected pod has no valid session — expired, revoked, or missing in that container. This is the same underlying condition as the two earlier incidents (Admin/_LogIncident/573a90667445a82d, Admin/_LogIncident/d0b80e494a4c7326, filed as Systemorph/MeshWeaver#4988, which folded the first two occurrences spanning 2026-09-17 to 2026-09-20 with reasons ranging from "Not logged in" to "401 Invalid bearer token"). The new occurrence shows the failure now surfacing earlier, at token resolution rather than inside RunProcessAsync, so tokens are still absent ~6 days after the first sighting. The remediation question from #4988 (pre-flight auth check + actionable surfacing instead of a raw ERROR stack, plus ops alerting on auth failure) remains open.
Impact
Minimal: a single occurrence on one pod (memex-portal-deployment-7fd48bdcd4-vhm9l, namespace memex), killing one agent thread run. However, any Claude-Code-backed thread routed to a pod without valid credentials will fail until the credential store is restored.
Where to look
MeshWeaver.AI.ClaudeCode/ClaudeCodeChatClient.cs — ResolveToken (~line 185) and RunProcessAsync (~line 364). First action is operational: re-authenticate the Claude Code CLI / refresh the stored credentials on the memex-portal deployment; this is likely a near-duplicate of #4988 and can probably be closed against it once the credential refresh is confirmed.
Evidence
| Fingerprint | 2c7fde55c5639cba |
| Category | MeshWeaver.AI.AgentChatClient |
| Severity | Error |
| Exception | MeshWeaver.AI.AuthRequiredException |
| Top frame | MeshWeaver.AI.ClaudeCode.ClaudeCodeChatClient.<ResolveToken>b__21_0(CancellationToken ct) |
| Namespace | memex |
| Pods | memex-portal-deployment-7fd48bdcd4-vhm9l |
| Occurrences | 1 |
| First seen | 2026-09-26 09:54:36Z |
| Last seen | 2026-09-26 09:54:36Z |
| Routing | not determined — no configured route matches the category MeshWeaver.AI.AgentChatClient. This repository is the configured fallback, not a finding about who owns the fault; the category names the LOGGER, which may not be the subject. |
Recent log lines
2026-09-26 09:54:36Z memex-portal-deployment-7fd48bdcd4-vhm9l fail: MeshWeaver.AI.AgentChatClient[0]
[ThreadExec] ERROR: 09:54:36.246 threadPath=rbuergi/Task/713c40def4/_Thread/you-are-the-triage-partner-participant-i-d932
MeshWeaver.AI.AuthRequiredException: Not logged in to Claude Code. Run /login to connect your Claude subscription.
at MeshWeaver.AI.ClaudeCode.ClaudeCodeChatClient.<ResolveToken>b__21_0(CancellationToken ct) in /repo/src/MeshWeaver.AI.ClaudeCode/ClaudeCodeChatClient.cs:line 185
at MeshWeaver.Mesh.Threading.IoPool.<>c__DisplayClass73_2`1.<InvokeBlockingCore>b__3() in /home/runner/work/MeshWeaver/MeshWeaver/src/MeshWeaver.Mesh.Contract/Threading/IoPool.cs:line 895
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot, Thread threadPoolThread)
--- End of stack trace from previous location ---
at System.Threading.Channels.AsyncOperation`2.GetResult(Int16 token)
at MeshWeaver.Reactive.ObservableTopNExtensions.ToAsyncEnumerableSequence[T](IObservable`1 source, CancellationToken ct)+MoveNext() in /home/runner/work/MeshWeaver/MeshWeaver/src/MeshWeaver.Messaging.Hub/Reactive/ObservableTopNExtensions.cs:line 146
at MeshWeaver.Reactive.ObservableTopNExtensions.ToAsyncEnumerableSequence[T](IObservable`1 source, CancellationToken ct)+System.Threading.Tasks.Sources.IValueTaskSource<System.Boolean>.GetResult()
at MeshWeaver.AI.ThreadExecution.<>c__DisplayClass29_7.<<ExecuteMessageAsync>b__42>d.MoveNext() in /home/runner/work/MeshWeaver/MeshWeaver/plugins-repo/src/MeshWeaver.AI/ThreadExecution.cs:line 2654
--- End of stack trace from previous loc…[truncated]
Opened automatically from Admin/_LogIncident/2c7fde55c5639cba. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site ceaf1d0cedf26da6: other fingerprints of this site fold in here as comments rather than opening tickets of their own.
- 主要言語
- C#
- スター
- 12
- フォーク
- 5
- 平均マージ
- 5時間 44分
- マージ済み PR(30日)
- 968
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
Systemorph/MeshWeaver のほかの issue
-
bug sev:M
難易度 4/5 3〜5日 初心者へのやさしさ 12/100
Systemorph/MeshWeaver#6857 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
bug sev:M
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
Systemorph/MeshWeaver#6856 ·
メンテナーはふだん 1 日以内に返信
-
bug sev:M
難易度 4/5 3〜5日 初心者へのやさしさ 18/100
Systemorph/MeshWeaver#6853 · コメント 3 件 ·
メンテナーはふだん 1 日以内に返信
-
bug sev:H
難易度 4/5 3〜5日 初心者へのやさしさ 18/100
Systemorph/MeshWeaver#6850 ·
メンテナーはふだん 1 日以内に返信
-
bug cli-publish-failure feature:release-promotion sev:M
難易度 3/5 1〜3時間 初心者へのやさしさ 12/100
Systemorph/MeshWeaver#6845 ·
メンテナーはふだん 1 日以内に返信
Systemorph/MeshWeaver の issue をすべて見る
似ている issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
Sector-Vestige/Sector-Vestige#476 ·
メンテナーはふだん 1 日以内に返信
-
S: Untriaged
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
Trauma-Station/Trauma-Station#5058 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
メンテナーはふだん 2 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 75/100
HoffmanEngineering/3d-print-log-api#243 ·
メンテナーはふだん 1 日以内に返信
-
:books: documentation untriaged
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
メンテナーはふだん 1 日以内に返信