## Problem Duo Developer and other Remote Flows when they can use `run_command` they can already theoretically do anything their token allows via using `curl` or similar commands. Currently we're adding individual tools to those (e.g. `create_mr`, `read_issue`) to interact with GitLab. While those tools are theoretically faster they consume additional tokens. Additionally, agents/llm's are known for being optimized to run bash commands and work with CLIs but getting API calls right can still be tricky, especially if it's not easy to get the API documentation. The big advantage of running bash commands is that the agent can also directly work with results locally without needing another LLM call. E.g. it can directly pipe large results into grep to narrow down results before they are sent to the LLM. Many developers already use the [GLAB CLI](https://docs.gitlab.com/cli/) directly with agents so that they can interact better with GitLab. ## Desired Outcome `glab` is automatically available for any flow. So that if it can run commands it can use this to interact with GitLab rather than specific tools.