docs: link custom-agent guide to connectors; remove broken screenshot stubs

Two fixes:

- The connector docs shipped with <Frame> placeholders pointing at
  /assets/connectors/*.png that don't exist yet. Mintlify renders
  these as broken-image boxes — worse UX than no image at all.
  Strip them; the prose walks the user through every click anyway.
  When real screenshots land they can drop back in.

- Custom-agent guide had no mention of connectors, so nobody building
  a custom agent would discover that real-world data access is a
  one-line REQUIRED_CONNECTORS declaration away. Adds a "Using GAIA
  connectors" section right after Overview that explains what
  connectors are, why an agent should reach for them instead of
  baking API keys into code, and links to the connectors guide.
  Also adds connectors to the bullet list of what custom agents can
  have, and a Card to the Next Steps grid.

Author: itomek

docs/connectors/github.mdx

@@ -35,10 +35,6 @@ MCP server uses.
 4. **Expiration**: pick something — 90 days is a sensible default.
    GitHub will email you before it expires.
 
-<Frame caption="Generate new token in GitHub settings">
-  <img src="/assets/connectors/github/generate-token.png" alt="Generate token" />
-</Frame>
-
 ### Pick scopes
 
 The scopes you grant the token are the **maximum** GAIA can do. Per-
@@ -54,10 +50,6 @@ agent grants further narrow it from there.
 For a typical setup, tick **`repo`** and **`read:user`**. Add
 `workflow` if you want agents to interact with Actions.
 
-<Frame caption="Token scopes — pick the minimum your agents need">
-  <img src="/assets/connectors/github/token-scopes.png" alt="Token scopes" />
-</Frame>
-
 5. Scroll to the bottom and click **Generate token**.
 6. **Copy the token now** — GitHub will not show it again. It looks
    like `ghp_…` followed by 36 characters.
@@ -69,10 +61,6 @@ For a typical setup, tick **`repo`** and **`read:user`**. Add
 3. Paste the PAT into the **GitHub Personal Access Token** field.
 4. Click **Save**.
 
-<Frame caption="The Configure form for the GitHub connector">
-  <img src="/assets/connectors/github/agent-ui-form.png" alt="GitHub configure form" />
-</Frame>
-
 GAIA will:
 
 1. Store the token in your OS keyring (single slot, distinct from any

docs/connectors/google.mdx

@@ -29,10 +29,6 @@ Otherwise:
 2. Click the project dropdown at the top → **New project**.
 3. Name it something like `gaia-personal` and click **Create**.
 
-<Frame caption="New project dialog in Google Cloud Console">
-  <img src="/assets/connectors/google/new-project.png" alt="Create new project" />
-</Frame>
-
 ## Step 2 — Enable the APIs you want to use
 
 GAIA only sees the Google APIs you explicitly enable on the project.
@@ -45,10 +41,6 @@ For a typical setup enable at least:
 In the Cloud Console, go to **APIs & Services → Library**, search for
 each API by name, click it, and click **Enable**.
 
-<Frame caption="Enable the Gmail API in the Library">
-  <img src="/assets/connectors/google/enable-api.png" alt="Enable API" />
-</Frame>
-
 ## Step 3 — Configure the OAuth consent screen
 
 Google requires you to fill in a consent-screen form before it will
@@ -64,10 +56,6 @@ issue OAuth credentials, even for personal-use apps.
    pages — leave them empty for now. You'll add yourself as a test
    user in the next step.
 
-<Frame caption="OAuth consent screen — minimum required fields">
-  <img src="/assets/connectors/google/consent-screen.png" alt="Consent screen" />
-</Frame>
-
 ### Add yourself as a test user
 
 While the app is in **Testing** publishing status (the default), only
@@ -95,10 +83,6 @@ This is the credential GAIA uses.
    Secret**. **Copy both** — you'll paste them into GAIA in a moment.
    You can also download the JSON.
 
-<Frame caption="The OAuth client credentials dialog">
-  <img src="/assets/connectors/google/client-credentials.png" alt="Client credentials" />
-</Frame>
-
 <Warning>
   Even though "Desktop app" clients are technically public (the secret
   isn't a real secret in the cryptographic sense), Google's token
@@ -114,10 +98,6 @@ This is the credential GAIA uses.
 4. Paste the **Client ID** and **Client Secret** from Step 4.
 5. Click **Save & Connect**.
 
-<Frame caption="The Save & Connect form in the Agent UI">
-  <img src="/assets/connectors/google/agent-ui-form.png" alt="Save and Connect" />
-</Frame>
-
 GAIA will:
 
 1. Store the credentials in your OS keyring (macOS Keychain on Mac,

docs/connectors/index.mdx

@@ -26,10 +26,6 @@ All credentials live in your OS credential store (macOS Keychain,
 gnome-keyring/kwallet on Linux, Credential Locker on Windows). GAIA
 never writes a token to a plaintext file.
 
-<Frame caption="Settings → Connections in the Agent UI">
-  <img src="/assets/connectors/connections-panel.png" alt="Connectors panel showing Google and GitHub" />
-</Frame>
-
 ## How to set up a connector
 
 1. Launch the Agent UI: `gaia chat --ui`.

docs/guides/custom-agent.mdx

@@ -18,6 +18,38 @@ Custom agents can have their own:
 - **Preferred models** (override the server default)
 - **Conversation starters** (suggestion chips in the UI)
 - **MCP servers** (any Model Context Protocol server)
+- **Connectors** ([Google, GitHub, and more](/connectors)) — give your agent permission to read your real email, calendar, repos, etc.
+
+---
+
+## Using GAIA connectors
+
+If your agent needs to act on your behalf — read your inbox, list your
+calendar events, query GitHub, post to Slack, etc. — wire it up to a
+**GAIA connector** rather than asking users to paste API tokens into
+your code.
+
+A connector lets users:
+
+1. **Authenticate once** in Settings → Connections (OAuth flow for
+   Google-style providers, paste-an-API-key for MCP servers).
+2. **Grant scopes per agent** so each agent only sees the data it
+   actually needs. The Agent UI surfaces this when a user first picks
+   your agent.
+3. **Trust that secrets stay in the OS keyring**, never in plaintext
+   files or env vars baked into your code.
+
+Declare what your agent needs by setting `REQUIRED_CONNECTORS` on the
+class, and call `get_credential_sync(connector_id, agent_id, required_scopes=[...])`
+from inside a tool to get a usable token. The
+[`connectors-demo` agent](https://github.com/amd/gaia/blob/main/src/gaia/agents/connectors_demo/agent.py)
+is a working reference for both `oauth_pkce` (Google) and `mcp_server`
+(GitHub) connectors.
+
+<Card title="Read the connectors guide" icon="plug" href="/connectors">
+  Walks through what connectors are, how the OAuth + MCP flows differ,
+  per-agent grants, and a step-by-step setup for Google and GitHub.
+</Card>
 
 ---
 
@@ -340,6 +372,9 @@ If you used a manifest with `mcp_servers:`, the BuilderAgent's MCP template emit
   <Card title="MCP Integration" icon="plug" href="/sdk/infrastructure/mcp">
     Connect any MCP server to extend your agent with external tools
   </Card>
+  <Card title="GAIA Connectors" icon="key" href="/connectors">
+    Give your agent permission to read Gmail, GitHub, Slack, and more — without baking API keys into code
+  </Card>
   <Card title="RAG SDK" icon="magnifying-glass" href="/sdk/sdks/rag">
     Add document Q&A to your agent with the RAG SDK
   </Card>