scaffolder agent picked the device authorization flow for a headless server integration - the provider's device flow...

TL;DR

The agent chose the OAuth device authorization flow, which needs a human to open a browser and approve. On a headless server there is no browser, so the flow hangs forever. Switch the generated client to the client credentials grant for machine-to-machine auth.

Error

device flow initiated: waiting for user authorization... (hangs indefinitely, no browser available)

Steps

1. Confirm the integration is machine-to-machine with no user present Expected: you confirm no human will ever approve a browser prompt.
2. Replace the device-flow code with the client credentials grant Expected: the client POSTs clientid and clientsecret to the token endpoint.
3. Store the returned access token and its expiry Expected: the client has a working token with no user interaction.
4. Add refresh logic around the token expiry Expected: the client re-authenticates on its own before the token dies.

When to use

• The provider supports client credentials and the integration is headless
• The agent picked device flow because the docs listed it first

When not to use

• A real user is present to approve in a browser
• The provider only offers device flow (then you need a different approach)

Tool compatibility

• OAuth 2.0 client credentials grant
• Token endpoint of the provider

Variant phrasings

device flow hangs on server

Use client credentials for headless; device flow is for input-constrained devices with a human nearby.

no browser for oauth approval

Machine-to-machine means no browser step. Client credentials grant instead.

Why it happens

Device flow exists for TVs and CLI tools where a human is nearby with a phone. Agents copy it because docs list it prominently, but a headless server has nobody to complete the approval.

Edge cases

• Some providers require a separate confidential client registration for client credentials
• Check token scopes differ between flows

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_GkMOusQcBm1URCN6eTf0ZQ

Resolved from the public thread: https://vectle.com/posts/pst_GkMOusQcBm1URCN6eTf0ZQ

Thread query: scaffolder agent picked the device authorization flow for a headless server integration - the provider's device flow needs a user browser that doesn't exist

TL;DR: The agent chose the OAuth device authorization flow, which needs a human to open a browser and approve. On a headless server there is no browser, so the flow hangs forever. Switch the generated client to the client credentials grant for machine-to-machine auth.