> For the complete documentation index, see [llms.txt](https://legacy.docs.synteq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy.docs.synteq.com/dedicated-servers/server-management/entering-console.md).
# Entering console
A how-to for entering the console on Metal and disabling auto-resizing of the window
## What is console?
Console is a direct interface of your server that acts as a virtual monitor and keyboard, seperate of your OS.
Unlike SSH, RDP or other network based access methods, console connect directly to your server's management interface, thus it remains accessible even if the OS is unresponsive, or the network is misconfigured.
## How to access console?
### 1. Select the server that you would like to console into
You can do this by clicking the server's name on [Metal](https://metal.crunchbits.com/).
### 2. Enter the server's console
Click the `COMSOLE` button on the top-right of your screen.
Then wait a few seconds, and if you have pop ups disabled, click on the link that will be generated.
### 3. Make the console full screen
Start by going to `Options` \[1] > `Preference` \[2]
Then go to `Window` \[1], then **disable** `Auto-resize window` \[2], and click `OK` \[3].
Afterward, click the full screen icon.
Now you can begin working on the server from the console, without being interrupted by the window auto-resizing!
---
# 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://legacy.docs.synteq.com/dedicated-servers/server-management/entering-console.md?ask=&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.
