GitLab

OpenCode integrates with your GitLab workflow through your GitLab CI/CD pipeline or with GitLab Duo.

In both cases, OpenCode will run on your GitLab runners.

---

GitLab CI

OpenCode works in a regular GitLab pipeline. You can build it into a pipeline as a CI component

Here we are using a community-created CI/CD component for OpenCode — nagyv/gitlab-opencode.

---

Features

• Use custom configuration per job: Configure OpenCode with a custom configuration directory, for example ./config/#custom-directory to enable or disable functionality per OpenCode invocation.
• Minimal setup: The CI component sets up OpenCode in the background, you only need to create the OpenCode configuration and the initial prompt.
• Flexible: The CI component supports several inputs for customizing its behavior

---

Setup

1. Store your OpenCode authentication JSON as a File type CI environment variables under Settings > CI/CD > Variables. Make sure to mark them as “Masked and hidden”.

2. Add the following to your .gitlab-ci.yml file.

   include:
     - component: $CI_SERVER_FQDN/nagyv/gitlab-opencode/opencode@2
       inputs:
         config_dir: ${CI_PROJECT_DIR}/opencode-config
         auth_json: $OPENCODE_AUTH_JSON # The variable name for your OpenCode authentication JSON
         command: optional-custom-command
         message: "Your prompt here"

For more inputs and use cases check out the docs for this component.

---

GitLab Duo

OpenCode integrates with your GitLab workflow. Mention @opencode in a comment, and OpenCode will execute tasks within your GitLab CI pipeline.

---

Features

• Triage issues: Ask OpenCode to look into an issue and explain it to you.
• Fix and implement: Ask OpenCode to fix an issue or implement a feature. It will create a new branch and raise a merge request with the changes.
• Secure: OpenCode runs on your GitLab runners.

---

Setup

OpenCode runs in your GitLab CI/CD pipeline, here’s what you’ll need to set it up:

Tip

Check out the GitLab docs for up to date instructions.

1. Configure your GitLab environment
2. Set up CI/CD
3. Get an AI model provider API key
4. Create a service account
5. Configure CI/CD variables
6. Create a flow config file

You can refer to the GitLab CLI agents docs for detailed instructions.

---

Examples

Here are some examples of how you can use OpenCode in GitLab.

Tip

You can configure to use a different trigger phrase than @opencode.

• Explain an issue

  Add this comment in a GitLab issue.

  @opencode explain this issue

  OpenCode will read the issue and reply with a clear explanation.

• Fix an issue

  In a GitLab issue, say:

  @opencode fix this

  OpenCode will create a new branch, implement the changes, and open a merge request with the changes.

• Review merge requests

  Leave the following comment on a GitLab merge request.

  @opencode review this merge request

  OpenCode will review the merge request and provide feedback.