Presence avatars

What it adds to your app

Component PresenceAvatars (props: room, max, label). Two presence channels: per record and per page. A Who's here page.

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.

   Param	What it is	Example
   entity	The table whose record pages show who is viewing them.	ticket
   page_role	The role the sample page is for. Optional.	agent

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.

Add the Presence avatars template (slug "presence-avatars") 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: records; page_role: who sees the who's here page).

{
  "tool": "use_template",
  "arguments": {
    "slug": "presence-avatars",
    "project_id": "<your project id>",
    "params": {
      "entity": "ticket",
      "page_role": "agent"
    },
    "dry_run": true
  }
}

appbricx templates use presence-avatars --param entity=ticket --param page_role=agent --dry-run