Claude Code authorization is not created in previously initialized projects with another provider

[ilyv]

When running the npx magnitude command in a previously initialized project with another provider, the claudeCode.json credentials file is not saved.
When I updated to the latest version and tried to use Claude Code, I got stuck on the authorization step. As a workaround, I ran the magnitude init, which successfully set up the authorization.

Environment

• macOS
• magnitude-test@0.3.10
• magnitude.config.ts contains:

llm: {
    provider: "claude-code",
    options: {
      model: "claude-sonnet-4-20250514"
    },
  }

Steps to Reproduce

1. Ensure .magnitude/credentials/claudeCode.json file doesn't exist.
2. Run the Magnitude command: npx magnitude ...
3. On the Anthropic callback page, copy the provided authorization code.
4. Paste the authorization code into the terminal prompt.

Actual Result

• Terminal process remains awaiting input after code is pasted.
• claudeCode.json file is not created in the .magnitude/credentials/ directory.

Expected Result

Access and refresh tokens should be successfully saved in claudeCode.json after authorization code is submitted.

[anerli]

So when running normally it prompted you for claude code authorization, but putting it in did not create a claudeCode.json file? magnitude init shouldn't prompt for claude code authorization, thought create-magnitude-app would - you're saying it worked in that case though?

[raivisdejus]

@anerli if the claude code token has managed to expire running a magnitude test (that was working previously) will prompt for an authorization, it will also open the authorization screen and show a place to paste the authorization code from claude website, but on pasting the code nothing will happen. The authorization will not be saved and magnitude will not work.

Workaround for this is to run magnitude init that will process authorization and the token will be saved.

[ym-han]

I'm running into this issue too, when I follow the steps at https://docs.magnitude.run/testing/test-setup with my own project without having first done npx create-magnitude-app@latest elsewhere.

Deps:

• "magnitude-test": "^0.3.10",
  

• package-lock says magnitude-core version is "0.2.31",

Magnitude config:

import type { MagnitudeConfig } from 'magnitude-test';

export default {
  // Vite's default dev server
  url: 'http://localhost:5173',

  // Use Claude Code instead of direct API
  llm:
    {
      provider: 'claude-code',
      options: {
        model: 'claude-sonnet-4-20250514'
      }
    },
} satisfies MagnitudeConfig;

Issue:

❯ npx magnitude

  Magnitude v0.3.10  
  
  ☰ tests/magnitude/example.mag.ts
    ◌ can add and complete todos
  
  
  ◌ 1 pending  tokens: 0 in, 0 out
Claude Code Pro/Max access token missing or expired.
Opening browser for authentication...

If browser did not open, visit:
https://claude.ai/oauth/authorize?code=true&client_id=9d1c250a-e61b-44d9-88ed-5944d1962f5e&response_type=code&redirect_uri=https%3A%2F%2Fsiteproxy.ruqli.workers.dev%3A443%2Fhttps%2Fconsole.anthropic.com%2Foauth%2Fcode%2Fcallback&scope=org%3Acreate_api_key+user%3Aprofile+user%3Ainference&code_challenge=zep0gQq5051wO1O9IuIcjMEcb9jWzYP6T99GJc32zqE&code_challenge_method=S256&state=DVzBVQjoRkKB-1Fdz3KupCB2KGdr2rKFhZGL1f30f04

Paste the authorization code here:
<gets stuck here even after code is pasted>

[ym-han]

The workaround that worked for me: run npx create-magnitude-app@latest (in a separate dir or whatever) and work through the wizard to do the Magnitude x Claude Code auth. The CC configuration / auth flow in that wizard is more reliable.

[anerli]

Ah hm, yeah with the test runner it might not be waiting properly for the code. The workaround mentioned by @ym-han should work in the meantime - but yeah probably the test runner should check for this specific situation and handle the oauth handoff specifically