Integrations setup

1. 1 During onboarding (or later from Settings → GitHub installations), pick the personal account or organization to connect and click “Install app”.
2. 2 On GitHub, choose all repositories or a selection — that’s the boundary of what Gentlybot can see. You can change or revoke it on GitHub at any time.
3. 3 Optionally enable autonomous capabilities in settings: auto-fix failing CI, address review comments, PR-comment slash commands (@gentlybot …), and security-alert fixes. Each is a separate toggle, off by default, with its own scoped GitHub permission.

Gentlybot clones code on demand into sandboxes; it does not keep a standing copy of your repositories.

1. 1 A workspace admin or owner connects Slack from Settings → Slack; you’ll go through Slack’s standard authorization screen.
2. 2 Invite @gentlybot to the channels where work happens.
3. 3 Mention Gentlybot with a product question in a channel, or send it a direct message. Name the app or flow you mean and attach screenshots when useful.
4. 4 Read the answer in Slack. In a channel, mention Gentlybot again in the same thread to ask a follow-up; it continues the linked Gently thread with the conversation context.
5. 5 If Gently asks for clarification, use its answer buttons or Reply action in Slack. Use “Open in Gently” to inspect the thread, previews, and artifacts.

1. 1 Connect from Settings → Integrations with Atlassian OAuth and pick your site.
2. 2 Threads can then create well-scoped issues (with the PR and evidence linked) and read issue context into runs.

Automation triggers on Jira events are in early access.

1. 1 Connect from Settings → Integrations with Linear OAuth and approve the workspace Gentlybot should use.
2. 2 Runs can search and read issues, create and update issues, change status, and add comments.
3. 3 For automations, choose issue or comment events and optionally narrow them by team or keyword.

1. 1 Connect from Settings → Integrations with Notion OAuth and grant access to the pages you want available.
2. 2 Runs can use those pages as product context and work with page content through the connected integration.
3. 3 Automation triggers can watch page changes and be scoped to a specific page or database.

Early access.

1. 1 From Settings → MCP, add a remote MCP server by URL. Authenticate with a bearer token or OAuth, depending on what the server supports.
2. 2 Pick from presets for common tools (Confluence, Linear, Sentry, Datadog, …) or add any server that speaks the Model Context Protocol.
3. 3 The connection panel shows live health, so a degraded integration is visible instead of silently failing mid-run.

Credentials are encrypted at rest and scoped to your workspace.

1. 1 Capable models are included out of the box — nothing to configure to get started.
2. 2 Admins can adjust model pools in Settings → Model pools: which models handle asking, small coding, and complex coding work, with ordered fallbacks.
3. 3 Workspace-owned provider keys live separately under Settings → AI credentials; Enterprise workspaces can also use private deployments.