App ID

Not configuredEdit

App slug

Not configuredEdit

Client ID

Not configuredEdit

Webhook delivery

Not configuredEdit

Client secret

Not configuredEdit

Private key

Not configuredEdit

Webhook secret

Not configuredEdit

Logto connector secret

Not configuredEdit

Instance

https://gitlab.com

Application ID

Not configuredEdit

Secret

Not configuredEdit

Redirect URI:

Scopes:

GitLab does not expose OAuth application creation through an API. In User settings → Applications, or a group's Settings → Applications, add an application whose redirect URI is exactly the value above, keep Confidential selected, grant the scopes above, then save the generated Application ID and Secret here. GitLab shows the secret only once.

Use your own user applications unless you are an instance administrator registering one application for everyone; an instance-wide application lives in the Admin area instead.

Creating each agent's bot account later needs authority this page cannot verify — no GitLab API reports it: either connect an instance administrator (whose API token cannot act as one while Admin Mode is enabled), or, on Premium and Ultimate, turn on Admin → Settings → General → Account and limit → “Allow top-level group Owners to create service accounts”.

Instance

https://gitea.comEdit

Each organization connects Gitea by pasting the personal access token of a bot user it created, in the console — nothing about that identity is a deployment setting. Gitea 1.23 or later, or Forgejo 15 or later, is required, and the address is checked against that floor when it is saved.

Leave the field empty for gitea.com. A self-hosted instance under a path prefix keeps the prefix. A Forgejo instance, Codeberg included, is entered the same way.

App ID

Not configuredEdit

Client ID

Not configuredEdit

Client secret

Not configuredEdit

Signing secret

Not configuredEdit

Logto sign-in

Not configured

Client ID

Not configuredEdit

Client secret

Not configuredEdit

Webhook signing secret

Not configuredEdit

Callback URL:

Webhook URL:

Linear does not expose OAuth application creation through an API. In Settings → API → OAuth applications, create one application under the product's own name and icon, add the callback URL above, then save its Client ID, Client secret, and webhook signing secret here.

On the same application, enable webhooks, point them at the webhook URL above, and check the Agent session events category.

Until that category is enabled, agent sessions are disabled for the whole application: delegating an issue only sets the delegate badge and no session is created. Enabling it later raises a new scope, so every already-connected workspace must reconnect before webhooks arrive.

Client ID

Not configuredEdit

Client secret

Not configuredEdit

Authorized JavaScript origin:

Authorized redirect URIs:

Google does not expose OAuth client redirect settings through an API. Copy these required values into Google Auth Platform; Setup can verify only the Logto connector.

Project ID

Not configuredEdit

Project number

Not configuredEdit

Service-account key

Not configuredEdit

HTTP endpoint URL:

1. Use a Google Workspace account that may create a Cloud project and service-account keys. An organization policy can block key creation.
2. Create a Google Cloud project for this app and enable the Google Chat API in it.
3. On the Chat API Configuration page, build the app as a Google Workspace add-on, the default for a new app (convert an existing app first). Under Connection settings choose HTTP endpoint URL, use one URL for all triggers, and enter the URL above. Allow 1:1 messages and joining spaces, and choose who can use the app.
4. Under Commands, add a slash command named /help with the description "Show how to use this app" and command ID 1; any free ID works, since AgentConnect matches the name.
5. In the same project, create a service account and a JSON key for it, grant it the Browser role on the project, and enable the Cloud Resource Manager API; AgentConnect reads the project number with that key.
6. Save the project ID and key here. The project number is optional: it is on the project's settings page and in the add-on's service account email, service-PROJECT_NUMBER@gcp-sa-gsuiteaddons.iam.gserviceaccount.com. When entered, it must match the number read from the key's project.
7. Configure Google sign-in above, then add the app in Google Chat and send it a message. Each Google Workspace organization connects itself from Google Chat by signing in to the console with Google; publish the app on the Google Workspace Marketplace to reach other organizations.

App ID

Not configuredEdit

App secret

Not configuredEdit

App ID

Not configuredEdit

App secret

Not configuredEdit