Approvals & safety
Dieser Inhalt ist noch nicht in deiner Sprache verfügbar.
Gosper is built so you can hand an agent an entire job without handing over everything your accounts can do.
Reads and writes are treated differently
Section titled “Reads and writes are treated differently”The agent uses outside services through connectors, and every call is one of two kinds:
| Kind | Examples | What happens |
|---|---|---|
| Observation (read) | List a channel’s videos, read a document, look up orders | Runs right away and is recorded in the activity history |
| Action (side effect) | Publish a video, edit a document, send a message, delete something | Waits for approval; nothing happens until you approve |
Approvals don’t block the agent
Section titled “Approvals don’t block the agent”Classic human-in-the-loop makes the agent stop and wait. Gosper doesn’t. When an action needs approval, the connector simulates the outcome, tells the agent it’s done, and lets it keep working on the next steps. You review when it suits you, one by one or in bulk.
A denied action never happens. If later steps depended on it, the agent sees that on its next turn and adjusts.
The Activity panel
Section titled “The Activity panel”Each workspace’s Activity panel has three tabs:
- Needs review: actions waiting for you, each saying what it will do and to which resource. Choose Approve or Deny.
- Auto-approval: action types that may run without asking. Only types the connector’s author marked safe to apply without review appear here; once you turn one on, those actions stop asking.
- History: every observation and action, including ones applied automatically.
Grants go to specific resources
Section titled “Grants go to specific resources”Connecting an account doesn’t hand the whole account to a workspace. You grant a workspace specific resources: “this YouTube channel (read-only)”, “this Linear team”, “these tools of this MCP server”. The agent can’t reach anything outside that grant, and never sees the account’s tokens. See Connectors.
Code runs in a sandbox
Section titled “Code runs in a sandbox”Code the agent writes and apps it builds run in isolated sandboxes, separate from your computer, other users and other apps. An app reaches outside services only through the connections you granted.
Sharing doesn’t leak data
Section titled “Sharing doesn’t leak data”When you share an app, Gosper checks that the people you share with could already see the data the app has read. They connect the service with their own account and must be able to reach the same resources, or they can’t open it. Workspaces that have read especially sensitive data can’t be shared at all. See Sharing & collaboration.