> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/user-guides/fr/tips-and-tricks/keyboard-shortcuts.md).

# Raccourcis clavier

## Raccourcis clavier

Si vous préférez utiliser des raccourcis clavier plutôt que la souris pour rendre le remplissage automatique de vos mots de passe encore plus fluide, suivez les étapes ci-dessous :

1. Naviguer vers le site auquel vous souhaitez vous connecter.
2. Saisir **command+shift+k** (pour Mac OS) ou **alt+k** (pour Windows).
3. Dans le champ fourni, commencer à saisir vos termes de recherche.
4. Utiliser les **flèches haut et bas** de votre clavier pour trouver et mettre en surbrillance l'entrée que vous recherchez.
5. Utiliser la touche **entrée** pour remplir rapidement et se connecter au site.


---

# 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.keeper.io/user-guides/fr/tips-and-tricks/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.