Limits of GitKraken's personal access token handling: no automatic expiration detection

Goal: maintain uninterrupted repository interactions after a personal access token (PAT) reaches its expiration date without requiring manual re‑entry.

Constraint: GitKraken currently does not monitor PAT validity; it only reacts when a push, pull or fetch fails with an authentication error, at which point the user must re‑enter the token.

Uncertainty: whether future releases will add proactive expiration checks, integrate with the provider’s API to query token validity, or provide configurable warnings before a token lapses.

Does GitKraken plan to implement token‑expiration notifications or pre‑flight validity checks for PATs?
Can users configure GitKraken to query the hosted service for token status before each operation?
Is there a roadmap for automatic re‑authentication prompts when an impending PAT expiry is detected?