Getting started
Condux private-beta onboarding is assisted. The Condux team can help with installation and the first codebase setup, but the overall path is straightforward.
1. Request access
Section titled “1. Request access”Request beta access at condux.build. Once your workspace is ready, sign in to app.condux.build with GitHub.
2. Connect your tools
Section titled “2. Connect your tools”The Dashboard launch checklist guides you through the required connections:
- Install the Condux GitHub App for the repositories you want to use.
- Optionally connect Linear if your team manages product work there.
- Connect OpenRouter, Anthropic, or OpenAI for model access.
- Connect Slack and install Mason if you want product planning in Slack.
Each connection is scoped to your Condux workspace.
Use Integrations to connect or repair external services, Settings for workspace identity, membership, and shared runtime secrets, and Codebases for repository setup and repository-specific secrets.
3. Import a codebase
Section titled “3. Import a codebase”Choose an available GitHub repository. Condux investigates how the project is developed and tested, then opens a small configuration pull request for your team to review.
You do not need to write the initial configuration from scratch. Condux proposes it based on the repository. Review and merge the pull request when it reflects the way the project should be prepared and validated.
After the merge, Condux validates a working environment for the codebase. The dashboard shows when the codebase is ready.
4. Choose where to begin
Section titled “4. Choose where to begin”If the work is still an idea, mention @mason in Slack. Mason can help the team investigate it, make decisions, and create the Linear issue.
If the work already exists in Linear, delegate the issue directly to Condux. If you work entirely in GitHub, add the condux label to an issue in an imported repository. Condux creates that label when the repository is imported. Either path uses the same built-in grooming and delivery pipeline.
5. Follow the work
Section titled “5. Follow the work”Open the run from Linear, the status comment on a labeled GitHub issue, or the Condux dashboard. You can follow its current stage and inspect the evidence it produces. Condux returns the result as a normal GitHub pull request for your team to review and merge.
Your first successful run
Section titled “Your first successful run”At the end of a successful first run, you should have:
- A Linear or GitHub issue connected to the work
- A visible Condux run with stage history
- A GitHub pull request containing the implementation
- Test, review, and preview evidence when applicable
Next, learn how to delegate work or follow a run.