Shimpz
First useful result

Add one capability to your Team

An Assistant gives the Team one or more focused Actions. Install only the Assistant you need, then ask for the result in normal language.

  1. Install the Assistant

    Select the Team in the Team list, open Assistants, and choose Install or replace on the Assistant's catalog card. The confirmation dialog shows the Destination Team; check that it is the Team you selected, then choose Confirm install. Continue when Admin reports Assistant installed.

  2. Ask for one useful result

    Open Chat for the same Team and ask for the outcome in normal language, naming the installed Assistant. For example, a DNS Assistant might receive:

    Use the installed DNS Assistant to list the zones I can access.

    If private access is necessary, the turn pauses and shows the exact requirement.

  3. Provide only what the Action requests

    If an Integration is required, choose Continue, review the provider and scopes, and approve on the provider's website. If a third-party private value is required, Shimpz shows one bounded request form. The same conversation continues after the requirement is satisfied.

  4. Confirm the result, then ask a follow-up

    The turn is complete when Chat shows the Team's complete response with no human request still pending. If the response contains a list or table, choose one returned value for a follow-up:

    Show me more details about the first result.

    Private values are submitted from the dedicated form only to the exact selected Action. Shimpz does not add them to the Brain context, chat transcript, or chat response.

Automatic maintenance

Local keeps installed Assistants current

When a newer reviewed publication is available, Local verifies its exact immutable image and updates every Team using the older version. The current Assistant stays available if Shimpz is offline, the Team is busy, or the replacement cannot be proved safe; Shimpz retries later.

An update can remove permissions automatically, but it cannot silently add a network host, Integration, provider, or OAuth scope. Broader access requires your approval. After a successful replacement, Shimpz removes the old Assistant container and its unused image and policy state without pruning unrelated Docker data.

Blocking a publication prevents new installations but does not remotely stop a copy that is already running in your Local Space. If a security notice requires immediate removal, the Local Supervisor must uninstall that Assistant instead of waiting for a newer safe version.

If something does not work

Check the visible state first

  • No Assistant in chat: return to Assistants and confirm it is installed in this Team.
  • Install refused for a full Team: a Team holds at most 16 Assistants. Uninstall one from this Team, or install into another Team.
  • No authorization window: allow pop-ups for the local Admin and send the message again.
  • Wrong Integration: disconnect it, then authorize the correct provider identity.
  • Model keeps thinking: verify the Team's model API key, then retry the message once.
Remove access

Disconnect before uninstalling

Disconnect any Integration to revoke its provider grant, then uninstall the Assistant. A third-party password you type for a single request is not kept. A value the Assistant keeps as a Stored Input, such as a WhatsApp token, stays encrypted for that Team: clear it under Assistant integrations in the chat, or uninstall the Assistant, which removes it. Uninstalling the Assistant does not delete the Team or its conversation history.