Skip to main content
November 19, 2026
The GitLab Self-Managed integration page in Settings with the GitLab connection card: Check now, Re-install hooks, Change bot token, and Disconnect, the bot @paradime-bot as Maintainer, GitLab version 19.5.2, a token expiry that rotates automatically, and the connected projects with active hooks
Paradime now uses a separate, short-lived GitLab token for every run, and DinoAI agents no longer need git push.
  • A token for each run. Each Bolt run and each DinoAI agent session gets its own fine-grained token. The token can only read code, and only in the projects on the connection. Paradime revokes it when the run or the session ends. See Run tokens.
  • Agent commits pass push rules. DinoAI agents commit through the GitLab API instead of git push, so push rules such as Reject unsigned commits donโ€™t block them. The commits go only to the agentโ€™s own branch. They are made as the person who started the session if that person linked their GitLab account, or as the Paradime bot otherwise, with DinoAI as co-author. See DinoAI agents on GitLab.
  • Change bot token. Admins can replace the botโ€™s token from the GitLab connection card, with no reinstall. See Change the bot token.
GitLab Self-Managed needs version 19.2 or later. See Before you start. Shipped in Paradime v6.26.3.