> This page is for GlideOS.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://www.glideapps.com/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://www.glideapps.com/docs/_mcp/server.

# Projects

Projects hold one or more apps that all work with the same data. Every app you build in GlideOS lives inside a project. The number of projects your

organization

can create depends on your plan.

Projects are designed to scale with your work. Each one can store elements that are shared by all the apps within that project. A project can contain:

* One or more apps
* Chat history
* Workflows
* Integrations
* Data tables and connections
* Secrets
* Attachments

You can access the Projects screen from the left sidebar at any time.

# Create a Project

You can create a project from three places.

1. **Home screen:** Type a prompt in the box on the home dashboard. Ask GlideOS to create a new project, or describe an app you want to build.
2. **Sidebar:** Click the

   <path d="M5 12h14" /><path d="M12 5v14" />

   sign next to **Projects**. Name the project and click **Create**.
3. **Projects screen:** Click the

   <path d="M5 12h14" /><path d="M12 5v14" />

   **New** button at the top right. If your organization has no projects yet, click **Create a project**. Name the project and click **Create**.

# Access a Project

Recent Projects that you’ve visited appear in the sidebar automatically. Select the Project name to view and go directly to elements from the project. From this sidebar you can open:

* Recently visited chats
* Data tables
* Apps
* Attachments

## Add a project to favorites

Adding projects to your favorites pins them to the left sidebar. When a project is pinned, you can go directly to the project screen, an app inside the project, a recent chat, a data table, or an attachment from the sidebar. There are two ways to pin a project:

1. **From the project dashboard:** Click the three-dot menu that appears when you hover over a project. Click **Add to favorites**.
2. **From the project screen:** Click the three-dot menu at the top right of the screen. Click **Add to favorites**.

# Delete a Project

> **Deleting a project is permanent.**
>
> Deleting a project is a permanent action. Deleted projects can’t be recovered.

There are three ways to delete a project:

1. **From the project dashboard:** Click the three-dot menu that appears when you hover over a project and select **Delete**. To confirm, click **Delete** again.

2. **From the project screen:** Click the three-dot menu at the top right of the screen and select **Delete**. To confirm, click **Delete** again.

3. **From the chat:** Ask in any chat to delete a project, or several at once. GlideOS will ask you to confirm before it deletes anything.

# Project Memory

Every project has a shared memory file that GlideOS reads from when working on your apps. Its contents apply across every chat and app in the project, including new apps you build.

Each chat session is independent, so GlideOS can’t read previous conversations directly. Project memory is how it carries decisions and context forward instead.

GlideOS keeps a memory file in each project as it works. You can also explicitly ask it to remember something, or to update or remove something if a decision changes.

You can’t view or edit the memory file directly. To find out what’s currently in it, ask GlideOS to read it back to you or tell you what is noted about a specific topic. If something important was decided in a past chat, confirm that the project memory reflects it before building on top of it.

GlideOS can read project memory notes from any app in the project, so a decision made while building one app can inform another.

Here are some ways you can use project memory:

* **Store branding and design rules.** Use project memory to define the visual and tonal standards that apply across every app in the project. Tell GlideOS your specific colors or a defined writing style so GlideOS applies them consistently whenever it builds or updates an app.

* **Store business context.** Give GlideOS context about what your organization does, who your users are, and how your business operates. A vehicle leasing company, for example, might specify that it leases to businesses rather than individuals and that maintenance is included in the contract price. GlideOS uses that context when building new apps so it doesn’t need to be re-explained each time.

* **Store terminology.** If your business uses specific names for things, store them in project memory. A logistics company that refers to its customers as “shippers,” for example, can tell GlideOS to use those terms consistently across every app.