> 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/getting-started/start-from-steam.md).

# Start Kouch from Steam

Why Kouch should always be started from Steam, and what happens when it isn't.

**Always start Kouch from your Steam library.** Kouch reads your controllers through Steam Input, and Steam only turns Steam Input on for a program it started itself.

## What you get when Steam starts Kouch

* **Every controller Steam knows**, including the Steam Controller and the Steam Deck's own controls.
* **Motion** from every controller that has it, for up to 8 players.
* **Steam's button glyphs** for **Match each controller**, so the prompts on screen can match the controller in your hands.
* **Your Steam profile and friends** in Kouch's top bar.

## If you start Kouch another way

Kouch still opens if you start it from the Start menu, a desktop shortcut or a file manager, but:

* It only sees the controllers your system reads directly. Controllers that only work through Steam don't show up, and motion only comes from controllers your system can read it from.
* Steam's **desktop controller layout** is still active, so a controller moves the mouse and sends key presses at the same time as Kouch reads it. Kouch filters that double input out in its own menus, but emulators may still see it.
* Kouch shows **"For controllers, start Kouch from Steam"** the first time it notices.

If that happens, close Kouch and start it again from Steam.

## Kouch and the Steam overlay

Kouch doesn't need the Steam overlay to work, and it doesn't replace it. You open Kouch's own [Quick Menu](/playing/quick-menu.md) during a game by holding **Select + Start**. Steam's own button still opens Steam's menus as usual.


---

# 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/getting-started/start-from-steam.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.
