> For the complete documentation index, see [llms.txt](https://docs.screendesk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.screendesk.io/request-screen-recording.md).

# Request Screen Recording

- [Request a recording](https://docs.screendesk.io/request-screen-recording/request-a-recording.md): What customers and agents see when recording and viewing submissions
- [Developer tools](https://docs.screendesk.io/request-screen-recording/developer-tools.md): Capture system info, console logs, and network activity alongside recordings for faster debugging.
- [System Info](https://docs.screendesk.io/request-screen-recording/developer-tools/system-info.md): Metadata captured with recordings and how long it is retained
- [Console logs](https://docs.screendesk.io/request-screen-recording/developer-tools/console-logs.md): Capture browser console output during recordings to debug client-side errors faster.
- [Network Logs](https://docs.screendesk.io/request-screen-recording/developer-tools/network-logs.md): Inspect HTTP requests and responses captured with extension and replay sessions to debug API and loading issues.
- [Installing Screendesk script](https://docs.screendesk.io/request-screen-recording/developer-tools/installing-screendesk-script.md): Embed the Screendesk widget on your site and configure CSP for the script.
- [Send to apps](https://docs.screendesk.io/request-screen-recording/send-to-apps.md): Create Linear, GitHub, and Jira issues from a recording.
- [Linear](https://docs.screendesk.io/request-screen-recording/send-to-apps/linear.md): Create Linear issues from recordings with team, project, and workflow fields.
- [GitHub](https://docs.screendesk.io/request-screen-recording/send-to-apps/github.md): Create GitHub issues from recordings with repository, labels, assignees, and milestone fields.
- [Jira](https://docs.screendesk.io/request-screen-recording/send-to-apps/jira.md): Create Jira issues from recordings with project, issue type, priority, and labels.
- [Branding & customization](https://docs.screendesk.io/request-screen-recording/branding-and-customization.md): Customize branding for the recorder, share pages, and live rooms
- [Remove Screendesk logo](https://docs.screendesk.io/request-screen-recording/branding-and-customization/remove-screendesk-logo.md): Remove Screendesk branding from the recorder and share pages
- [Customize recorder](https://docs.screendesk.io/request-screen-recording/branding-and-customization/customize-recorder.md): Customize the screen recorder UI with your logo and brand colors.
- [Set name alias in recorder](https://docs.screendesk.io/request-screen-recording/branding-and-customization/set-name-alias-in-recorder.md): Set an alias so recipients see the name you choose in recording requests.
- [Disable countdown](https://docs.screendesk.io/request-screen-recording/branding-and-customization/disable-countdown.md): Disable the 5-second countdown so recording starts instantly.
- [Recorder flow](https://docs.screendesk.io/request-screen-recording/branding-and-customization/recorder-flow.md): Show a guided multi-step introduction to customers before the screen recorder opens.
- [Internationalization](https://docs.screendesk.io/request-screen-recording/branding-and-customization/internationalization.md): Supported recorder UI languages, automatic locale switching, and English fallback.
- [Browser compatibility](https://docs.screendesk.io/request-screen-recording/browser-compatibility.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.screendesk.io/request-screen-recording.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.