Repository navigation
fix(dialectic): token-type-aware Anthropic auth — sk-ant-api → x-api-key (CLA-117) - #46
Conversation
…key (CLA-117) The dialectic was the one scheduled Anthropic caller the CLA-117 migration missed — it hardcoded `Authorization: Bearer`, so the sk-ant-api key 401'd every Stage 1 call (06-14 / 06-15 runs: 3/3 errors). Mirror the token-type block cscc/orient/encode already use. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughIn ChangesToken-type-aware auth header
Estimated code review effort🎯 2 (Simple) | ⏱️ ~5 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
The nightly dialectic was the one scheduled Anthropic caller the CLA-117 token-type-aware auth migration missed.
worker_dialectic.rshardcodedAuthorization: Bearer {token}, so once the secret became ansk-ant-api…key, every Stage 1 call got a flat 401authentication_error: "Invalid bearer token".Evidence (
dialectic_runs)Anthropic API 401 … Invalid bearer tokenencode,cscc,orientandadasalready carry the token-type-aware block and were unaffected — only the dialectic was missed.Fix
Mirror the exact block the other callers use:
Verification
cargo check --target wasm32-unknown-unknown --lib— clean.errors_count3 → 0 indialectic_runs.🤖 Generated with Claude Code
Summary by CodeRabbit