Start with the entitlement. Then trace the install.

Contact support

Use the published address for purchase, access, installation, privacy, terms, or refund questions. Checkout will not open without a configured support address.

No response-time guarantee or support service-level agreement is offered. Before checkout opens, the owner must confirm that the configured mailbox is monitored and that purchase and access requests can be handled reliably.

What support covers

• locating a Polar purchase or GitHub repository benefit;
• matching the connected GitHub account to the private repository;
• understanding an installer error or preserved-file conflict;
• clarifying the current product, licence, privacy, or refund pages; and
• receiving a refund request for review.

Support does not include building or debugging a buyer’s game, operating a live service, guaranteeing an engine or portal outcome, or receiving proprietary projects unless a separate written arrangement says otherwise.

Private-repository access checklist

1. Confirm that the GitHub account connected in Polar is the account you intend to use for development.
2. Accept any pending GitHub invitation associated with the benefit.
3. Sign in to that account at GitHub and open getagentguild/kit-games.
4. If GitHub shows a 404, verify the browser account again; private repositories commonly appear missing to an account without access.

Installer checklist

1. Use Node.js 22 or newer.
2. Run gh auth status locally and confirm the active GitHub account can open the private repository.
3. Run the installer from the top-level directory of the intended game project.
4. Read conflict messages carefully. The installer deliberately preserves files you modified instead of silently overwriting them.
5. Review the complete, print-friendly buyer setup guide.

What to include in a request

• the purchase email and GitHub username;
• the Polar order identifier, if available;
• your operating system and Node.js version;
• the exact command you ran; and
• a redacted error message and the step where it occurred.

A minimal reproduction is useful for an installer defect, but do not attach a private game project or customer data unless support explicitly agrees on a safe transfer method.

Keep credentials and player data private

Never send passwords, GitHub personal access tokens, OAuth tokens, recovery codes, Polar access tokens, webhook secrets, payment-card data, private keys, or unredacted gh auth status credential output. AgentGuild does not need those secrets to diagnose entitlement or installer problems.