> For the complete documentation index, see [llms.txt](https://docs.zerve.ai/zerve-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerve.ai/zerve-docs/notebooks/notebook-and-canvas.md).

# The notebook and canvas

The two ways to view and work with a project in Zerve.

Every project in Zerve is made of **blocks** connected in a graph: each block takes inputs from the blocks before it and passes its results on. You can work with that graph in two views.

| View         | What it's like                                                             | Best for                                                      |
| ------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------- |
| **Notebook** | Blocks in a list, top to bottom, like a Jupyter notebook                   | Most work, and working with the agent                         |
| **Canvas**   | Blocks laid out as a graph you can see and arrange, with their connections | Seeing how a workflow fits together, and canvas-only features |

Both views show the same blocks. The notebook arranges them in order; the canvas shows how they connect.

## What's only in the canvas view

Some features are only available in the canvas view:

* [**Layers**](/zerve-docs/notebooks/layers.md), which separate a project into workflows such as development and deployment
* The [**Logic gate**](/zerve-docs/notebooks/blocks/logic-gate.md) block
* **API Controller**, **API Route** and **SageMaker endpoint** blocks, for building deployments in a deployment layer. See [APIs](/zerve-docs/ship-your-work/apis.md#building-apis-in-the-canvas).
* Arranging and grouping blocks on the graph

In the notebook view, you deploy apps and APIs from the **Deploy** screen instead. See [Deployments overview](/zerve-docs/ship-your-work/shipping.md).

## How blocks run

Each block runs on its own, on the compute you choose for it, and its results are saved. A block can use the results of the blocks before it without rerunning them. See [How code runs](/zerve-docs/compute/compute.md) and [Variables, outputs and caching](/zerve-docs/notebooks/variables-outputs-and-caching.md).

## Sidebars

Both views have sidebars for the project's resources. Open them with keyboard shortcuts:

| Sidebar                | Notebook   | Canvas     |
| ---------------------- | ---------- | ---------- |
| **Left sidebar**       | Ctrl/⌘ + M | Ctrl/⌘ + M |
| **Layers**             |            | Ctrl/⌘ + 1 |
| **Files**              | Ctrl/⌘ + 1 | Ctrl/⌘ + 2 |
| **Environments**       | Ctrl/⌘ + 3 | Ctrl/⌘ + 3 |
| **Imports**            | Ctrl/⌘ + 4 | Ctrl/⌘ + 4 |
| **Resources** (assets) | Ctrl/⌘ + 5 | Ctrl/⌘ + 5 |
| **Source control**     | Ctrl/⌘ + 6 | Ctrl/⌘ + 6 |

See [Keyboard shortcuts](/zerve-docs/notebooks/keyboard-shortcuts.md) for the full list.

## The agent

Open the agent with **Alt+K** (Windows) or **⌥+K** (Mac). See [Agent modes](/zerve-docs/agents-in-the-workspace/agent-modes.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zerve.ai/zerve-docs/notebooks/notebook-and-canvas.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.