Skip to content

Glossary

The terms you come across in Highwind and in this documentation, in alphabetical order.

The database rules that decide who can read or change each row (“row level security”, RLS). The agent creates them for every table: each user only sees their own data.

The name chosen for your published app, in front of .highwind.site (for example souffle-yoga for souffle-yoga.highwind.site): 3 to 40 characters, lowercase letters, digits and hyphens. You choose it in the Publish menu and can change it with Change the address. See Publishing.

The artificial intelligence that builds and changes your app. It reads and writes the project’s files, installs libraries, checks that everything compiles and that the preview shows without errors, then sums up what it did. See How the agent works.

A short form the agent shows in the chat when a few answers really change what it will build. It’s pre-filled with its guesses; you can answer or click Let the agent decide. See Agent questions.

An app’s visual stance (editorial, bold and graphic, organic, technical…). For each new app, the agent starts from a direction that suits the topic, so that two projects don’t look alike. Your style instructions always come first. See Design and themes.

The “data” part of an app: a database, user accounts and file storage, hosted in Paris by Highwind (with Supabase). It’s enabled for a project in Project settings → Backend, or from the agent’s choice card; the agent never enables it on its own. See Database.

The chat’s normal mode: the agent changes your app. The opposite of Discussion mode.

The Your call card the agent shows when your app needs to keep data and several solutions are possible (Google Sheets spreadsheet, email, database, “later”). You choose, and the agent carries on. See Data choices.

A connector key saved in your account (Connectors page), encrypted and reusable across projects. You can have several for the same service, for example a test key and a production key. See Account connections.

An outside service your app can use: emails (Resend, Brevo…), payments (Stripe, Mollie…), AI (OpenAI, Mistral…), Google Sheets, Slack and more than 50 others. Most are used with your own key, called by the app’s server. See Connectors.

An account the agent can read to build your app: Notion, Linear, Figma or Kameleoon. You connect it once from the Connectors page. See Context sources.

The unit that measures the agent’s work. Each request is counted according to the work actually done: less than one credit for a change, 2 to 4 for a new app. During the beta, 5 credits per day and at most 30 per month. See Credits.

A dark variant of your app’s theme, set in Design → Theme → Light and dark. You choose the mode shown by default: Device setting, Dark or Light.

The left panel mode (Chat / Design switch) where you edit your app yourself, without the agent and without credits: Element tab (an element’s text, colors, sizes, spacing) and Theme tab (palettes, colors, fonts, dark mode). See Design mode.

A chat mode where the agent answers, explains or proposes a plan without changing anything. The Apply this plan button then has it carried out. Shortcut: Alt + P. See Discussion mode.

Attaching an element of the preview to your message (+ menu → Select an element), so the agent knows exactly what you’re talking about. See Select an element.

The building blocks of an A/B test with Kameleoon. An experiment compares a page’s original version with one or more variations; a goal (a click, a page visited) measures which one converts best. See Experiments and variations.

The domain apps are published on (your-app.highwind.site). It’s kept separate from the platform (highwind.app) so that published apps can never touch your Highwind account.

A third mode of the left panel (Chat / Design / Kameleoon), visible when your Kameleoon account is connected and your project is linked to a site: experiments, variations, results and goals. See The Kameleoon panel.

The app server’s journal: messages and errors from its /api routes. Server logs button in the preview bar, with a Preview tab and a Live tab (the published app, over 24 hours).

A pill inserted in your message by typing @, which points to a connector or a context source. The agent then knows exactly which service to use.

Your app running, shown on the right of the editor (Preview tab). It updates live while the agent works and when you make edits. It has an address bar, Desktop, Tablet and Mobile views, and logs. See The preview.

Highwind’s current phase: invite-only access, free, with credits offered every day.

Standing rules the agent follows on every message in a project (style, tone, language…). They’re set in Project settings → General → Instructions for the agent. See Project settings.

Putting your app online at its .highwind.site address. Update publishes the latest version; Unpublish takes the app offline. See Publishing.

A reference image (screenshot, mockup, inspiration) is looked at by the agent but doesn’t go into the site. A project image (your logo, your photos) is saved in the project and shows in the site. See Project images.

A request handled by the agent, from the message sent to the final summary. A run can be stopped (Stop the agent); it creates a version if it changed files, and it’s counted in credits according to the work done.

The isolated environment, specific to each project and located in the European Union, where the agent writes code and where the preview runs. It’s disposable: the real source is the last saved version.

An API key or confidential value (for example RESEND_API_KEY) used by the app’s server. Secrets are encrypted, never shown again, never shown to the agent nor sent to visitors’ browsers. They’re managed in Project settings → Secrets. See Secrets.

Your app’s code that doesn’t run in the browser: /api routes to call a service with a secret key, send an email or receive data. The agent only adds it when a feature needs it. See App server.

A project’s environment stops after 15 minutes without activity and restarts within a few seconds when you come back. After 24 hours, it’s recreated from the last version.

Two or three next steps the agent proposes under its reply. One click sends them as a request.

A complete app from the Start from a template gallery, which you get instantly and without credits to customize. See Templates.

All of your app’s colors (by role) and fonts (text and headings), adjustable in Design → Theme.

Your app’s colors named by their role rather than their value: Background, Text, Secondary text, Cards and blocks, Borders, Primary, Text on primary, Accent, Text on accent, and a few more roles if the design needs them (8 to 12 in total). The whole site uses these roles: changing a role changes all its uses at once. See Design and themes.

A saved, numbered state of your project (v1, v2…). Every request to the agent, every editing session and every code save creates one. You can view and restore any version. See Versions.

The changes made in Design mode. An editing session becomes a single version, saved when you go back to the chat or when the agent starts.