Every so often we sit down with someone from our support team and turn their week into a blog post. This time, Roberto walks us through four things generating tickets right now: an upcoming Microsoft authentication change, how AI credit pools actually work, multi-account support in Kepler, and a one-line fix for laggy GitKraken on Linux or WSL. Here’s what’s changing and what to do about it.

Microsoft is changing how authentication works, here’s what we know

Microsoft is deprecating certain personal access token configurations and changing how its OAuth works. The change is expected to land in early December, and it’s already generating questions from teams who authenticate through Microsoft services.

We don’t have a public-facing plan to share yet. Our team is reviewing options and waiting on additional documentation from Microsoft before committing to a direction. What we can commit to: something will be in place before the December changes go live, so your existing functionality keeps working. We’ll publish specifics as soon as there’s a decision to share.

How GKAI credit pools actually work

Every subscription draws from two separate credit pools, and knowing the difference explains most of the confusion we see in tickets.

• Individual pool: each user gets their own weekly allotment, and it’s the first thing used up when you run AI features.
• Shared organization pool: covers things like automations, and it’s what kicks in once an individual user’s weekly credits run out.
• Add-ons: if the shared pool runs dry too, organizations can purchase additional credits.

Running out of your individual pool doesn’t cut off AI features. The system just starts pulling from the shared pool instead. To check where you stand, click your profile picture for your individual pool progress, or go to Preferences > GKAI to see both the individual and shared pool at once.

Kepler now supports multiple accounts on Pro and above

If you’re juggling more than one AI agent account or more than one git service account, Kepler can now hold onto both, as long as you’re on a Pro-level plan or higher.

• AI agent or cloud accounts: go to Settings > Agent > Cloud and select the option to add an account. Useful if you’re splitting token usage across accounts.
• Git service provider accounts: these connect through gitkraken.dev, not inside Kepler directly. Add the account there first.
• Sync: back in Kepler, hit refresh on the integrations page in Settings to pull in the newly connected accounts, orgs, and repos.

Fix laggy GitKraken on Linux or WSL by turning off GPU acceleration

Running GitKraken Desktop through Linux or WSL adds an extra rendering layer, and that’s usually what’s behind the odd stuff we hear about: UI elements sized wrong, lag when dragging or dropping, general sluggishness.

The fix is counterintuitive but consistent: turn the GPU off. From your WSL instance, run:

gitkraken –disable-gpu

Disabling GPU acceleration resolves the display oddity for most users running GitKraken through Linux or WSL.

FAQ

What authentication changes is Microsoft making, and when?

Microsoft is deprecating certain personal access token configuration options and changing how its OAuth works, expected in early December. GitKraken doesn’t have a public plan to share yet but will have something in place before the change goes live.

What happens when I run out of my individual GKAI credit pool?

You’re not blocked from using AI features. GitKraken automatically starts pulling from your organization’s shared credit pool instead.

Where can I see my GKAI credit usage?

Click your profile picture for your individual pool. Go to Preferences > GKAI to see both your individual and shared organization pools.

Can I connect multiple accounts in Kepler?

Yes, on Pro-level plans or higher. Add multiple AI agent or cloud accounts under Settings > Agent > Cloud. Add multiple git service provider accounts through gitkraken.dev, then refresh the integrations page in Kepler settings to sync them.

How do I fix GitKraken display issues on Linux or WSL?

Run gitkraken –disable-gpu from your WSL instance to disable GPU acceleration, which resolves sizing and lag issues for most users.