Windows application
Open a local project on Windows, keep the file tree visible, run terminal checks, review suggested edits, and decide which actions the agent can take.
Product
UGP features
UGP is built around a Windows desktop app for coding work and a web portal for everything around that work: account access, projects, agents, history, billing, usage, API keys, devices, teams, integrations, and security settings.
Account portal
Use the website for profile, projects, agents, history, API keys, payments, spend, teams, devices, integrations, settings, and security state.
Sign-in
Email/password sign-in uses the configured server. Google sign-in appears when real OAuth credentials are configured and is hidden or blocked honestly when they are not.
Projects
Project records can show owner, team, status, language, local path, timestamps, and activity counters so the web portal mirrors the work tracked by the desktop app.
Agents and saved history
Agent runs, chat history, statuses, provider/model metadata, exports, and deletion actions stay attached to the account record returned by the API.
Limits and credits
Spend, monthly limits, remaining credits, forecast, breakdown by provider/model, and recent usage events are designed to be visible in the portal.
Payments
Stripe Checkout, Customer Portal links, subscription status, invoices, and billing emails are connected to your account when billing is configured.
API keys
Create scoped API keys, see masked prefixes, rotate or revoke credentials, set rate limits, and reveal new secrets only once.
Teams and devices
Invite members, assign roles, review linked devices, revoke stale sessions, and keep team access separate from personal account settings.
Security settings
Review email verification, account status, linked devices, session recovery, API keys, and destructive account actions from protected routes.
Integrations
The portal is ready to list configured providers and connectors, their status, and account-level settings without claiming unavailable integrations.
Release honesty
Download pages show a direct installer only when a real Windows release URL and version are configured; otherwise they explain the missing release data.
What people use it for
UGP is not a generic landing page promise. These are the practical workflows the product surface is built around today.
Understand a codebase faster
Open a project, ask the agent to explain the structure, identify important files, summarize risky areas, and turn unknown code into a short plan you can verify.
Prepare a focused change
Use the agent to reason through a bug, propose the smallest edit, keep terminal checks nearby, and review the final diff before applying or shipping anything.
Keep account work out of the editor
Billing, devices, API keys, teams, plan state, usage exports, and security settings live in the web portal instead of being mixed into the coding surface.
Clear boundaries
- The website is the account and product portal; coding work belongs in the Windows application.
- The Windows app is the place for local files, terminal work, project context, and agent-assisted coding.
- Integrations, releases, and billing actions are shown only when the required server configuration exists.
- AI output is assistance for review, not a guarantee that code is correct, secure, or ready to deploy without human verification.