> For the complete documentation index, see [llms.txt](https://docs.ins-pi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ins-pi.com/freelucy/personalize-and-accessibility/keyboard-shortcuts.md).

# Keyboard shortcuts

Move around Freelucy without the mouse.

YouDesign Freelucy is fully keyboard navigable. You can switch views, move through lists, and act on records without the mouse.

## Switch views

Switch views with the view tabs, or press `Alt/Option` together with the view's number. For example, `Alt/Option + 1` opens Classic, `Alt/Option + 2` opens Flow, and `Alt/Option + 3` opens List.

## Move and act

* **Tab** moves through the header, menus, and dialogs in a logical order.
* **Arrow keys** move between rows inside Flow columns and the List table, which use a roving focus so one arrow press lands you on the next row. In Classic, arrow keys pan the canvas or move the selection, depending on the mode — see below.
* **Delete** removes the focused relationship.
* The **context menu** key opens the actions for the focused record.

## Navigate the Classic canvas

The Classic canvas is a single Tab stop with two modes, so the arrow keys can both pan the view and walk the graph. Screen readers announce the current mode and every focus move.

* **Canvas mode** is where you land when you Tab into the editor. Arrow keys pan the view, `+` and `-` zoom, and `0` or `f` fits the graph to the view. Press **Enter** to switch to object mode.
* **Object mode** moves a selection around the graph. An arrow key moves to the nearest node or connection in that on-screen direction — a connection sits between the primary element and its node, so pressing the same arrow twice steps across it onto the node. The view follows the selection, so the focused item never scrolls out of sight.

While in object mode:

* **Home** jumps back to the primary element.
* **Enter** activates the selection: a node opens its context menu, a connection opens its relationship form, and a group expands or collapses.
* **Delete** removes the selected node's relationship.
* **Escape** dismisses an open tooltip or menu first; press it again to return to canvas mode, where arrows pan again.

A mouse click anywhere on the canvas also returns you to canvas mode.

## Single-character shortcuts

Some shortcuts are single keys, such as `/` to focus search and the Classic zoom keys `+`, `-`, `0`, and `f`. These are convenient but can get in the way of typing or assistive tools, so they are governed by a toggle. The Classic keys are only active while the canvas has focus, so they never interfere with typing elsewhere.

Turn **Single-character keyboard shortcuts** on or off in the [accessibility settings](/freelucy/personalize-and-accessibility/accessibility.md). When the toggle is off, single-key shortcuts such as `/` are disabled, while combination shortcuts like `Alt/Option + 1` keep working.

***

## What's next

* [Accessibility](/freelucy/personalize-and-accessibility/accessibility.md)
* [Choose a view](/freelucy/get-started/choose-a-view.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.ins-pi.com/freelucy/personalize-and-accessibility/keyboard-shortcuts.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.