Docs

Chat-first installs

Install and connect agents from chat.

Users should not have to browse the Orchet Store to make a request work. If a required capability is missing, Orchet pauses the task and renders the right connect surface inline.

The principle.

The chat thread is the primary install surface. The Orchet Store is for discovery, trust context, and developer review, not a required setup detour.

  • The user asks for the real outcome, such as checking groups or booking a ride.
  • Orchet detects the required approved agent and checks install/connection status.
  • If missing, Orchet renders a connect card in the assistant message.
  • After OAuth or install succeeds, Orchet resumes the original request when it is still safe to do so.

Connect card contract.

A connect card must carry the agent identity, OAuth start URL, user-facing scope copy, and the original intent that should resume after authorization.

JSON

{
  "type": "connection_required",
  "agent_id": "splitwise",
  "display_name": "Splitwise",
  "reason": "Read groups and create expenses",
  "requested_scopes": [
    "View groups and balances",
    "Create expenses after confirmation"
  ],
  "resume_prompt": "Check my Splitwise groups"
}

Do not tell users to go elsewhere.

Assistant copy should say, for example, 'Tap Connect Splitwise below to sign in, then I'll continue.' It should not tell the user to manually visit the Orchet Store.