⚠️ This is highly experimental and will break often. Use at your own risk.
What?
Glide Code is a plugin for Claude Code, which gives the world's most popular coding agent the ability to not only build apps and work in Glide, but to do so with many agents in parallel via browser automation and Glide's multiplayer support.
This is a much more powerful (but slower) version of the built-in Agent in Glide today. It's more powerful because it can do everything in the builder, but it's also a general-purpose agent which can do things like analyze files and use the Glide API.
Clip from a 4hr session where Glide Code built 3 apps (sped up 40x):
Installation
First, install Claude Code if you don't have it.
/plugin marketplace add glideapps/glide-code
/plugin install glide@glide
How to Use
Run the /glide command with what you want to build or work on:
/glide Build an app for managing repairs for our construction company. The data is in repairs.csv
This will open a browser window where you can sign in to Glide (first time only). Your session will be remembered for future use. Claude will use the appropriate agents to build your app.
You can also kick off a working session with an existing app:
/glide do a design review on my Repairs app
Working on multiple apps: You can work on many apps at the same time, but you should work on them in separate directories with separate instances of Claude Code.
Development
Running Scripts
| Script | Purpose |
|---|---|
./scripts/start | Run plugin from installed/cloned repo (from any directory) |
./scripts/dev | Run plugin for local development (run from repo root) |
When working on the plugin itself, use scripts/dev from the repository root. This loads the plugin from the current directory, so changes to agents, skills, and commands are reflected immediately.
git clone git@github.com:glideapps/glide-code.git
cd glide-code
./scripts/dev
Alternatively, point Claude Code to the local directory:
claude --plugin-dir /path/to/glide-code/glide
Build Workflow
- Clarify use case - Understand what you want to build
- Create app - Start a blank app in Glide Builder
- Analyze file (if provided) - Extract data structure from spreadsheets
- Create tables via API - Import data using the Glide API
- Build screens - Design the UI with Playwright automation
- Design review - Critique and improve screen layouts
- QA verification - Verify features actually work
- Finalize - Configure access and publish
Commands
| Command | Purpose |
|---|---|
/glide | Guided setup - interactive login, choose app, select task |
/tip | Provide expert guidance - plugin learns and updates skills |
Agents
| Agent | Purpose |
|---|---|
| build | Creates apps and builds screens via browser automation |
| data | Creates tables and imports data via Glide API |
| file-analysis | Analyzes spreadsheets to extract data models |
| design-review | Critiques screens for design quality on mobile/desktop |
| qa | Verifies features work before declaring the app ready |
| app-research | Explores existing apps to document structure |
Skills
| Skill | Purpose |
|---|---|
| glide | Main workflow, agent coordination, builder navigation |
| design | Screen structure, component selection, layout patterns |
| templates | Browse Template Store for design inspiration |
| data-modeling | Tables, columns, relationships |
| computed-columns | Math, If-Then-Else, Relations, Rollups |
| ai | AI columns (Generate Text, Audio to Text, etc.) |
| api | Glide API v2 usage |
| app-sharing | Privacy settings and authentication |
| browser | Multi-browser coordination for parallel work |
Concurrent Operations
The plugin supports up to 6 parallel browser sessions, enabling multiple agents to work simultaneously on the same app. Glide is multiplayer-enabled, so concurrent edits work seamlessly.
Use cases:
- Build multiple screens in parallel
- Design review while building continues
- QA verification alongside fixes