The command palette is the one to learn first: it finds every action and every discussion, so you do not have to remember the rest.
| What | Keys |
|---|---|
| Command palette | Cmd/Ctrl + K |
| New discussion | Cmd/Ctrl + N |
| Send | Enter |
| New line | Shift + Enter |
| Stop the run | Esc |
| Search discussions | Cmd/Ctrl + F |
| Settings | Cmd + , |
In the composer
- Start a message with a seat's name — "@gemini …" — to ask that seat alone. One pass, no review.
@guestopens the catalogue: pick a model and it answers once as a guest./nameruns one of your skills, wrapping the message in the instructions it holds./comment …leaves a note for your team in the transcript that the room never answers.- Drag a file, or paste an image, straight onto the composer.
While a run is going
You can keep typing. What you send is picked up at the next turn boundary rather than interrupting the seat mid-sentence or being thrown away — so a correction you think of halfway through lands in the same discussion.
The full list
The current bindings live in the app's own help, written beside the code that binds them: the help centre. The palette is worth the habit either way; it finds everything the menus do and every discussion you have.