A failed nightly build
Maya Okafor, mobile lead at Northwind, asked why the nightly iOS build had failed. Memtro read the build and gave its workflow, branch, commit, abort reason and how long it ran before stopping.
Why did last night's iOS build fail, and how many credits did it use?
Bitrise shows you your mobile projects and their repositories, then builds with status, branch, commit, workflow, duration and credits used. Memtro also reads pipelines, the workflows a project has run, build artifacts, pull-request builds waiting for approval, and quarantined tests. When asked and granted, it can start a build or pipeline, rebuild or abort one, and approve or reject a waiting pull-request build. It can also quarantine a flaky test or release one from quarantine. Build logs, secrets and signing files are never read, so Memtro reports an abort reason but not the log behind it.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Bitrise tool, reads what it needs, and answers with the source cited.
These tools change something in Bitrise. 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.
Once Bitrise 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.
Why did last night's iOS build fail?
How many credits did the release workflow use this week?
Which pull-request builds are waiting for approval?
Which tests are in quarantine on the Android app?
Rebuild the last failed build on the main branch.
Maya Okafor, mobile lead at Northwind, asked why the nightly iOS build had failed. Memtro read the build and gave its workflow, branch, commit, abort reason and how long it ran before stopping.
Dan Fletcher, Android engineer at Acme Ltd, asked Memtro to quarantine a login test that kept failing at random. With the action granted, Memtro quarantined it on the project, so its failures stopped failing builds for the whole team.
The teams that lean on Bitrise most, a question each of them asks, and what they connect beside it.
A record in Bitrise 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.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Bitrise, open Account settings → Security → Personal access tokens → Create token. A Workspace API token with only the role Memtro needs suits a team better.
Open Connections → Bitrise in Memtro and paste the Access token.
An administrator grants actions such as start a build or approve a pull-request build by name to the teams that may use them.
Ask why last night's iOS build failed.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Bitrise tools are the same everywhere.
Only when you ask, and only what it has been granted: start a build or pipeline on a branch, tag, commit, workflow or pipeline (spends credits); abort a running build; rebuild a finished build (spends credits); abort a running pipeline; rebuild a pipeline, whole or from its failed workflows (spends credits); approve or reject a pull-request build waiting for approval; quarantine a flaky test; release a test from quarantine. 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.
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.
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.
Access token. In Bitrise, open Account settings → Security → Personal access tokens → Create token. A Workspace API token with only the role Memtro needs suits a team better.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time