Skip to content

basemodo recognize

Have a Public App ask visitors already signed in to Basemodo to continue as themselves (on), let them in as Guests again (off), or say which.

Terminal window
basemodo recognize [OPTIONS] [on|off]

Anyone opens a Public App with no sign-in, and its Toolbar shows them as Guests; someone signed in to Basemodo stays a Guest until they press Sign in. With Recognize on, they are asked once, the first time they open the App, whether to continue as themselves (the App then learns their email), and go straight in after; Cancel leaves them a Guest. Turn it on only when the App needs to know who its visitors are. It is off for every App, and does something only while the App is Public: every other Visibility asks anyway. [web] recognize = true in basemodo.toml turns it on when that Deploy goes live. The Owner or an Editor changes it.

Arguments

  • on|off: on has a Public App ask visitors signed in to Basemodo once to continue as themselves, off lets them in as Guests; its Owner or an Editor turns it. Without it, only show whether it is on.
  • --app <APP>: The App. Default: the one named after the current folder.

Like every command, it also takes the global options --json and --api-url.

Examples

Have the App of this folder recognize visitors signed in to Basemodo:

Terminal window
basemodo recognize on

Let them in as Guests again:

Terminal window
basemodo recognize off

Say whether an App recognizes them:

Terminal window
basemodo recognize --app lunch-rota

Output

With --json, it prints {"app", "url", "recognize"}, after the change. A Member is refused with code owner_or_editor_only.

From an agent

Basemodo's MCP serves it as the tool recognize. It changes things, so an agent's client may ask you before it runs. Its arguments are the command's, named as JSON keys: turn (text), app (text). It answers what the command prints with --json.

Explained in