> ## Documentation Index > Fetch the complete documentation index at: https://docs.nscale.com/llms.txt > Use this file to discover all available pages before exploring further. # Quick search > Find any resource, page or command in the console from the keyboard. Search by name, ID, IP address, MAC address or hostname, narrow results with filters, and jump straight to what you need. Quick search is the fastest way to get around the Nscale console. Open it from any page, type what you are looking for, and press **Enter** to go there.

Quick search open with no query, showing recent items, suggested pages and create actions

## Open quick search * On macOS, press **Cmd+K**. * On Windows and Linux, press **Ctrl+K**. * Or select **Search** at the top of the sidebar. Press **Esc** to close it. Before you type anything, quick search shows the items you opened recently, a few suggested pages and the most common create actions. Use the arrow keys to move through the list and **Enter** to open the highlighted row. Press **Cmd+Enter** (**Ctrl+Enter** on Windows and Linux) to open it in a new tab instead. ## Search for resources Start typing and results appear as you go. You don't need the full name: each word you type can match any part of a name, ID or other detail, so `train 01` finds `training-node-01`. Small typos are forgiven too, so `traning` still finds it. Matched text is highlighted in each row.

Quick search results for vpc, with matching VPCs, the project each belongs to, and an option to search inside VPCs

You can search across: * **Resources** such as projects, instances, Kubernetes clusters, VPCs, security groups, filesystems, object storage, reservations, placements and models. * **Pages** in the console, including settings, billing and service tokens. * **Commands** such as changing the theme, copying the page URL, copying your organisation ID and signing out. Each resource row shows the project it belongs to. Results you open often, and recently, move up the list over time. When you are working inside a project, that project's resources are listed first. You only see resources and pages that you have permission to view, so the list may differ from a colleague's. ### Search by ID, address or hostname Paste an identifier and quick search recognises what it is. A badge in the search box shows what it found. | Paste | What you get | | :- | :- | | A resource ID, or just its first block (for example `3f2a9c1e`) | The resource with that ID | | An IPv4 address (for example `10.0.4.17`) | The instance or placement server that holds the address | | A CIDR range (for example `10.0.0.0/16`) | The VPCs whose range contains it | | A MAC address | The instance or server with that network interface | | A server hostname (for example `rack-0-3`) | The matching placement servers | | An email address | That person in **Settings > People**, if you manage people in your organisation | | A link to a console page | That page | ## Filter results Type a filter as `key:value` followed by a space, and it turns into a chip that narrows the results. Start typing a key, such as `sta`, and quick search suggests the keys and their values as you go.

Quick search with a status filter chip applied, listing only resources in an error state

| Filter | Values | Example | | :- | :- | :- | | `status` | `pending`, `provisioning`, `provisioned`, `deprovisioning`, `error`, `unknown` | `status:error` | | `health` | `healthy`, `degraded`, `error`, `unknown` | `health:degraded` | | `project` | Any project name in your organisation | `project:research` | | `type` | A resource type, such as `instance`, `vpc`, `sg` or `k8s` | `type:instance` | You can combine filters and text. For example, `status:error type:instance gpu` lists instances in an error state whose name or details match `gpu`. While a filter you typed is applied, only resources are listed; pages and commands come back when you remove it. To remove the last chip, press **Backspace** in an empty search box. When you open quick search from inside a project, it starts with a `project` chip for that project. Press **Backspace** to remove it and search your whole organisation. ## Search inside one resource type A scope limits the search to a single resource type, such as instances or VPCs. This is useful when a name matches several kinds of resource, or when you want to browse everything of one type.

Quick search scoped to VPCs, listing every VPC in the organisation

To enter a scope: 1. Type the name of the resource type, such as `instances` or `vpc`. Common alternatives work too, for example `vm`, `k8s`, `sg`, `bucket` or `nodes`. 2. Press **Tab**. The scope appears at the start of the search box. 3. Type to search within it, or leave the box empty to list everything of that type. You can also select a scope from the **Search in** list at the bottom of the results. To leave a scope, press **Backspace** in an empty search box, or select the **x** on the scope. ## Recent items Quick search remembers the pages and resources you open, whether you reached them through search or by browsing the console. They are listed under **Recent** each time you open it, so you can get back to what you were working on in a couple of keystrokes. Recent items are kept per organisation in your browser. To remove one, highlight it and press **Cmd+Backspace** (**Ctrl+Backspace** on Windows and Linux). ## Create resources Type `create` or `new`, followed by what you want to make, to see the create actions available to you. For example, `new instance` or `create vpc`. If you are already inside a project, the create action opens in that project. Otherwise, quick search asks you to choose a project first. ## Run commands Quick search also runs a few everyday commands: * **Change theme** switches between light, dark and system themes. * **Copy page URL** copies a link to the page you are on. * Type `org id` to copy your organisation's ID, for example when contacting support. * **Sign out** signs you out of the console. ## Calculator Type a sum or a conversion and the answer appears at the top of the results. Press **Enter** to copy it.

Quick search showing the calculator answer for 64 gpus for 2 weeks

| Type | Answer | | :- | :- | | `8 * 72` | `576` | | `(1024 + 512) / 4` | `384` | | `64 gpus for 2 weeks` | `21,504 GPU-hours` | | `2 TiB in TB` | `2.199 TB` | | `3 days in hours` | `72 hours` | GPU-hours accept hours, days, weeks, months and years. Storage conversions accept both decimal units (KB, MB, GB, TB, PB) and binary units (KiB, MiB, GiB, TiB, PiB). ## Keyboard shortcuts Type `?` in quick search to list every shortcut.

Quick search listing its keyboard shortcuts after typing a question mark