The consent screen is what a user sees when they click an agent install link. It shows the declared scope, identifies the author, and gives two options: approve or decline.
What the user sees
┌─────────────────────────────────────────────────┐
│ Stripe Payment Monitor │
│ by Alice Chen · v1.0.0 · 42 installs │
│ │
│ This agent is requesting access to: │
│ │
│ ● Stripe read, list │
│ ● GitHub write, create │
│ │
│ Your credentials are never shared with the │
│ agent author. All access is logged and you │
│ can revoke at any time. │
│ │
│ [ Approve ] [ Decline ] │
└─────────────────────────────────────────────────┘
The two options
Approve — grants exactly the declared scope. Gazebo creates an access profile under the user's account with the permissions shown and reveals a one-time bearer token.
Decline — nothing happens. No profile is created, no access is granted.
No account required to view
The consent screen is public. Someone without a Gazebo account can read the full declared scope before deciding whether to trust the agent. Gazebo prompts signup only when the user clicks Approve — the consent decision requires an account to create the access profile.
This is intentional: the consent screen is the primary acquisition surface. Gating it behind a login would hide the value proposition from the people most likely to become users.
What happens after approval
- Gazebo creates an access profile under the installing user's account — scoped to exactly the declared scope
- A one-time bearer token is revealed on screen — copy it immediately, it is not shown again
- The access profile appears in the Agents dashboard alongside other profiles
- All credential access from this agent is logged in their audit trail
- They can revoke access at any time from the Agents dashboard
If a service shown on the consent screen isn't connected in the user's vault yet, get_credential will return a service_not_connected error when the agent tries to use it. The error includes a link to add the credential.
The one-time token
After approving, the bearer token is shown once on the confirmation screen. This token is what the agent uses to authenticate against the MCP endpoint or REST API. Store it in your agent's environment configuration — Gazebo does not store or re-display it.
# Example: set in your agent's environment
GAZEBO_TOKEN=<paste token here>
What the agent author sees
The agent author sees:
- Total install count on their published agent page
- Current version status (active / deprecated / revoked)
The agent author does not see:
- Who installed the agent
- What services the installing user connected
- Any credential values from the installing user's vault