Cost control: a monthly token allowance for each modelSee how it works
memtro
Start for free

Semaphore CI + Memtro

Why did the last build fail, and which tests are flaky?

Semaphore CI shows you a project's workflows and pipelines by branch and time, with state, result, duration and failure reason. It reads a pipeline's jobs, a job's commands with exit codes, deployment targets, pipeline insights and flaky tests. When asked and granted, it can run, rerun or stop a workflow, stop a pipeline or job, and rebuild failed blocks. It can also trigger a promotion, run a task, and activate or deactivate a deployment target. Semaphore can tell Memtro as it happens when a pipeline finishes, and a job can start on it. Self-hosted editions are not supported.

Connect Semaphore CIStart for freeReference
In Memtro

What you can do with Semaphore CI in Memtro

Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Semaphore CI tool, reads what it needs, and answers with the source cited.

What it does

  1. 01Lists workflows and pipelines by branch and time with state, result and duration.
  2. 02Reads a pipeline's blocks and jobs, and a job's commands with exit codes and the first failing one.
  3. 03Reads promotions, deployment targets, pipeline duration and pass rate, and flaky tests.
  4. 04When asked and granted, runs, reruns or stops a workflow, stops a pipeline or job, or rebuilds failed blocks, using CI minutes.
  5. 05When asked and granted, triggers a promotion, usually a deploy, runs a task, or activates or deactivates a deployment target.
  6. 06With events on, a pipeline that passed, failed, stopped or was canceled in Semaphore CI can start a job.

Acts when asked

When you ask it to

These tools change something in Semaphore CI. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.

  1. 01Run a workflow on a branch, tag or pull request
  2. 02Rerun a workflow
  3. 03Stop a running workflow
  4. 04Stop a running pipeline
  5. 05Rebuild a pipeline's failed blocks
  6. 06Trigger a promotion (deploy) of a pipeline
  7. 07Run a task now
  8. 08Stop a running job
  9. 09Deactivate a deployment target
  10. 10Activate a deployment target

Events

When it happens

Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Semaphore CI, choosing the same kinds; the tab shows Semaphore CI's own steps. Each event can start a job, with the event as its input. Semaphore CI signs every delivery, and one whose signature does not check out is refused before it is read.

Events and webhooks
  • 01A pipeline finished (passed, failed, stopped or canceled)
In practice

Ask it like you would a colleague

Once Semaphore CI is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.

Semaphore CI + Memtro

  • Why did the last pipeline on main fail?

  • Which tests are flaky in the api project?

  • What is the pass rate of our main pipeline this month?

  • When did we last deploy to production?

  • Rebuild the failed blocks of the last pipeline on main.

01

Red build on main

Priya Sharma, an engineer at Northwind, asked why main was failing. Memtro read the pipeline's jobs, found the failing job and gave the first failing command with its exit code.

02

Triage on a failed pipeline

When a pipeline on main finished with a failure, a job started for Tom Reilly at Acme Ltd. It read the failing job's commands and the project's flaky tests, and told him whether the failure was a known flaky test.

Teams

Where it fits

The teams that lean on Semaphore CI most, a question each of them asks, and what they connect beside it.

Better together

Works with

A record in Semaphore CI is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.

Also in Engineering and operations

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

Setup

How to connect

Connect withOrganization and API token
  1. 1

    In Semaphore open Account settings, then API Token, and copy your token. A service account's token, made by an organization admin, can have a narrower role.

  2. 2

    In Memtro open Connections → Semaphore CI and fill in Organization, the name in your Semaphore address, and the API token.

  3. 3

    An administrator grants the run, promotion and deployment target actions by name. Events are turned on from the connection's Events tab, and the address is then added in Semaphore's notification settings.

  4. 4

    Ask: why did the last pipeline on main fail?

Also works from

Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Semaphore CI tools are the same everywhere.

Set it up as an MCP serverClients and agents
FAQ

Questions

Can Memtro change anything in Semaphore CI?+

Only when you ask, and only what it has been granted: run a workflow on a branch, tag or pull request; rerun a workflow; stop a running workflow; stop a running pipeline; rebuild a pipeline's failed blocks; trigger a promotion (deploy) of a pipeline; run a task now; stop a running job; deactivate a deployment target; activate a deployment target. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.

Who can use a Semaphore CI connection?+

A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.

Does Memtro store my Semaphore CI data?+

Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.

How do I connect Semaphore CI?+

Organization and API token. In Semaphore open Account settings, then API Token, and copy your token. A service account's token, made by an organization admin, can have a narrower role.

Can Semaphore CI start a job?+

Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Semaphore CI, choosing the same kinds; the tab shows Semaphore CI's own steps. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.

Connect Semaphore CI in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Start for freePricing

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

Start for freeGetting started

7-day free trial · card on file, nothing charged until it ends · cancel any time