> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/readme/content-development-environments/set-up-a-github-codespace-environment.md).
# Set up a GitHub Codespace environment
This topic provides step-by-step instructions for setting up a personal Codespace for developing Cortex XSIAM content.
**What are GitHub Codespaces?**
[GitHub Codespaces](https://github.com/features/codespaces) are cloud-based development environments provided by GitHub that allow you to set up remote environments with preinstalled and preconfigured tools and dependencies using a dev container.
Your Codespace environment is hosted on GitHub's servers (attached to your GitHub account), and allows you to access your Codespace from any computer.
**Cost and limitations**
GitHub offers a free quota for Codespaces (which is higher for GitHub Pro users) that you can utilize for developing Cortex XSIAM content.
The quota is calculated based on the number of hours your Codespace is actively running. You can see the free quota plan and options for additional paid usage after you reach your quota, in the [GitHub documentation](https://docs.github.com/en/billing/managing-billing-for-github-codespaces/about-billing-for-github-codespaces#monthly-included-storage-and-core-hours-for-personal-accounts).
You will receive an automated email notification when you have used 75%, 90%, and 100% of your free quota. You can find information about your Codespaces quota usage in the GitHub settings under **Billing and plans**. For more information, see the GitHub article [Viewing your GitHub Codespaces usage](https://docs.github.com/en/billing/managing-billing-for-github-codespaces/viewing-your-github-codespaces-usage).
{% hint style="info" %}
### Note
Codespaces generated from the content repository (or a fork of it) are configured to have four cores by default.
{% endhint %}
**Create a new Codespace**
1. Log in to your GitHub account. If you do not have a GitHub account, you must create one before you can create a Codespace.
2. Enter the [content repository](https://github.com/demisto/content).
3. Fork the repository to your account.
1. Click **Fork** at the top right.
2. Select your account as the owner, and leave the repository name as is.
3. Keep the **Copy the master branch only** option selected.
4. **Create fork**.
4. After a few seconds, you are redirected to your forked repository page.
5. Create a new branch on your fork, and give it a meaningful name.
6. Click **Code**, go to the **Codespaces** tab, and **Create Codespace on \branch name>**.
If the message **This Codespace is requesting additional permissions** appears, **Continue without authorizing**.
7. Click **New Codespace**.
This may take a few minutes to complete.
**Configure an IDE**
Browser-based Visual Studio Code
By default, GitHub provides a browser-based Visual Studio Code editor that's automatically configured, authenticated, and connected to your Codespace, using your GitHub account.
To open the editor, enter the main forked repository page, click **Code**, go to the **Codespaces** tab, and click the newly created Codespace (should have a random name).
It can take a few minutes for the Codespace to be fully initialized. This delay only occurs the first time you open a Codespace.
Once the initialization is completed and your Codespace is ready, you are redirected to the IDE, where you can start your development.
Visual Studio Code (local)
To connect to your Codespace from a local Visual Studio Code editor and use the [Visual Studio Extension](/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/readme/content-development-environments/visual-studio-code-extension.md), you need to install the official [GitHub Codespaces extension](https://marketplace.visualstudio.com/items?itemName=GitHub.Codespaces).
For a complete installation and configuration tutorial, refer to the [Using GitHub Codespaces in your local development environment](https://docs.github.com/en/codespaces/developing-in-codespaces/using-github-codespaces-in-visual-studio-code) article by GitHub. You can skip the **Creating a Codespace in VS Code** section, as we've already created a Codespace.
JetBrains IDEs (PyCharm, IntelliJ IDEA, etc.) (local)
To connect to your Codespace from a JetBrains IDE, you will need to install and configure [JetBrains Gateway](https://www.jetbrains.com/remote-development/gateway).
For a complete installation and configuration tutorial, refer to the official [Using GitHub Codespaces in your JetBrains IDE](https://docs.github.com/en/codespaces/developing-in-codespaces/using-github-codespaces-in-your-jetbrains-ide) article by GitHub.
**Development**
After your IDE is connected to your Codespace, you can start developing your content. The environment comes pre-installed with all the required tools and dependencies for developing Cortex XSIAM content. Configuring SSH keys or any other credentials is not required, as the Codespace is already authenticated using your GitHub account.
**Additional Resources**
For additional documentation about GitHub Codespaces, see the official [GitHub Codespaces documentation](https://docs.github.com/en/codespaces).
---
# 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://cortex-docs.paloaltonetworks.com/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/readme/content-development-environments/set-up-a-github-codespace-environment.md?ask=&goal=
```
`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.