Get started
Console
Where your applications, credentials, auth links, and test runs live.
The console is where you create applications, find credentials, build auth links, watch connections, and test prompts on a connected account before you write code. Sign in with an email code or a Google account.
Applications
Create an application, then open it for its credentials and settings:
- Client ID is the application's id and the
client_idon every auth link. - Client secret appears once, for confidential applications only, because WOOL keeps only a hash of it. Copy it before you leave the page. You can rotate it later from the application's overview; the new secret is shown once and the previous one stops working immediately.
- Redirect URIs are matched exactly. Register every callback your app uses, including a
localhostone. The console's own callback needs no registration: it works for every application, and a connection made through it can only be completed by you, signed in to the console. On a public application, alocalhostor plainhttpredirect is for development only: anyone can run that address on their own machine, complete a connection, and every sign-in and run settles to your balance. Remove it before real users connect. A server application is safe here, because its code cannot be exchanged without the client secret. - Icon is what users see when they authorize. Use a square JPEG, PNG, or WebP of at most 512 KiB.
The client type locks once the application has connection history. Applications and clients explains the choice.
Auth link
The auth link is the URL your user opens to connect an account. The application page builds one for you:
choose the website, pick a redirect URI (one you registered, or the console's own callback), and copy the URL. Opening it runs a real connection through
the selected callback. In your app, generate a fresh state value to check when the user returns and, if you
use PKCE, a new verifier and challenge for each authorization. The Quickstart explains how
to generate these values and build the link in your app.
Connections
Connections belong to your application. To end the active connection in the playground, choose Revoke connection. Every token for that connection stops accepting new runs, and WOOL deletes the saved sign-in. Past executions stay readable. A run already in progress may still finish.
Your app can revoke a single token at POST /v1/oauth/revoke; that leaves the connection and saved sign-in in
place. You can delete an application after its active runs and sign-ins finish. Deleting it removes all its
connections and execution history.
Playground
Select a token you saved from a callback, write a prompt, and run it. The playground shows that connection's execution history, newest first, with the status, the reason if the run failed, and the result JSON. Testing with the playground walks through a session.
Account
Your email, name, and role. Signing out ends the session in every tab.
Next steps
With an application created, follow the Quickstart to connect a user's account, exchange the authorization code, and run a prompt on that account.