Install on Windows with the public entrypoint.
Start with the Windows package-manager path. If that is not available in the environment, use the PowerShell fallback installer instead. From there, move into docs and choose the workflow or surface that matches how your team works.
Start with winget
Use the package-manager path first when Windows already has winget available. That is the cleanest install story for the public product.
Use PowerShell if needed
If winget is unavailable or blocked in the environment, use the PowerShell installer path instead.
Then open the docs
After installation, use the docs and workflow pages to choose whether you are starting from build diagnosis, project reads, agent integration, or editor work.
Primary path first, fallback when needed.
Use the package-manager install when possible. Keep the PowerShell route available as the Windows fallback rather than the primary story.
> winget install Gamibase.Gamibase> powershell -NoProfile -ExecutionPolicy Bypass -Command "irm https://gamibase.ai/install.ps1 | iex"