Usage
| Argument | Required | Description |
|---|---|---|
provider | Yes | One of: github, google, slack, linear |
Prerequisites
You must be logged in first. Runtoolshed login if you haven’t already.
How it works
- The CLI reads your config from
~/.toolshed/config.jsonto get your user ID and server URL - Starts a temporary local HTTP server on a random port
- Opens your browser to the server’s OAuth login endpoint for the chosen provider
- The server runs the standard OAuth2 flow (with PKCE where supported)
- After you authorize in the provider’s UI, the server stores encrypted tokens and redirects back to the CLI
- The CLI confirms the connection and exits
Example
Checking connections
Usetoolshed status to see which providers are connected:
Provider details
| Provider | PKCE | Scopes |
|---|---|---|
| GitHub | No | repo, read:user |
| Yes (S256) | gmail.modify, calendar, drive.readonly | |
| Slack | No | channels:read, chat:write, groups:read |
| Linear | Yes (S256) | read, write |