Testing with the playground

The console's playground lets you connect an account, run prompts on it, and read the execution history. It saves the connection access token when you return from authorization, or you can paste a token from your own app's callback. Test your prompts there before using them in your integration.

Connect an account in the playground

1. In the playground, pick an application and the website to connect. The console uses its own callback as the redirect URI, which needs no registration on the application.
2. Connect an account you own on the WOOL page that opens.
3. You land back in the playground with the connection saved. Only you, signed in to the console, can complete an exchange through the console's callback, so a stranger who starts a flow with it ends up with a code they cannot use. This works the same for a server application: the console never needs your client secret.

The playground stores the token in your browser. Remove clears the selected connection and its token from the playground. To revoke the connection and its tokens in WOOL, choose Revoke connection.

Iterate on a prompt

Write the prompt exactly as you'd send it from code, run it, and check its status. For a completed run, read result.final_text, then result.evidence.urls and result.evidence.side_effects to see what the run did. For a failed run, read terminal.status and terminal.reason. A prompt that names the page, the item, and the exact outcome completes more often than a broad one.

Try the failure paths on purpose

• Sign the account out on the website, run again, and watch the run fail with session_expired and the next run return 409.
• Send a prompt the connection isn't for and watch it fail with blocked_policy or not_possible.
• From code, send the same create request twice with the same Idempotency-Key, request body, and connection token. Confirm the history shows one run; see Idempotency.

The playground doesn't set output_schema; do that from code. It also doesn't replace your own error handling.

Next steps

Move the prompt into code with the Quickstart and wire up Handling failures.