Every so often we sit down with someone from our support team and turn their week into a blog post. First up: Roberto Vizcarra, on four things generating tickets lately, AI credits, student plans, integrations, and Mac performance. Here’s what changed and what to do about it.

Why your GKAI credits are still moving when you bring your own key

If you’re using bring your own key (BYOK) with your own AI model instead of a GitKraken-provided one, you may have noticed your GKAI credits are still ticking down. That’s not a bug.

Your key handles the AI processing, but GitKraken Desktop and GitKraken services are still doing the work to deliver the feature to you. Because of that, BYOK usage draws a small percentage of GKAI credits. It’s a fraction of what you’d pay using a GitKraken-provided model, but it isn’t zero.

What to do: nothing broken here. If your credits are dropping under BYOK, that’s expected behavior tied to how the feature is delivered.

Student plan changes: what’s different if you joined before the switch

The GitHub Student Pack benefit has changed. New students now get a six-month free Pro trial, with the option to upgrade to Pro at a discount afterward.

If you were a student on the old plan, where you stand depends on how much you’d already used before the system switched over:

• Used less than a year of free trial under the old system? You should be able to move into the new six-month trial and discount.
• Already used more than a year of free trial? You’re no longer eligible for the trial or the discount. You’ll need to purchase a regular Pro account.

What to do: check your usage history under the old plan before assuming you qualify for the new terms.

Integrations now live on gitkraken.dev first

As of version 12.3.0, integrations changed from the ground up. They used to start in GitKraken Desktop, with an option to publish them to gitkraken.dev so other products like GitLens could use them. Now it works the other way. Integrations live on gitkraken.dev first, then filter out to GitKraken Desktop, GitLens, and Kepler.

If you set up an integration before 12.3.0, it may have stopped working. Here’s how to fix it:

• Disconnect the integration locally in whichever product you’re using (GitLens, Desktop, Kepler).
• Go to gitkraken.dev/integrations and disconnect it there too.
• Try reconnecting. For most people, this resolves it.
• Still stuck? Go to your Git provider’s OAuth settings and revoke any existing GitKraken authorizations.
• Reconnect from gitkraken.dev. This generates a fresh authorization request with updated permissions.
• Once gitkraken.dev shows the integration as connected, go back into your product (Desktop, VS Code, etc.) and click reconnect. It’ll pull the new integration down automatically.

What to do: if an old integration breaks after updating, disconnect and reconnect through gitkraken.dev first, not just locally.

Mac users: match your chipset, or your fans will tell you about it

GitKraken Desktop ships in separate builds for Intel-based Macs and Apple Silicon Macs (M1, M2, M3). Installing the wrong one for your chipset usually won’t stop the app from running, but it will cause problems: higher GPU usage, higher CPU usage, and fans running louder than they should from the overheating.

What to do: confirm the build you have installed matches your Mac’s chipset. If your fans have been unusually loud lately, this is worth checking first.