Draft: POC for using API endpoints to retrieve any GL context

Tim Zallmannrequested to merge
tz-full-webpage-context into main

What does this merge request do and why?

related to gitlab-org/gitlab#579510 (closed)

POC Branch: Simulating full access to the instance API in the full scope of the user has.

This change adds two new general-purpose tools for interacting with GitLab's API and simplifies the available tools for chat workflows.

The new tools allow users to make direct GET requests to any GitLab API endpoint and execute GraphQL queries, providing more flexible access to GitLab data compared to the previous specialized tools. Instead of having separate tools for getting merge requests, projects, issues, etc., users can now use these two universal tools to fetch any data from GitLab.

The chat workflow has been updated to primarily use these new flexible tools while commenting out most of the old specialized tools, streamlining the available options and reducing complexity. This approach gives users more control and flexibility in accessing GitLab data while maintaining the same functionality through a simpler, more unified interface.

Uses now only 11k token for whole web agentic chat with mutation tools

image

image

image

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request checklist

  • Tests added for new functionality. If not, please raise an issue to follow up.
  • Documentation added/updated, if needed.
  • If this change requires executor implementation: verified that issues/MRs exist for both Go executor and Node executor or confirmed that changes are backward-compatible and don't break existing executor functionality.
Edited by Tim Zallmann

Merge request reports