AI co-pilot
The co-pilot is a chat panel inside the studio. A member asks in plain words, such as "make day two shorter" or "add a waypoint at the refuge", and the model edits the open itinerary or zone.
Opt-in- An AI provider for the organization. An owner or admin configures the provider, model and API key under Organization → AI co-pilot in the Mountaya app. Runs are billed by your provider, on that key.
- The
copilotfeature in your agreement, for members with a write role. - A member token. The co-pilot acts as the member the session token names, like every edit.
State behavior.copilot on the host, and give the host a viewer that holds the copilot feature. The editor then offers a co-pilot tab.
Your function answers per organization. Report configured and writable from what you know, and return a withheldNotice to explain, in your words, why the co-pilot is off.
The co-pilot changes the studio only by dispatching verbs on the tool bus, as a click does. It sees the verbs the member's grants allow, minus a few the studio keeps for people, such as publishing and share links.
While a run is driving, the studio's other controls go inert until it ends.
A destructive verb asks the member first, whether a click or the co-pilot dispatched it. The model cannot approve its own call: the member sees the same confirm dialog, and a "no" refuses the call.
MountayaStudio places the co-pilot panel for you. In a layout of your own, mount CopilotPanel from @mountaya/studio-react/copilot, and open a co-pilot tab by dispatching studio.tabs.open with { kind: "copilot" }.
AgentEngine of @mountaya/elements/agent runs a conversation over any bus and context, for a product that draws its own chat. When the run's stream answers 503, the engine keeps reopening it for up to two minutes before it reports the error.