FAQ
Frequently asked questions
Clear answers on the product wedge, submission flow, readiness states, credentials, and public beta limits.
Product basics
What Repokit is, what it is not, and who it serves.
Repokit is a repository-aware retrieval product for developers and AI agents. It ranks the files most worth inspecting for a coding task inside one repository.
It is for developers who want to shorten debugging and implementation setup, and for AI agent builders who need better repository context before reasoning or editing.
No. Repokit is not a general autonomous coding platform. The product wedge is repository-aware file ranking inside one repo.
Submission and readiness
How supported repositories move from intake to a ready runtime.
Supported repositories can follow the normal self-serve beta path while intake is active. You connect GitHub, activate the repo, and track the visible stage bar.
No. Submission starts the path, but the repository still needs processing time. It moves through onboarding, training, evaluating, and only then reaches ready.
The user-facing stages are submitted, onboarding, training, evaluating, ready, and failed / needs attention.
Ready means a runtime is active and the repository is being served. At that point you can issue a verification token and query the repo through API or MCP.
Access and credentials
What you need before making verification requests.
Yes. API and MCP are credentialed. When your repository reaches ready, the submission detail provides a verification token and repo-specific next steps.
After the repo is ready, issue a verification token from the submission detail. That token is then used in the API or MCP examples for your repository.
You can query repositories that have reached ready and are being served by the hosted runtime.
Edge cases
Expectations for repositories that do not fit the normal happy path.
Python, JavaScript, and TypeScript are supported today.
Sparse or unusual repositories may stop early and require operator inspection. The product is intentionally narrow, so the happy path is strongest for supported repos with enough signal.
No. Public surfaces focus on submission, readiness, API, and MCP. Admin controls stay internal.