Glide AI App Builder: Building With the GlideOS Agent and Credits

Glide (glideapps.com) puts its AI app builder inside GlideOS, the product new sign-ups are sent to. There, the Glide Agent turns a prompt, a spreadsheet, a PDF or a screenshot into an internal app, the tables behind it and the workflows around it. All of that work is paid in credits, GlideOS's standard unit for the LLM tokens the agent spends. GlideOS Free lets you build and test, but publishing and the choice of agent mode start on GlideOS Basic, $25 per month with 100 credits, billed monthly. Building through your own agent over MCP needs GlideOS Pro, priced at $125 per month for 5 team members and 500 credits, billed monthly.^[1] The craft is spending those credits where they count.

Four ways to hand the agent a starting point

Every GlideOS build begins in a chat box. You can describe the app in plain English, upload a CSV or Excel file, attach a PDF, an image or a text file, or connect a Google Sheet. The home-screen prompt links only one Google Sheet per project, and further sheets are connected through the chat panel. Workbooks under 100 MB are read and imported, while bigger files get a too-large message. Start from whichever input already holds your real columns.

Spreadsheets pass through SheetSense, Glide's proprietary layer for translating a sheet into software. Glide's launch recap says it looks for formulas, comments, macros, pivot tables, charts and conditional formatting, beginning with a lighter pass because a full scan is expensive. The agent also flags contradictions or missing data and asks you to settle them rather than guessing. One behavior catches sheet owners out. GlideOS copies the sheet into its own database table and never writes back, so later edits live only in GlideOS, unlike the two-way sync of Glide Classic (see our Glide review).

Since August 2026, each new app stops at a mockup filled with sample data and waits for your go-ahead, even when the first message said to build it. Glide calls this Plan mode and says it replaced a wait of about 8 minutes with a preview in seconds. The agent now asks for live data sources before that first mockup, so the screens carry your real columns and rows. Treat this pause as your cheapest review. A change requested here reshapes a sketch, not a finished project with apps, tables and workflows already wired together.

Agent modes and the credit meter

Paid GlideOS plans let you pick a model tier per chat and switch at any moment. The pricing page calls the tiers light, medium and heavy; the docs name them Light, Balanced and Heavy. GlideOS Free offers no choice. According to the docs, Balanced uses about 3x the credits of Light and Heavy about 5x Light, and the cost of a single message is not reliably predictable.^[2] Our rule of thumb: keep Light for small edits, label changes and layout nudges, and save Heavy, at about 5x Light, for requests where it spares you more Light retries than its extra cost.

Credits are pooled across the organization rather than assigned per person. Only on GlideOS Pro do members add credits, 50 each on top of 250; GlideOS Basic and Plus credits do not grow with members. Monthly credits reset every billing cycle, and unused ones do not carry forward. Extra credits are one-time purchases on paid plans, valid for 12 months and spent only after the monthly allowance is gone; GlideOS Basic allows one top-up a month, GlideOS Plus two, Pro and Enterprise unlimited. When monthly credits run out, new AI requests stop until the reset or a top-up, and owners get an email. Glide's June 2026 changelog put the markup at 3% over raw LLM cost.

GlideOS Plus is where credits scale on their own. Its menu runs from $50 per month for 250 credits to $1,025 per month for 10,000 credits, billed monthly, and by our arithmetic each further 250 credits adds $25 a month, so the price per included credit falls from $0.20 to about $0.103. GlideOS Pro with 5 members and 500 credits, at $125 per month, costs $50 a month more than GlideOS Plus with 500 credits at $75 per month. That gap buys two more members, MCP, unlimited published apps and human support. Every GlideOS plan bills monthly, and Glide says annual plans are coming soon (our Glide pricing guide covers the menus).

Runtime AI, workflows and integrations keep spending after launch

Building is only the first bill. AI features you place inside an app draw on the organization's pool, and the GlideOS Terms say a Glide app may consume the account's credits whenever it is used. Only owners see the Usage page, which splits spending by user, project, mode, build agent versus Runtime AI, workflows and integrations; a Cycle filter shows use since the billing period began, and Enterprise adds a per-model view. Open it often in the first month.

Workflows can be created on any GlideOS plan but run only on paid ones: GlideOS Basic enables one, GlideOS Plus five, Pro and Enterprise an unlimited number. Triggers include schedules, webhooks, row added, updated or deleted (since October 2026), integration events, app buttons and manual runs. Step costs fall in tiers, and Glide's own example puts a 500-step run at 30 credits. Because cost depends on the data each run processes, every trigger shows an estimated monthly figure. When the agent sets a schedule, it states the runs and credits to expect each month.

Integrations reach over 1,000 services through Composio, connected from chat or the project screen with one-click authorization, and the agent never sees stored credentials. Each call costs 0.01 credits. GlideOS Free is limited to one integration, premium integrations sit on Pro and some services cannot connect at all because of their sign-in method. Watch one quirk. A data trigger ignores changes made by tools that write straight to the database, such as your own scripts. Connection details are in our guide to the Glide API and integrations.

Reviewing what the agent built

Draft changes stay in preview until you publish, and only paid organizations can publish. Before that click, a short review pays for itself:

• Open the mockup and the preview on the devices your team actually uses; GlideOS supports Chrome, Safari, Firefox and Edge on desktop, Chrome and Safari on mobile.
• Ask GlideOS to read back its project memory, the file every chat in the project consults; you cannot edit it directly.
• Check each workflow's estimate and, after a few runs, its cost per run and its 7-day and 24-hour totals.
• Confirm the access mode, because data shown in a public app is open to anyone with the link.

Recovery depends on the plan. Version history, which saves a version each time an update succeeds, starts on GlideOS Plus. Data backups cover 24 hours on GlideOS Pro and 30 days on Enterprise. A deleted project cannot be recovered. The agent may read files and data from other projects in the organization, but its writes stay in the active one.

The GlideOS Terms treat the authorized actions of AI agents as yours, tell you to review their work and keep your own backups, and accept no liability for agent-caused loss. They also bar using agents for legal, medical, financial or tax advice, or for decisions that materially affect a person without human review. Build approval steps into anything of that kind.

Your own agent on GlideOS Pro, your own provider on Enterprise

Since August 2026, GlideOS has run an MCP server for bring-your-own-agent building, included on Pro and Enterprise. Claude, Claude Code, Cursor, ChatGPT or any MCP client signs in through OAuth as the user, with that user's permissions; only admins or editors can connect, and each connection serves one organization. The reasoning runs on your own provider plan, so building this way spends no Glide credits, yet Runtime AI, workflows and integrations still do.^[3] Glide's changelog adds that unexpected MCP credit usage is not refundable. Each action can be set to ask first, always approve or never ask.

The app itself stays in Glide. If a builder leaves or an agent subscription lapses, Glide says (as read in November 2026) the company keeps the software and can keep editing it from another agent or in GlideOS, and different people can work on the same app with different agents. That makes MCP a fit for teams that already pay for a coding assistant and want GlideOS to host the result.

Model choice is an Enterprise matter. Only GlideOS Enterprise lets the organization choose its LLM provider. Glide's Enterprise page says admins pick approved models, set an AI budget and per-person daily caps, and see spend by model, project, app and team. Lower plans get the three modes. Glide's Terms also let it substitute or remove models and providers at any time without notice.

Prompts, training and the older Glide Classic AI

The GlideOS Privacy Policy (July 2026) says Glide uses the prompts, instructions and conversations you enter, plus the structure, configuration and formulas of your apps and spreadsheets, to train its AI features and models. It says it does not use the specific data values or personal data in your data sources for training.^[4] Where an account type offers an opt-out and you used it, your inputs are left out, and the Terms add that a later opt-out does not undo past training. For Enterprise, Glide says its contracts state no AI training on customer data. Glide says Glide Classic is SOC 2 Type 2 certified and SOC 2 Type 1 for GlideOS is in progress (as read in November 2026), and both products' rules prohibit HIPAA health data.

Glide Classic has its own, older AI. Glide AI there offers ten features, from Generate Text to Image to Text and Text to JSON, used as columns or actions on paid Glide Classic plans (Explorer and up), and each use spends Glide Classic updates, not credits. A Generate Text column reruns on every row when its prompt changes. Since January 2026, paid Glide Classic plans can also connect OpenAI, Gemini and Claude models, plus over 300 models through OpenRouter; the AI provider bills separately and each run spends updates. The two products keep separate accounts, and Glide has no tool to move a Classic app into GlideOS.

The bottom line

GlideOS is where Glide's AI building lives, and it rewards teams that already run on spreadsheets and want internal apps without a developer. Publishing starts on GlideOS Basic at $25 per month with 100 credits, billed monthly. The real budget, though, is behavior: Light mode for small edits, a firm review at the mockup, and a weekly look at workflow costs once apps go live. Teams with a coding assistant should price GlideOS Pro for MCP. Anyone who needs app-store apps should look elsewhere for now.