Failed deploy
Tom Reilly, platform engineer at BigCo, asked why the last deploy_api run failed. Memtro read the execution, named the failed stage and its error, and said who had triggered the run.
Why did the last deploy_api run in Harness fail?
Harness connects Memtro to your CI/CD. It reads organizations, projects and pipelines with their last run, and executions by status with stage counts, failures and durations. For one run it reads each stage's status and the error, and it lists pending approvals, services and environments. When asked and granted, it can run a pipeline, retry a failed run from given stages, abort a run or mark it failed, approve or reject an approval step, and tag or annotate a run. A CD pipeline deploys when it runs, and an abort does not undo what has already deployed.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Harness tool, reads what it needs, and answers with the source cited.
These tools change something in Harness. 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 Harness 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 the last deploy_api run in the payments project fail?
Which pipeline runs are waiting on approval?
Which runs failed this week in the checkout project?
Which environments does the payments project deploy to?
Retry yesterday's failed deploy_api run from the deploy stage.
Tom Reilly, platform engineer at BigCo, asked why the last deploy_api run failed. Memtro read the execution, named the failed stage and its error, and said who had triggered the run.
Sarah Chen, engineering manager at Northwind, asked Memtro to approve the waiting approval step on the release pipeline. As granted, Memtro approved it as the key's user with her comment, and the gated deployment went ahead.
The teams that lean on Harness most, a question each of them asks, and what they connect beside it.
A record in Harness 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 Harness, open My Profile, My API Keys, add an API key and a token with an expiry, and copy it. A service account token limited to viewing and executing chosen pipelines is safer.
In Memtro, open Connections → Harness and paste the API key token and your Account ID, from any Harness URL.
An administrator grants the actions by name, such as running pipelines, to the teams that may use them. Set the Host only for a vanity or self-managed Harness.
Ask why the last deploy_api run in payments failed.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Harness tools are the same everywhere.
Only when you ask, and only what it has been granted: run a pipeline (a CD pipeline deploys); retry a failed pipeline run from given stages; abort a running pipeline execution; mark a pipeline execution as failed; approve or reject a Harness approval step; add tags to a completed pipeline execution; set the notes on a pipeline execution. 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.
API key token and account ID. In Harness, open My Profile, My API Keys, add an API key and a token with an expiry, and copy it. A service account token limited to viewing and executing chosen pipelines is safer.
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