docs(agent): document the mut_ user token the API now accepts - #12658
Merged
mergify[bot] merged 1 commit intoSep 3, 2026
Conversation
Contributor
Merge Protections🟢 All 6 merge protections satisfied — ready to merge. Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
jd
reviewed
Sep 2, 2026
mergify-ci-bot
force-pushed
the
docs-agent/change-watch
branch
from
September 3, 2026 05:16
624113c to
e3165b7
Compare
Contributor
Author
|
jd
approved these changes
Sep 3, 2026
AlexandreGaubert
approved these changes
Sep 3, 2026
Contributor
Merge Queue Status
This pull request spent 4 minutes 5 seconds in the queue, including 2 minutes 58 seconds running CI. Required conditions to merge
|
63 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The API takes a third bearer credential that this page did not mention: Mergify's
own user tokens, prefixed
mut_. Anyone holding one had nothing here telling themit would work, and the caution box listing the endpoints that refuse a personal
access token said nothing about how those endpoints treat a user token.
Adds a short section for it — the prefix, that it comes from the OAuth 2.0 device
authorization grant, and that it resolves to the same person their dashboard
session resolves to, so holding one grants no access its owner does not already
have. The caution box now says the four application-key-only endpoints refuse a
user token just as they refuse a PAT.
Evidence: the engine's bearer scheme for these tokens, which looks a
mut_*tokenup and returns the same user a dashboard session does; and those four endpoints,
which enable the application-key auth methods and nothing else.
Open question: where a reader gets one. That the device authorization grant issues
it is as far as I could verify — nothing says what to run to start that flow, and
the CLI schema has no login command to point at, so somebody reading this section
still cannot obtain a token. If there is a front door for it, that is the sentence
to add.