> For the complete documentation index, see [llms.txt](https://docs.ccv.brown.edu/archive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccv.brown.edu/archive/jupyterhub/using-your-hub/creating-a-new-notebook.md).

# Creating a New Blank Notebook

## Creating a Notebook on JupyterHub

{% hint style="danger" %}
Notebooks created and stored on Brown's JupyterHub will persist between logins, but will not have any long-term redundant backups . Should you lose permissions to access the hub (i.e., end of semester), or should the hub crash, these files may be lost. To back up your Notebooks, please download them to your local hard drive or push them to GitHub.
{% endhint %}

To create a notebook on JupyterHub, follow the instructions below:

1. Select the local![](https://2883398872-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LLCCXzhzhO5fUT5UTHC-887967055%2Fuploads%2Fgit-blob-05b2353f28dde3ab25bb477c789e19cf0a96e0f4%2FScreenshot%20from%202018-09-19%2009-14-01.png?alt=media)File Browser from left sidebar
2. Create a new launcher using the <img src="https://2883398872-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LLCCXzhzhO5fUT5UTHC-887967055%2Fuploads%2Fgit-blob-cff521c44306f73efa0ccd80c2bee41c012182d4%2FScreenshot%20from%202018-09-19%2015-46-05.png?alt=media" alt="" data-size="line">New Launcher button
3. Click **Python 3** under the **Notebook** section
4. A new “Unititled(#).ipynb” file will appear in your current working drive directory and a blank Notebook will launch. Click on "Untitled" to change the name of the file

![](https://2883398872-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LLCCXzhzhO5fUT5UTHC-887967055%2Fuploads%2Fgit-blob-451f60f3eb838b9e2cb54d7bf7512f63e4ebfda3%2FScreenshot%20from%202018-09-19%2009-21-05.png?alt=media)


---

# 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.ccv.brown.edu/archive/jupyterhub/using-your-hub/creating-a-new-notebook.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.
