Why submit a repo
- Verify repository-aware retrieval on your own code.
- See the ranking claim against real tasks in one repository.
- Unlock repo-specific API and MCP examples when the runtime is ready.
Submission flow
- Open the control plane.
- Connect the GitHub installation that owns the repository.
- Choose a supported Python, JavaScript, or TypeScript repository.
- Activate the repository and follow the readiness states.
Status meanings
- submitted: the repo was accepted into the intake path.
- onboarding: repository metadata and artifacts are being prepared.
- training: ranking inputs are being prepared for the runtime.
- evaluating: the produced runtime is being checked before serving.
- ready: the runtime is active and the repository is being served.
- failed / needs attention: the automatic path stopped and may require operator inspection.
Supported today
- Python
- JavaScript
- TypeScript
What to expect
Supported repos auto-start the happy path while intake is active, but submission does not make the repository live instantly.
Sparse or unusual repositories may stop early. That is expected in the current public beta and does not mean every repository will follow the same path.
What ready means
Ready means a runtime is active and the repository is being served.
At that point the submission detail can issue a verification token and present repo-specific next steps for API or MCP.
Related docs