Hivel-managed credentials
Every provider - Jira, GitHub, GitLab, Bitbucket, and Azure DevOps - supports two credential models:
Self-hosted (default): you supply token (and email for Jira/Bitbucket) in config.yml / .env, as shown above. The credential never leaves your network - it's used only to authenticate the agent's own outbound calls.
Hivel-managed: omit token (or set it to placeholder) in that provider's config. At startup, the agent fetches the credential from api.hivel.ai using your HIVEL_API_TOKEN instead. Choosing this means Hivel holds that source-system credential on your behalf, rather than you holding it yourself - a deliberate tradeoff, not a default.
Last updated