Get it for macOS

Shows the merge and pull requests a thread opened, with live state and pipeline status, in the thread context card and Info tab. It finds each GitLab MR or GitHub PR that the thread's own commands created (glab mr create, gh pr create, git push -o merge_request.create), lists it with a Draft, Open, Merged or Closed chip and a pass, fail or running pipeline mark, and opens it on click. Rows refresh every minute and from a refresh button; agents get bb session-mrs list and bb session-mrs status <url>. Read-only: it needs glab and/or gh logged in on the machine that runs the BB server.


Overview

View source

See every merge or pull request the current thread created, with live state, pipeline status and a clickable link, in the thread context card and the Info tab, and from the bb session-mrs command.

What you get

  • A Merge requests section listing each GitLab MR or GitHub PR the thread created, with a Draft / Open / Merged / Closed chip and a pipeline result.
  • bb session-mrs list and bb session-mrs status <url> for agents.

How it works

Status comes from the glab and gh logins already on the machine that runs the BB server. The plugin is read-only and stores nothing.

More from JonniK

Bang ShellRun a shell command from a thread's composer and hand the agent the command and its output in one message. Use it when the agent's sandbox or permission mode blocks a command that needs your secrets or access: the agent proposes it, you run it, and the agent only sees the output. Send with Mod+Alt+Enter or Send menu → Run in terminal; the command runs once in the thread's own environment, on whichever machine the session uses, local or remote. You can also highlight a command in an agent's answer and pick Run in terminal next to Add to chat. Fenced shell code blocks in an answer also get a one-click Run in terminal button; python blocks get it once you turn on the runPythonBlocks setting. The message waits in the queue while the command runs, then reaches the agent as a sh block and an output block, so its next answer starts from the real result. Commands that outlast the wait (30 seconds by default) keep running in the thread's Terminal panel, and pagers are off so git log and git diff print in full. Messages from agents, other plugins and bb thread tell never run a command; commands run with your account's full rights, outside the agent's permission mode. Requires bb 0.49+ and a POSIX shell (macOS or Linux; Windows is not supported).NewBottom PanelPuts bb's App panel, with its terminal, browser tabs and previews, below the chat like an IDE, and lets you resize it by dragging the divider. Select text in the terminal and press Cmd+L (Ctrl+L on Windows and Linux) to drop it into the chat composer without sending it, also on non-Latin layouts. One header button switches back to the native right panel. Needs no account or external service.NewSkill DialRun your go-to skills in one tap from chips beside the send button, instead of typing them through the / menu each time. Each chip either drops its skill, with preset arguments, into your draft or sends it right away. Select text in the chat or in your draft first, and the chip passes it to the skill as the argument. Add as many chips as you need in the plugin settings; they scroll sideways, fold into one toggle, and shrink to emoji on phones. Needs no account or external service.New

More in Code & Reviews 63

Work with repositories, builds, changes, pull requests, issues, and reviews.

View all