Search what you copied, not only what is current
Clipboard history is useful when it remains easy to scan. Axiom separates copied text, links, images, and other entries while keeping the newest and frequently used content close. The workspace follows the same visual language as the rest of the app rather than behaving like a detached utility.
Bulk controls and lifecycle rules should update the visible list immediately. Removing an item should not leave a stale row waiting for another interaction to redraw the screen.
Reusable text with names and deliberate triggers
A snippet has three distinct pieces: a human-readable name, the text that will be inserted, and an optional trigger keyword. The trigger can replace typed text in another app when the required system permission is available.
From the Snippets list, Return opens editing by default. Context actions can create or edit a snippet, while the list shows the name on the left and a useful preview of the actual content on the right.
- Name for recognition
- Content for insertion
- Trigger for replacement
- Default Return action opens editing
Emoji and GIFs that become faster with use
Emoji and GIF search uses a visual grid, keyboard navigation, visible selection, and a frequently used section. GIF results load incrementally as the user scrolls, prioritize what is visible first, and preserve the original aspect ratio inside a full visual tile.
Provider attribution belongs in Settings rather than competing with the search task. The workspace says “Search GIFs,” while provider details remain available where configuration lives.
Common questions
Can a snippet have both a trigger and a shortcut?
Yes. They are different fields and can be configured independently without creating duplicate search results.
Does Axiom remember frequently used GIFs?
Selected GIFs can appear in a frequently used section similar to the emoji workflow.
Can I exclude sensitive clipboard entries?
Clipboard behavior depends on the controls available in the installed build; sensitive data should never be described as protected without verifying those settings.