VisuaLeaf Blank Activity
Blank Activity is what a fresh tab looks like in VisuaLeaf. Big centered search, three category dropdowns underneath, and no MongoDB or SQL context pinned to it — a scratchpad you can drive to any collection, table, or command in the workspace. Under the hood it embeds the Command Palette and filters it down to the three categories you're most likely to want from a new tab: Create, Saved, and Navigate.
Open a blank tab and jump wherever you want:
The page is a single centered column with two blocks:
A full-width input with the placeholder "Collection, database, or command...". Focus and click both open the results dropdown; blur closes it after a short delay so a click on a result still lands. Below the input, a small hint reminds you that ↵ selects and ↑/↓ navigate.
Row of three buttons directly under the search. Each button carries the category's item count and expands into a scrollable panel of every item in that category.
| Button | Palette category | Icon | Accent color |
|---|---|---|---|
| Create | Create | fa-solid fa-plus |
emerald |
| Saved | Saved Items | fa-solid fa-bookmark |
amber |
| Navigate | Navigation | fa-regular fa-compass |
sky |
Only one dropdown can be open at a time. Clicking an already-open button collapses it. Opening a dropdown also clears any active search query so the panel owns the screen without competing with search results.
Blank Activity is designed to sit between workflows, not inside one. Common uses:
The Command Palette exposes seven categories in total. Blank Activity intentionally shows just three of them because the other four are already at your fingertips in the surrounding chrome:
Search only walks items in Create, Saved Items, Navigation, and Collections / Tables. Items from the excluded categories (Workspace, Settings, Account) never show up in Blank Activity's results even if their labels or keywords would match.
A query matches if it appears (case-insensitively) in any of:
label,category,description,keywords.Blank Activity caps the number of rows it mounts in the dropdown at 80. Search itself still walks the full item list — only the rendered slice is bounded, so short queries stay snappy even in workspaces with thousands of collections and tables. The moment the 80th match is found, the search short-circuits and stops scanning.
When the input is focused but empty (either right after mounting or after deleting your query), the dropdown fills with the top slice of Collections / Tables instead of going blank. This mirrors the "type nothing, see something" behavior you'd want from a jump-to-collection launcher.
The two views are mutually exclusive:
Collection and table result rows carry the same inline chip strip as the Command Palette — Documents, Aggregator, Shell, Schema, Charts, Indexes, Export, Import for Mongo; Rows, Schema, Editor, Constraints, Export, Import for SQL. Clicking a chip runs that sub-action instead of the row's main action, so you can jump straight to indexes or the aggregation builder without opening the collection view first.
Running a result doesn't append a new tab. Instead, the Blank Activity swaps itself out and the opened activity takes its place in the exact same panel slot — so if you split-paned four panels and hit "+" on the third, the new collection view lands in that same third pane. If the action opens a modal instead of an activity (like New Connection), the blank tab is simply removed.
The search input owns the keyboard while it's focused — global shortcuts elsewhere in the workspace are not intercepted.
| Key | Action |
|---|---|
| Enter | Run the highlighted result. |
| ↑ / ↓ | Move the active result up or down (wraps around). |
| Esc | Clear the query. If the query is already empty, does nothing (the blank tab stays open). |
Download and start managing your MongoDB databases with ease.
Download Free Trial