anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 02:05:26 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE] Opencode's Bash tool selection should default to provider's CLI tol #8924

New Issue
Open
opened 2026-02-16 18:11:11 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:11:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @nweinshenker on GitHub (Feb 9, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Description

When using OpenCode with GitLab, the bash tool currently assumes GitHub CLI (gh) is available and should be used by default for repository operations. Looking at the bash.txt that builds the bash tool, we can maybe rely on the supported provider that the user /connects to for Git hosting i.e (GitHub, GitLab, etc...).

Example request when connected to GitLab provider models:

Image

Expected Behavior

Building a custom plugin or adding an agent skill for the GLab CLI tool seem to be a work around for OpenCode's default reliance using GH CLI features: https://opencode.ai/docs/skills/.
However, I'm wondering if we can infer information from the bash description to determine which provider to use.

Ideal end state

When connected via the /connect command, the LLM relies on the default provider CLI tool if it exists.
Use the appropriate CLI tool:

  • gh for GitHub repositories
  • glab for GitLab repositories

Environment Details

OpenCode Version: 1.1.53
Npm Version:: v22.21.1
Glab Version:: glab 1.80.4 (f4b518e9)

Originally created by @nweinshenker on GitHub (Feb 9, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request ## Description When using OpenCode with GitLab, the bash tool currently assumes GitHub CLI (gh) is available and should be used by default for repository operations. Looking at the `bash.txt` that builds the `bash` tool, we can maybe rely on the supported provider that the user `/connects` to for Git hosting i.e (GitHub, GitLab, etc...). Example request when connected to GitLab provider models: <img width="435" height="250" alt="Image" src="https://github.com/user-attachments/assets/b7c56765-03ef-41c3-9c7f-cf405b6dd230" /> ## Expected Behavior Building a [custom plugin](https://opencode.ai/docs/ecosystem#plugins) or adding an agent skill for the GLab CLI tool seem to be a work around for OpenCode's default reliance using GH CLI features: https://opencode.ai/docs/skills/. However, I'm wondering if we can infer information from the bash description to determine which provider to use. ### Ideal end state When connected via the /connect command, the LLM relies on the default provider CLI tool if it exists. Use the appropriate CLI tool: * gh for GitHub repositories * glab for GitLab repositories ## Environment Details **OpenCode Version:** 1.1.53 **Npm Version:**: v22.21.1 **Glab Version:**: glab 1.80.4 (f4b518e9)
yindo added the discussion label 2026-02-16 18:11:11 -05:00
yindo commented 2026-02-16 18:11:11 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 9, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #10607: [FEATURE]: GitLab Support - Addresses the fundamental gap that OpenCode lacks proper support for non-GitHub platforms like GitLab, which is the root cause of the bash tool defaulting to GitHub CLI tools

Feel free to ignore if this doesn't address your specific case.

@github-actions[bot] commented on GitHub (Feb 9, 2026): This issue might be a duplicate of existing issues. Please check: - #10607: [FEATURE]: GitLab Support - Addresses the fundamental gap that OpenCode lacks proper support for non-GitHub platforms like GitLab, which is the root cause of the bash tool defaulting to GitHub CLI tools Feel free to ignore if this doesn't address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8924
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?