Connect with an API key

1. Create a key in Settings → API Keys.
2. Select Authorize and paste the complete grupa_live_… or grupa_test_… key.
3. Choose an endpoint, select Try it out, and then select Execute.

Paste the key without a Bearer prefix. Swagger adds it automatically. The key stays only in this browser tab.

Build a worker that can continue

Persistent workers keep an identity while idle. Enable memory to carry compact context across assignments. Idle identities and pending triggers do not reserve a desktop; execution and waits inside an active run are billed.

• Steer active work: POST /v1/runs/{runId}/feedback. Ordinary feedback continues the run; interrupt: true stops at a safe boundary for follow-up.
• Answer a missing fact: read /questions, then post an answer. Authentication and approvals use their separate interfaces.
• Continue after completion: enable retainContext when creating the run, then use /continue with new work and a new timeout. A new browser starts; source credentials are not copied.
• Wake on time or events: create a persistent worker and use its /automations for fixed intervals, authenticated event triggers, or dependency workflows. Use /turns to queue work while it is busy.
• Call your application: register custom tools with execution: "client" and inputSchema. Claim requests from /tool-calls, execute once, persist results, then submit output.
• Correct an earlier action: /remediations starts linked correction work. Reversal depends on the external system; it is not a guaranteed undo.

The playground exposes feedback, agent questions, and follow-up in Run details. Feedback is not a separate concurrent chat service. Computer control currently uses managed desktops.