> For the complete documentation index, see [llms.txt](https://docs.kouch.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kouch.dev/controllers/keyboard-and-mouse.md).

# Keyboard and mouse as a player

Use a keyboard and mouse as a player, change its keys, and use the mouse as a stick or as motion.

A keyboard and mouse can be a player, just like a controller. That's handy on a desk, or for one more player when you've run out of controllers.

{% hint style="info" %}
This is different from **using** Kouch with a keyboard and mouse. The arrow keys, **Enter** and **Esc** always move around Kouch's menus. See [Finding your way around](/getting-started/finding-your-way.md#keyboard-and-mouse). This page is about the keyboard **playing games** as a seated player.
{% endhint %}

## Turn it on

1. Open **Settings › Controllers**.
2. Turn on **Use keyboard and mouse as a player**.
3. Go to the Players screen. The keyboard has its own box. Press **Enter** to join.

It keeps working while an emulator has the focus, on Windows and on the Steam Deck.

{% hint style="warning" %}
**Double presses.** An emulator that reads the keyboard itself sees these keys too. Turn off the emulator's own keyboard input to avoid pressing everything twice.
{% endhint %}

## The keys

| Keys                   | Controller input         |
| ---------------------- | ------------------------ |
| **W A S D**            | Left stick               |
| **Arrow keys**         | D-pad                    |
| **K** or **Enter**     | A                        |
| **L** or **Backspace** | B                        |
| **J**                  | X                        |
| **I**                  | Y                        |
| **U** / **O**          | LB / RB                  |
| **Q** / **E**          | LT / RT                  |
| **Tab**                | Select                   |
| **P**                  | Start                    |
| **F** / **H**          | Left / right stick click |

### Change a key

1. In **Settings › Controllers › Keys**, highlight a button and press **A** (or **Enter**).
2. Press the key you want. **Esc** cancels.

A button with no key shows **Not set**. **Reset keys to default** puts every key back.

## The mouse

Choose what the mouse does:

* **Mouse moves the right stick** (default): for games that look around with the right stick.
* **Mouse acts as motion:** moving the mouse tilts the controller, for games that aim with motion.
* **Mouse does nothing.**

**Mouse sensitivity** goes from 0.1× to 4×. While the mouse is on, **left click** is **RT**, **right click** is **LT** and **middle click** is the right stick click.

## On the Steam Deck

Kouch reads the keyboard and mouse with no setup. One exception: if an emulator runs outside the desktop's display system and the keys stop reaching Kouch while it plays, you can give your user access to input devices from Desktop Mode's terminal:

```sh
sudo usermod -aG input $USER
```

Then log out and back in. That lets any program you run read your keyboards and mice, so only do it if you need it.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kouch.dev/controllers/keyboard-and-mouse.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.