Sign-in and permissions
What an agent app may do once you sign it in, for how long, and how to take it back.
An agent app signs in with OAuth the first time it connects, or sends an API key. Either way it can only reach the screens and do the things you granted.
Signing in an app
- The app opens our sign-in page in your browser. You sign in as on the dashboard: an email link, GitHub, Google or a passkey.
- A consent page names the app and asks which screens it may use and with which permissions.
- You return to the app, which now holds a token for those screens and permissions.
The token lasts an hour and renews itself while the app is in use. It works only at the MCP server: the API refuses it, so a token that leaks from an agent app can't be used elsewhere.
The permissions
They are the same four permissions as for API keys (Keys and permissions). Each tool needs one of them, listed on the Tools page:
| Permission | Tools it opens |
|---|---|
read | Look: screenshot, zoom, read_tree, wait, list_screens, status, viewer_link |
control | Mouse and keyboard: act, clipboard |
exec | Commands and files: exec, exec_status, read_file, write_file |
power | No MCP tool uses it yet |
control is close to shell access: with the mouse and keyboard an agent can open a terminal and type commands. Grant exec too when the agent should run commands directly.
When the app needs more
If the agent calls a tool its token doesn't allow, the server answers 403 with insufficient_scope and names the permission. Good agent apps then open the sign-in page again so you can grant it; nothing runs until you do.
An API key instead
For agents that run without a person, such as CI jobs or servers, send an API key from the dashboard: Authorization: Bearer kubi_.... The key's own permissions and screens apply. The setup: Connect.
Taking it back
Open Connected apps in the dashboard and disconnect the app: its tokens stop working at once. A key stops working once you revoke it under API keys. Every call an app or a key makes shows in History.
While your account waits
During the private beta we approve each account by hand. Until then every call answers ACCOUNT_PENDING, and the agent should stop and tell you.