Zenhub logo

Zenhub + Memtro

What is in the In Progress pipeline, and what is blocking it?

Zenhub connects Memtro to your agile boards on GitHub. It reads workspaces and their repositories, pipelines, the issues in a workspace or a pipeline, searchable by words, labels or assignee, and one issue with its body, pipeline, priority, estimate, sprints, labels, issue type, parent and sub-issues. It reads blocking dependencies and issue types too. When asked, and once an administrator has granted the action by name, it can create or edit issues, close or reopen them, move them between pipelines, set estimates, add them to sprints, change types, nest them and add or remove dependencies. Assignees are not returned.

In Memtro

What you can do with Zenhub in Memtro

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

What it does

  1. 01Lists workspaces, a workspace's repositories, and its pipelines in board order
  2. 02Lists issues and pull requests in a workspace, and open issues in one pipeline matched by words in the title, labels or assignees' GitHub handles
  3. 03Reads one issue with its body, state, estimate, sprints, labels, issue type, parent, pipeline, priority and sub-issues
  4. 04Lists blocking dependencies in a workspace and the issue types a repository can take
  5. 05When asked and granted, creates an issue or sub-issue, which on GitHub notifies the repository's watchers, edits its title, body or dates, and closes or reopens issues
  6. 06When asked and granted, moves an issue to another pipeline, which everyone on the board sees, sets an estimate, adds issues to sprints, changes issue types, nests issues under a parent, and adds or removes a blocking dependency

Acts when asked

When you ask it to

These tools change something in Zenhub. 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. 01Create an issue or a sub-issue in a repository (a GitHub issue notifies the repository's watchers)
  2. 02Edit an issue's title, body, or start and end dates
  3. 03Close issues
  4. 04Reopen closed issues into a pipeline
  5. 05Move an issue to another pipeline
  6. 06Set an issue's estimate
  7. 07Add issues to sprints
  8. 08Change or remove the issue type of issues
  9. 09Make issues sub-issues of a parent
  10. 10Mark one issue as blocking another
  11. 11Remove a blocking dependency
In practice

Ask it like you would a colleague

Once Zenhub 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.

Zenhub logoZenhub + Memtro
  • What is in the In Progress pipeline?

  • Which issues are blocking the release epic?

  • What is the estimate on the login redesign issue?

  • Which issue types can the web repository use?

  • Move issue 482 to Review and set its estimate to 3

01

Stand-up in one question

Sarah Chen, engineering manager at Acme Ltd, asked what was in progress and what was blocked. Memtro listed the open issues in the In Progress pipeline and the blocking dependencies between them.

02

Updating the board

Tom Reilly, developer at BigCo, asked Memtro to move issue 482 to Review and set its estimate to three points. Memtro moved it in Zenhub, where everyone on the board saw it move, and set the estimate.

Teams

Where it fits

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

Better together

Works with

A record in Zenhub 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 withPersonal API Key and optional default workspace
  1. 1

    In Zenhub, open Dashboard → API → Personal API Keys at app.zenhub.com. The key acts as you, so Memtro sees the workspaces and issues you can see.

  2. 2

    Create a new key named Memtro and copy it now: Zenhub shows it once.

  3. 3

    In Memtro, open Connections → Zenhub and paste it into Personal API Key. Add Default workspace id from the end of your board's URL if most questions are about one board.

  4. 4

    Ask your first question: what is in the In Progress pipeline?

Also works from

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

FAQ

Questions

Can Memtro change anything in Zenhub?+

Only when you ask, and only what it has been granted: create an issue or a sub-issue in a repository (a GitHub issue notifies the repository's watchers); edit an issue's title, body, or start and end dates; close issues; reopen closed issues into a pipeline; move an issue to another pipeline; set an issue's estimate; add issues to sprints; change or remove the issue type of issues; make issues sub-issues of a parent; mark one issue as blocking another; remove a blocking dependency. 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 Zenhub 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 Zenhub 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 Zenhub?+

Personal API Key and optional default workspace. In Zenhub, open Dashboard → API → Personal API Keys at app.zenhub.com. The key acts as you, so Memtro sees the workspaces and issues you can see.

Connect Zenhub in a few minutes

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

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.

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