ultra_reconnect tool. Use it when you’re working in a terminal or your agent can’t surface the in-app Reconnect link.
Usage
<connector> must be an enabled HTTP upstream that authenticates with OAuth. With no connector name, Ultra reconnects every enabled OAuth connector whose sign-in is missing or expired. See Reconnecting every connector.
Flags
How It Works
- Resolves
<connector>to a configured, enabled HTTP upstream - Opens your browser to sign in, and always prints the authorize URL as a headless fallback
- Waits for you to finish signing in (press
Ctrl+Cto cancel) - Saves the new token to Ultra’s shared credential store
ultra start) afterward so its Ultra device process loads the new token.
Reconnecting every connector
Runultra reconnect with no connector name to re-authenticate everything that needs it in one pass. Ultra picks the connectors to reconnect for you and skips the ones it can’t help:
If nothing needs attention, Ultra prints
Nothing to reconnect. and exits.
Connectors are handled one at a time, each with its own browser sign-in. While a batch is running:
- Press
Ctrl+Conce to skip the current connector and move to the next one - Press
Ctrl+Ctwice in quick succession to stop the batch, leaving the remaining connectors unattempted
Examples
ultra reconnect only applies to OAuth connectors. If the connector authenticates with a token or API key instead, update its credential with ultra config set-token <connector> (see Authentication). Ultra returns a clear error if the connector is unknown, disabled, uses stdio transport, or doesn’t use browser-based OAuth.