Get started
Get started
Connect a repository, start a coding-agent session, and ship the first reviewable change.
Use this path to evaluate the core 143 loop with the fewest moving parts. A good first run proves that repository access, agent execution, review, and PR creation all work before you add previews, automation, or self-hosted operations.
Connect GitHub so 143 can read repositories and create branches through its GitHub App.
Start a session with a specific repo, branch, coding agent, and prompt.
Review the transcript, diff, validation results, and preview when one is configured.
Open a PR and let repository-native CI/CD remain the source of truth.
What 143 needs
143 works best when the repo includes:
- A clear default branch.
- A deterministic install/test path.
- A
.143/config.jsonfile for repo-specific setup and validation. - Preview config when frontend or full-stack review matters.
- Enough project context in issues, docs, and repository files for a coding agent to act safely.