chatbot setup

Versions and host UI API

Check the registry for the plugin's current version. The current browser bundle requires plugin UI API 62 and shared API 16. Install the core release that the plugin's manifest requires before you install this plugin; the manifest currently asks for Chetty 0.30.47 or newer.

Bot UI requirements are declared in the manifest (requiresCore, requiresSharedApi, web.requiresApiVersion), so an incompatible combination is refused at install rather than at the first visitor message.

Account and Project commit

Core commits the chatbot account and its managed-Project membership together, so an account never exists without the Project that will own its transcript. An existing chatbot account receives the chosen membership before its grants are saved.

The create flow reports which step failed — creating the account, assigning the Project, granting the account's tools or registering the chatbot — and keeps the account it already made, so the operator corrects that one step instead of starting again.

Admission then opens a real Elowen turn owned by the chatbot account through the host relay; the plugin never calls a model itself.

Spend accounting

Daily and monthly spend come from Elowen's own origin-attributed usage rollup, not from a separate meter. Dictation is billed to the same account and appears in the same rollup, which is why one pair of spend ceilings covers both text answers and live dictation.

Spending is checked before a turn or a dictation starts and is never reserved in advance, so work already running can pass a ceiling.

Bundle requests and shared settings

The browser bundle edits the instance-wide visitor-token lifetime through the host's configuration editor, sends structured JSON requests and uses the host's literal text interpolation.

Domains, limits, appearance and form-submission permission stay per-chatbot settings and never travel through that editor.