basemodo callers add
Let another App of the same Owner call this one: name it a Caller.
basemodo callers add [OPTIONS] <CALLER>It then reaches the paths this App exposes to its Callers ([callers] paths in basemodo.toml), as itself, without a token; naming it opens nothing else, and nothing when no path is exposed. Both Apps must have the same Owner; an App of another Owner calls through a Public Path instead. The Owner and the App's Editors name Callers.
Arguments
CALLER(required): The App that will call: its name among the Owner's Apps, or its slug.--app <APP>: The App to be called, whose Callers to change. Default: the one named after the current folder.
Like every command, it also takes the global options --json and --api-url.
Examples
Let the reports App call the App of this folder:
basemodo callers add reportsLet it call the crm App:
basemodo callers add reports --app crmOutput
With --json, it prints {"callers": [{"app", "name", "slug", "named_by", "named_at"}], "paths" (the paths exposed to them), "changes": [{"app", "name", "action" (named or removed), "by", "reason" (why a Transfer took it off), "at"}]}. An App of another Owner is an error with code caller_of_another_owner.
From an agent
Basemodo's MCP serves it as the tool callers_add. It changes things, so an agent's client may ask you before it runs. Its arguments are the command's, named as JSON keys: caller (text), app (text). It answers what the command prints with --json.