Skip to content
Bunkhouse Docs

Discovery cache

By default every session discovers skills from scratch. The discovery cache lets you, the site owner, publish a reviewed capability manifest so new sessions start with that functionality already available to the assistant. It is off until you enable it for a site.

What a manifest contains

Section titled “What a manifest contains”

A manifest holds sanitized descriptions of skills: API request descriptors, UI recipes from your hints and WebMCP tool bindings. It never contains credentials or authorization headers, record IDs or values, conversation transcripts, approvals or page-specific element references.

Scope

Section titled “Scope”

Each manifest applies to one exact scope:

  • your account and site;
  • the exact page origin;
  • a context profile (below);
  • the discovery version, manifest format and a digest of your current hints file.

Changing your hints file or bumping the site’s discovery version means sessions stop using older manifests until a matching one is published.

Context profiles

Section titled “Context profiles”

The context profile decides which users share a manifest:

  • Anonymous sessions use the public profile.
  • Signed sessions default to a profile of their own user.
  • Your backend may assign a shared profile from its own permissions, for example everyone with the same role. The name is 1-64 characters from A-Z a-z 0-9 . _ -.
    • Identity token: add a signed ctx claim, such as "ctx": "admin", to the identity token.
    • Server mint: send "contextProfile": "admin" in the session request.

The profile always comes from your backend. Assign a shared profile only to users who are allowed to see the same capabilities.

Publishing

Section titled “Publishing”
  1. Enable the discovery cache in the site’s setup in the dashboard.
  2. Signed sessions submit candidate manifests for their own scope. You can also export a sanitized file from the assistant’s Skills view and import it in the dashboard.
  3. Review candidates and publish one under Site setup → Discovery cache. Only the owner can publish.

Publishing is checked against the revision you reviewed: if someone else published in the meantime, the dashboard reports a conflict (HTTP 409) and you review again. A published manifest expires after seven days.

Next steps

Section titled “Next steps”