Docs
Use these notes to understand how UGP is supposed to work in production: install the Windows application, sign in, connect a local project, use agents, manage teams and keys, review usage, and understand what the site shows when a release or provider is not configured yet.
Create an account, install the published Windows release when it is configured, sign in from the desktop app, open a local project, and start with a small agent task such as explaining a file or preparing a test.
Agents work against local project context in the Windows app. Use them for explanations, plans, edits, tests, terminal checks, and review notes. Account history records status, provider, model, project, and update time when the server returns them.
Model and provider availability is configured on the server. The website should only present providers that are returned by account or system endpoints, and unavailable providers should be described as configuration-dependent.
Project records can include name, language, local path, status, team, timestamps, and activity counts. File reading, editing, terminal checks, and Git actions happen in the Windows application.
Manage projects, agents, history, usage, API keys, devices, teams, integrations, profile settings, and security state. Protected routes redirect guests to sign-in and should not be promoted for indexing.
Free account creation does not require payment. Pro is $20/month, Team is $40/user/month, and Enterprise is custom. Paid checkout and the Customer Portal use configured Stripe routes.
Self-hosting is for teams that want to run the website and server on their own infrastructure, connect their own model/provider routing, and keep deployment choices explicit.
If sign-in, billing, plan limits, email delivery, provider access, or release downloads are unavailable, verify server health, environment variables, OAuth credentials, SMTP settings, Stripe settings, and the configured release URL.
Create scoped keys only when needed, copy the secret at creation, rotate keys after exposure, and revoke old or unused keys from the account portal.
Use teams for shared billing and project ownership. Keep roles narrow, remove stale invites, and confirm billing ownership before adding production users.
The privacy page explains account data, usage records, billing data, cookies, provider-dependent AI data, retention, disclosure, and user rights in original UGP language.
The terms page explains account responsibility, acceptable use, AI output review, subscriptions, cancellations, availability, support, and product changes.
Google sign-in, Stripe checkout, release downloads, provider access, email delivery, and account data all depend on server or environment configuration. Pages must show the configured state, not pretend that missing services are ready.
The portal displays projects, agents, history, devices, teams, billing, and usage from the configured API. If an endpoint is unavailable, pages should degrade into clear error or empty states.
Code work happens in the Windows application. Documentation should keep that boundary clear so users understand the marketing website is the account and product portal.
