Skip to content

Web search: curate allowlist/denylist #690

Description

@hanna-paasivirta

Follow-up on #664

With a very limited allowlist, the assistant may try to search for external information several times, trying to find relevant urls it is allowed to open. For example, with just OpenFn documentation in the allowlist, and the user question "What is the latest format for tracked entity attributes according to the DHIS2 API? I need the exact field names", the assistant is likely to spend all of its allowed tool uses trying to find the information within OpenFn urls.

We should optimise the allowlist and prompts/tool use descriptions to avoid having the model stall at search attempts.

Create a couple of acceptance tests, but we should also test the internal tool use behaviour and not just the answer.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions