> For the complete documentation index, see [llms.txt](https://docs.paradime.io/app-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paradime.io/app-help/products/code-ide/left-panel/bookmarks.md).

# Bookmarks

Bookmarks in the Paradime Code IDE enable you to efficiently mark and navigate important sections of your codebase. This feature helps streamline workflows by allowing you to quickly revisit critical code snippets or areas during your dbt™ development process.

{% hint style="info" %}
**Bookmarks are useful for:**

* Marking important model definitions
* Tagging sections that need review or optimization
* Creating quick access to frequently referenced code
* Building a custom navigation system for large projects
  {% endhint %}

### Managing Bookmarks

{% @arcade/embed url="<https://app.arcade.software/share/XIklhXdi1OxX71lDlHOE>" flowId="XIklhXdi1OxX71lDlHOE" %}

### Adding Bookmarks

1. **Highlight** a block of code you want to bookmark
2. **Right-click** on the highlighted code
3. Hover over **Bookmarks** and select the **Toggle** command
4. A **bookmark ribbon** will appear next to the code block

{% hint style="info" %}
Use **Toggle Labeled Bookmark** to assign a label to the bookmark for additional context. This makes it easier to identify the purpose of each bookmark at a glance.
{% endhint %}

### Navigating Bookmarks

**Using Menus:**

* **Right-click** and hover over **Bookmarks**
* Click **Jump to Previous** or **Jump to Next**

**Using Keyboard Shortcuts:**

* **MacOS:**
  * `⌥ ⌘ L` to **Jump to Next**
  * `⌥ ⌘ J` to **Jump to Previous**
* **Windows:**
  * `F2` to **Jump to Next**
  * `Shift+F2` to **Jump to Previous**

**Using the Bookmarks Panel:**

* Open the **Bookmarks tab** from the left-hand panel to view and manage all bookmarks
* Click on any bookmark in the list to jump directly to that location in your code
* Edit bookmark labels as needed by clicking on the label in the Bookmarks tab

### Deleting Bookmarks

You can remove bookmarks in several ways:

* **From the editor**: Right-click the blue bookmark ribbon next to the code and select **Remove Bookmark**
* **From the Bookmarks tab**:
  * Click the **X** button next to a specific bookmark to remove it
  * Click the **Clear** icon to remove all bookmarks from a specific file
* **Toggle method**: Right-click on bookmarked code and use the Toggle command again to remove the bookmark

***

{% hint style="info" %}

#### Best Practices

**Command Usage**

* Use **Toggle Labeled Bookmark** to add meaningful labels that describe the purpose of the bookmarked section
* Regularly clear outdated bookmarks to maintain a clean and organized workspace
* Use consistent naming conventions for bookmark labels to make them easier to scan

**Workflow Optimization**

* Bookmark key SQL transformations and tests in your dbt models for easy navigation
* Create bookmarks for:
  * Model definitions
  * Complex joins
  * Custom macros
  * Test definitions
* Utilize the "Explorer" section of the Bookmarks tab to get an overview of all bookmarked sections in your project
* Combine bookmarks with other IDE features like Search for powerful project navigation
  {% endhint %}


---

# 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.paradime.io/app-help/products/code-ide/left-panel/bookmarks.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.