Keyboard shortcuts

Scrolling

dorCtrl+d
Scroll down
uorCtrl+u
Scroll up
Ctrl+e
One line down
Ctrl+y
One line up
gtheng
Top of article
G
Bottom of article

Articles

j
Older article
k
Newer article
O
Open original
H
Open hackernews
R
Open reddit

Lists

jor↓
Next item
kor↑
Previous item
gtheng
First item
G
Last item
oorEnter
Open selected item

Go to

gthenforgtheni
Feed
gthen1–9
Open feed entry
gthenb
Browse
gthenp
Preferences

Search and help

⌘+kCtrl+kor/
Global search
?
Show this help
Esc
Close this help

GitLab Integration

ampcode.com original

Amp now integrates with GitLab, on gitlab.com and on self-managed instances.

Connect your GitLab account and you can start projects from your GitLab repositories. Orbs clone and push as you and come with glab signed in, so the agent can open merge requests, comment on them, and read issues and pipelines.

Amp can also subscribe to comments and CI for a merge request it opens. A reviewer's request or a failed pipeline lands in the thread that wrote the code, so Amp already has the context.

An Amp thread receiving a comment on merge request !1 in amp-test/api, wrapping the README at 100 columns as the reviewer asked, then receiving the CI result: all pipelines complete An Amp thread receiving a comment on merge request !1 in amp-test/api, wrapping the README at 100 columns as the reviewer asked, then receiving the CI result: all pipelines complete

A New Orb for Every New Merge Request or Issue#

Ask Amp to start a new orb for every new merge request or issue in a project. You don't need to keep the thread where you set it up. See Create an Orb Spawner.

Each new merge request or issue gets its own orb, which reads it and has a summary ready when you open the thread. Later comments go to that same thread. Workspace admins can also run a spawner as a service account.

You manage all of these in Settings → Integrations & MCP → GitLab under Event Subscriptions, where you can pause or delete them, edit a spawner, and see the orbs each spawner started.

The GitLab Event Subscriptions table in Settings with a spawner for new amp-test/api issues expanded to show its Spawned Orbs, above subscriptions to issue #5, issue #1, and merge request !1 The GitLab Event Subscriptions table in Settings with a spawner for new amp-test/api issues expanded to show its Spawned Orbs, above subscriptions to issue #5, issue #1, and merge request !1

Set It Up#

Each person connects GitLab in Settings → Integrations & MCP. Then a group Owner installs Push Updates once for the workspace, with one button in Workspace Settings → Integrations & MCP.

Amp also supports self-managed GitLab. See Self-Managed Instances.

Connect GitLab to get started.