Connecting Agents
Build and run pages with Claude Code or Codex from the editor chat, or with any MCP client from your IDE.
Run a local CLI from inside the editor.
Pick Claude or Codex at the top of the chat. Cursor Agent is not offered in the chat for now (Cursor as an MCP client in your IDE still works). Opening the chat checks sign-in for each agent separately. If that CLI is not on this computer, Install runs the vendor's installer. If you are not signed in, Log in opens that provider's sign-in page in your browser. Chat stays locked until the CLI is installed and that sign-in has finished. Check again (or wait a few seconds) after either step. Glider also looks in each installer's own folder, so it finds a CLI you just installed without a restart. The same commands, if you prefer to run them yourself:
| Agent | macOS / Linux (Terminal) | Windows (PowerShell) |
|---|---|---|
| Claude Code | curl -fsSL https://claude.ai/install.sh | bash, then run claude once to sign in. | irm https://claude.ai/install.ps1 | iex, then open a new PowerShell window and run claude once to sign in. |
| Codex | curl -fsSL https://chatgpt.com/codex/install.sh | sh, then run codex once to sign in. | irm https://chatgpt.com/codex/install.ps1 | iex, then run codex once to sign in. |
| Picker | What it sets |
|---|---|
| Model | Claude Code: Default, latest Opus/Sonnet/Haiku aliases, current 5.5 models and earlier versions. Codex: models available to your signed-in account, with their supported effort levels. Use Refresh available models beside the pickers to update the list. |
| Effort | How long the model thinks. Claude Code: Default, Low, Medium, High, Extra High or Max. Codex: the effort levels reported for the selected model, including Max or Ultra when supported. Higher effort usually means better work and more tokens. |
Both pickers sit next to Send and are remembered per agent. Under each reply the chat shows the model and effort it ran with, and the turns, tokens and cost the CLI reported.
- Follow-up messages resume the same agent session.
- Questions from the agent appear as cards in the chat: pick an option, type an answer, choose a palette, or approve a change.
- Every change lands live in the open editor as one undo step.
- Attach files with Attach files, by pasting, or by dropping them anywhere on the chat: from your computer, or page files dragged from the Files panel (those are not uploaded again).
Workflow
The gear at the top of the chat opens Agent settings: the workflow and each provider's remaining allowance. Automatic (the default) decides for every message whether the agent designs a graphic or Control Panel (Artifact mode, below) or works on the page with Glider's tools. The size of the change decides: a new graphic or panel, a redesign from scratch or a new overall look is designed; a colour or two, a text, a size, animation timing, data and every kind of logic go to the tool agent. A fast model reads your message with the page and the conversation (Haiku on Claude, the mini model on Codex) and proposes the way. When it cannot tell, or a redesign would replace changes you made on the page, Glider asks first, about the graphic rather than about modes: for example whether you want a new version of the current lower third or a separate graphic. One click answers and sends the message; Cancel puts it back in the box. Choose myself brings back the Tools / Artifact switch, which a conversation keeps.
| Message | Automatic workflow |
|---|---|
| A new graphic or Control Panel (“Design a scoreboard”, “Bir alt bant tasarla”) | Designed. Next to a design of the same conversation, Glider asks whether it is a new version or a separate graphic, unless you said another or new. |
| Data, logic, animation timing, one change (“Make the title bigger”, “Start the clock on Show”) | The tool agent works on the page. |
| A redesign or new look (“Redesign it, more modern”) | A new version of the conversation's design. For a graphic it did not design, a new graphic next to it in the same scene, drawn from what the original shows: its texts, images, style and live parts. When the design was changed on the page since, Glider asks first. |
| Control Panels (“Maç için bir kontrol paneli yap”, “Panele kartlar için bir bölüm ekle”) | A page's first Control Panel is designed, also when a message needs controls and the page has none. Once the page has one, new controls, sections, layout and logic are built on it by the tool agent; only a separate new panel or a redesign from scratch is designed again. |
| Attached files | They do not decide the way. A design places images and reads text files (CSV, JSON, TXT); other files go to the tool agent for the logic afterwards. |
One conversation can hold tool turns, graphics and a Control Panel. Each runs in its own agent session and, when its turn comes, hears what happened in the turns it did not run. A separate graphic stays on the page when another is revised: a new version replaces only its own design.