Integrations

Condux connects the tools where product and engineering work already happens.

Slack

The Condux Slack App provides Mason, the AI product manager, and expands shared Condux run links with useful status context.

After Slack is connected, install Mason from the Slack page under Integrations. Condux creates the @mason handle for your Slack workspace. Conversations and installation data remain associated with the matching Condux workspace.

Learn how to work with Mason.

Linear

For teams that use it, Linear holds the durable product record. Condux uses it to:

• Receive delegated work
• Ask focused grooming questions
• Report progress and outcomes
• Connect the issue to its run and pull request
• Let Mason find, create, and update product work

GitHub

The Condux GitHub App provides access only to repositories selected during installation. It supports codebase import, configuration pull requests, implementation branches, pull requests, preview lifecycle, and status correlation.

During import, Condux creates a condux issue label. Adding that label to an open issue dispatches the issue through the same grooming and implementation pipeline used for Linear work. Questions and the durable run status stay on the issue. The App therefore needs read and write access to Issues, plus the Issues and Issue comment webhook events. Existing installations may need an administrator to approve those added permissions.

Your normal repository permissions, CI checks, review rules, and merge process still apply.

Model providers

Connect OpenRouter, Anthropic, or OpenAI from Integrations. These connections provide model access for Condux agents and are scoped to the workspace; they are separate from write-only runtime secrets under Settings.

Connection health

The Integrations catalog shows the current state of each connection. If an installation needs renewed permissions or a reconnect, the Dashboard identifies the affected integration and provides the next action.