Aamu.app has keyboard shortcuts for the actions you repeat all day: moving between sections, creating new items, navigating lists, selecting items, closing tasks or tickets, and opening comment panels.
The shortcuts are intentionally contextual. A key usually activates the visible button or item for the current view. That keeps the same habit useful across Tasks, Docs, Emails, Helpdesk, Meetings, Forms, Databases, Files, Designs, Chat, and Posts.
Shortcuts are visible in the UI
Many Aamu buttons show their shortcut in the tooltip. For example, a create button may say New doc [c], Compose new email [c], or New meeting [c].
This is the best way to learn shortcuts: hover the control you already use and notice the key in brackets.
When shortcuts do not run
Aamu avoids running global shortcuts while you are typing into an input, textarea, editor, or checkbox. That means ordinary writing should not accidentally navigate away or close an item.
In practice: if your cursor is inside a text field, the text field gets the key. If you are on the page itself, Aamu can use the key as a shortcut.
Navigation shortcuts
The sidebar has number shortcuts for the main sections. The exact sections depend on which apps your team has enabled, but the common mapping is:
1Home2Posts or AI, depending on the enabled sidebar layout3Chats4Tasks5Helpdesk6Emails7Designs8Meetings9Docs0Databases
Because teams can enable and disable apps, treat the visible sidebar as the source of truth. If a section shows a keyboard hint, that is the shortcut for your current workspace.
Create with C
c is the main contextual create shortcut. It activates the visible create/compose button in the current section.
Examples:
in Docs,
ccreates a new Doc,in Tasks,
ccreates or resumes a new task,in Emails,
ccomposes a new email,in Meetings,
ccreates a new meeting,in Forms,
ccreates a new form,in Databases,
ccreates a new database, andin Posts, Chat, Git, AI, and other sections,
cfollows the visible create action for that section.
This is more reliable than memorizing separate create keys for every app.
Move through lists
Most item lists support keyboard selection. Use the arrow keys to move the selected item up or down in the current list.
When the selected item moves out of view, Aamu scrolls it back into view. This makes long lists easier to scan without reaching for the mouse after every item.
Select and bulk-handle items
In item lists, s or . can select the current item when the list supports selection. This is useful before using bulk actions.
Esc can unselect items when a selection toolbar is active.
Shift with arrow navigation can also help select while moving in supported lists.
Close, reopen, delete, or toggle with X
x is used as a contextual toggle/action shortcut in several item views.
Examples include:
closing or reopening a task,
closing or reopening a Helpdesk ticket,
acting on the currently selected item when a supported list/action is visible.
Because x is contextual, check the visible button tooltip. If the UI says Close [x] or Close and resolve [x], that is the action that will run.
Reply, read, and section-specific keys
Some sections use additional shortcuts for their own workflow. For example, Emails has shortcuts around read/unread or message actions, and some comment/reply areas expose their own keys.
These are best learned from the visible controls, because the action depends on the current section and selection.
Internal comments with Alt+C
Some work items have an internal comments panel. Where the UI exposes it, Alt+C can open or close that internal comments area.
This is especially useful in Helpdesk and database-style workflows where internal discussion should stay separate from customer-facing or public content.
Preview with Alt+W
Some textarea/editor contexts use Alt+W for preview. This is handled separately so it can work in writing contexts where normal global shortcuts are disabled.
Keyboard-first, not keyboard-only
Aamu's shortcuts are meant to make repeated work faster, not to hide the UI. You can always use the visible buttons and menus. The shortcut simply clicks the same visible action when it is available and unobstructed.
That design matters. It keeps shortcuts discoverable, contextual, and safer than a global command system that fires regardless of what is on screen.
A practical way to learn them
Use number keys for the sections you visit most.
Use
cto create in the current section.Use arrow keys to move through lists.
Use
sor.when selecting list items.Use
xonly when the visible action says what it will do.Watch button tooltips for the shortcut hints.
After a little practice, the app starts to feel much faster because the same few keys work across many parts of the workspace.
