Pair a test app

The console's Test page cannot sign in to your app as anybody, so anything that runs as the signed-in user (an action connected as the user's token, or your own handlers inside the app) cannot be tried there. A build of your app can. Pairing lets the Test page watch that build's conversation while you use it.

Pair

1. On the console's Test page, press Pair a test app. A code appears, like K7Q2-M9XD. It works once, for ten minutes.
2. In a test build of your app, signed in as a test user, call:

final result = await Rendel.pair('K7Q2-M9XD');

const result = await Rendel.pair("K7Q2-M9XD");

result.ok is true with endsAt when it worked; otherwise reason says why: test_only (the build uses a live key), not_found (the code is wrong, used or expired), rate_limited, or failed. It never throws.

3. The Test page says Paired with your test app and shows what the build is doing as it happens: what was asked, what the copilot drew, each action with its risk and status, and which ones the server ran as the signed-in user.

A pairing lasts two hours, or until somebody presses End pairing.

A hidden developer menu or a debug-only screen is a good home for the pair call; it does nothing in a build with a live key.

What the console sees, and what it does not

• The conversation as it is stored: messages with personal data already masked, the components the copilot drew with their fallback text, and each action's name, risk and status.
• Never the user's token, never action parameters, never what your API returned.
• Only that build, only from the moment it paired, only for the window.

The console watches; it sends nothing to the build. Confirmations happen on the device, as they do for your users.

Who can pair

Owners, admins and developers of the app. Anyone who can read conversations can watch a pairing they started. Pairing works only with the test key: a live build cannot claim a code.