> For the complete documentation index, see [llms.txt](https://docs.openbrush.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrush.app/user-guide/portals.md).

# Portals Between Sketches

Add a portal widget that links the current sketch to an Icosa Gallery sketch.

A portal is a spherical widget that links the current sketch to another sketch on the Icosa Gallery. Its surface displays the destination sketch's thumbnail; activating it loads that sketch.

## Requirements

1. The destination must appear in the **Curated** or **Liked** section of the Sketchbook. Local sketches cannot currently be used as portal destinations.
2. Open Brush needs an internet connection to retrieve the destination from Icosa Gallery.
3. Save changes to the current sketch before testing a portal. Activating it loads another sketch and may show the normal unsaved-changes confirmation.

## Add a portal

1. Open the Sketchbook.
2. Open **Curated** or **Liked**.
3. Open the options menu for the destination sketch.
4. Select **Drop Portal**.
5. Move and scale the portal like another widget. Pin it if you do not want it to be moved accidentally.
6. Save the current sketch to store the portal and its destination.

## Use a portal

Point the brush controller at the portal and pull the trigger. Open Brush downloads the destination if necessary and then loads it. The portal changes appearance while loading is in progress.

Portal links use the destination's Icosa asset ID. A portal will stop working if that asset is removed or can no longer be downloaded.

## API

The HTTP API can add a portal at the current brush position with an Icosa asset ID:

```
http://localhost:40074/api/v1?portal.add=dLHpzNdygsg
```

See [Open Brush API](/user-guide/open-brush-api.md) for API setup and security guidance.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openbrush.app/user-guide/portals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.