Command palette

Every appbricx app already has a Cmd/Ctrl+K palette that jumps to pages and records. This component adds the part people act with: a visible search bar (so it works on touch screens) that opens a palette with server-side search over one or two of your tables, then actions on the record you pick: open it, move its status to the next stage, or delete it, each only when the role may. Quick create makes a new record from the palette with just its title and required fields, and you can list your own shortcuts to pages. Press / anywhere on the page to open it.

View the files
Command palette: the Quick actions page, added to Relay, on desktopCommand palette: the Quick actions page, added to Relay, on a phone

What it adds to your app

Component CommandBar (props: entity, titleField, fields, detailRoute, entity2, pages). A Quick actions page for the role you choose.

Pages

  • /quick-actions Quick actions (‹page_role›)

Components

  • CommandBar A search bar that opens a command palette (also with /): find ‹entity› records on the server, create one in place, move its status on, open or delete it, and jump to pages; works on phones

Set it up

It merges into the contract of an app you already have. Nothing is overwritten: a name you already use is refused until you pass a prefix.

  1. Pick the project

    Use the button above, or ask your coding agent with the Appbricx MCP server connected (quickstart).

  2. Point it at your tables and roles

    Leave out the ones with defaults; a wrong one is refused with the options your app has.

    ParamWhat it isExample
    entityThe table whose records the palette finds and acts on.job
    entity_2Optional: a second table to search alongside it. Optional.customer
    page_roleThe role the Quick actions page is for. Optional.staff
  3. Preview, then apply to dev

    A dry run shows the diff and the check report; applying it changes your dev environment only.

  4. Deploy

    When dev looks right, deploy. Production gets a snapshot first, so you can roll back.

Use it with your coding agent

The agent reads the template, runs a dry run, shows you the diff and applies it.

Prompt
Add the Command palette template (slug "command-palette") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (entity: table to search; entity_2: second table (optional); page_role: who sees quick actions).
MCP call
{
  "tool": "use_template",
  "arguments": {
    "slug": "command-palette",
    "project_id": "<your project id>",
    "params": {
      "entity": "job",
      "entity_2": "customer",
      "page_role": "staff"
    },
    "dry_run": true
  }
}
CLI
appbricx templates use command-palette --param entity=job --param entity_2=customer --param page_role=staff --dry-run

Your agent adds it. Appbricx runs it.

Start freeAll templates