usage_limits shows OAuth quota even when session uses Bedrock

[kornicameister]

Hey! Running into something weird with cship in a multi-provider setup.

I switch between AWS Bedrock (personal projects) and company OAuth (work stuff). Personal projects have CLAUDE_CODE_USE_BEDROCK=1 + AWS_BEARER_TOKEN_BEDROCK, work projects just use the default OAuth. Bedrock has no quota, OAuth does.

Problem is, cship.usage_limits always shows my company's OAuth quota regardless of which provider the session is actually using.

Example: in my personal project folder (/Users/me/dev/personal-project), /status confirms Bedrock:

API provider:     Amazon Bedrock
AWS region:       eu-central-1

But the status line shows:

💤 extra: 3% ($12.40)

That's my work account's quota. Bedrock doesn't have one, so this is misleading.

cship explain shows why:

cship.account: Caylent Enterprise
cship.usage_limits.extra_usage: 💤 extra: 3% ($12.40)

It's always reading the OAuth account, not checking what the current session is using.

What I'd expect: if CLAUDE_CODE_USE_BEDROCK=1 is set (or really any non-OAuth provider), usage_limits should either hide or show something like "Bedrock (no limit)".

I could disable usage_limits globally in cship.toml, but then I lose it in work projects where I need it.

Config:

• cship 1.8.0, macOS
• ~/.claude/settings.json: "statusLine": {"type": "command", "command": "cship"}
• Personal projects: .claude/settings.local.json with no forceLoginMethod (Bedrock wins)
• Work projects: default OAuth

Would be nice if cship checked the session's actual provider instead of always defaulting to OAuth credentials.

[kornicameister]

Quick follow-up: is there any way to conditionally disable usage_limits in cship.toml based on environment variables? Something like disabling it when CLAUDE_CODE_USE_BEDROCK=1 is set?

Right now I can only disable it globally, which breaks the quota display in OAuth sessions where I need it.