> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/settings/terminal.md).

# Terminal

Settings for the terminal application tab

Terminal settings control the trading workspace, order safeguards, chart labels, shortcuts, confirmations, and which terminal widgets are visible in each saved layout.

## Main settings

<table><thead><tr><th width="159.625">Setting</th><th>What it changes</th></tr></thead><tbody><tr><td>Orderbook</td><td>Controls bid and ask display style for the active terminal layout.</td></tr><tr><td>Orders</td><td>Sets max slippage, order-fill notifications, and trade form amount inputs.</td></tr><tr><td>Chart</td><td>Shows or hides user fill markers and chart line labels.</td></tr><tr><td>Shortcuts</td><td>Enables keyboard shortcuts for cycling through open positions.</td></tr><tr><td>Confirmations</td><td>Restores safety prompts for terminal and news trading actions.</td></tr><tr><td>Layouts</td><td>Creates, renames, switches, and deletes terminal workspaces.</td></tr><tr><td>Widgets</td><td>Shows or hides terminal blocks in the active layout.</td></tr></tbody></table>

Terminal settings apply to the [Terminal](/features/hyperliquid-trading-terminal.md) tab. Layout and widget choices are saved per terminal layout, so an execution layout can show different blocks than a news-focused layout.

## Orderbook

Use Design to choose how bid and ask depth is arranged.

* Side by Side keeps bids and asks mirrored.
* Stacked places asks above bids with market stats between the books.

Use Display as to choose whether order sizes are shown in the base asset or quote currency.

## Orders

Max Slippage controls the maximum accepted slippage for market order placement, including close-position market orders.

Order Fill Notifications controls whether Proliquid shows a notification when an order from the active trading account receives a fill. Browser notification behavior is configured in [General settings](/settings/general.md), and fill sounds are configured in [Sound alerts](/settings/sound-alerts.md).

Quantity / notional inputs controls which amount fields are shown in the [Trade form](/terminal-sections/trade-form.md).

<table><thead><tr><th width="159.625">Option</th><th>What it shows</th></tr></thead><tbody><tr><td>Show both</td><td>Shows Quantity and Notional inputs.</td></tr><tr><td>Only quantity (ex: BTC)</td><td>Shows the base-asset Quantity input only.</td></tr><tr><td>Only notional (USDC)</td><td>Shows the quote-currency Notional input only.</td></tr></tbody></table>

## Chart and shortcuts

User Fills shows fills from the active trading account as execution markers on the terminal chart.

Chart line labels shows or hides the labels attached to active orders, positions, and protection lines.

Position Shortcuts enables J / K on the terminal to cycle through open positions. This is useful when monitoring multiple positions from the [Positions](/terminal-sections/positions.md) table.

## Confirmations

Confirmation settings restore safety prompts after you choose not to show them.

<table><thead><tr><th width="159.625">Confirmation</th><th>When it appears</th></tr></thead><tbody><tr><td>Cancel Orders</td><td>Before sending a cancel order request.</td></tr><tr><td>Close Position</td><td>Before sending a reduce-only market close request.</td></tr><tr><td>Increase / Reduce Position</td><td>Before sending position size market adjustment requests.</td></tr><tr><td>Trade Block Orders</td><td>Before sending orders from the terminal trade block.</td></tr><tr><td>News Trading</td><td>Before sending orders from news ticker quick-trade actions.</td></tr></tbody></table>

Use confirmations when you want an extra review step before fast execution actions.

## Layouts and widgets

Terminal layouts are saved workspaces. Use layouts to switch between different arrangements for charting, execution, portfolio review, or news-driven trading.

Available layout actions:

<table><thead><tr><th width="136.875">Action</th><th>What it does</th></tr></thead><tbody><tr><td>Create</td><td>Adds a new terminal layout with the default widget arrangement.</td></tr><tr><td>Rename</td><td>Updates the layout name shown in selectors.</td></tr><tr><td>Delete</td><td>Removes the layout and its saved terminal block arrangement.</td></tr></tbody></table>

Widgets are scoped to the active layout. Turning off News in one layout does not hide News in another layout. Mini Markets is disabled by default and can be enabled from the widget list.

Available widgets:

<table><thead><tr><th width="159.625">Widget</th><th>What it shows</th></tr></thead><tbody><tr><td>News</td><td>The terminal news feed.</td></tr><tr><td>Chart</td><td>The primary trading chart.</td></tr><tr><td>Screener</td><td>The terminal market screener.</td></tr><tr><td>Orderbook</td><td>Live bid and ask depth.</td></tr><tr><td>Account</td><td>Account balances and portfolio details.</td></tr><tr><td>Trade</td><td>The order entry block.</td></tr><tr><td>Mini Markets</td><td>Markets available to the active trading account, with shared favorites, sorting, and compact labels.</td></tr><tr><td>Bottom Panel</td><td>Positions, orders, balances, history, Icebergs, TWAPs, and chases.</td></tr></tbody></table>

Related pages: [Terminal](/features/hyperliquid-trading-terminal.md), [Trade form](/terminal-sections/trade-form.md), [Orderbook](/terminal-sections/orderbook.md), [Terminal News](/terminal-sections/news.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.proliquid.xyz/settings/terminal.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.