Integrations
What AgentMingo connects to, and which way things flow
Each integration below says what AgentMingo reads, what it sends and what it needs. Anything not listed isn't connected.
Free during the open beta. Works with Claude Code today; Codex and more are next. On macOS or Linux.
Claude Code
- How
- Through Claude Code's own hooks and an MCP server, installed by the open-source reporter.
- Reads
- Each thread's state, repository and branch, a short title, token and tool counts, what a waiting prompt says, the paths of files it edits (on by default), what Claude writes when it reports a workflow step, and the files it attaches.
- Sends
- Short notes to the thread (the task's brief, review results, teammates' edits, main's changes, the next workflow step) and, if you turn answering on, your answers and replies.
- Needs
- macOS or Linux, Node.js 18 or newer, and the setup command. Works with Claude Code today; Codex and more are next.
GitHub
The AgentMingo GitHub App, on the repositories you choose
- Reads
- Pull requests, review comments from bots and from people who can write to the repository, check runs, pushes to main, and whether a pull request still merges.
- Writes
- A check run when a thread's workflow run finishes, an issue when you export a task, and a comment asking CodeRabbit for a new review when you press that button. Merging from AgentMingo uses your own GitHub account.
Jira
With Atlassian in one click, or an API token
- Reads
- Issues in the Jira projects you follow: title, description, acceptance criteria, type, priority, labels, parent and status, and the assignee (their email, when their Jira profile shares it, to match them to a member).
- Writes
- The issue's status when work moves here, off until an admin turns it on; a new issue when you export a task.
AI code reviewers and CI
On GitHub pull requests
- Reads
- Inline comments from CodeRabbit, Copilot code review, Greptile, Cursor Bugbot, Gemini Code Assist, Qodo and Sourcery in their own format, any other bot's as plain text, and check runs from any CI that reports them.
Notices
Chosen per person and per kind of notice
- Sends
- The bell, email, browser push, Slack, Discord, Google Chat and Microsoft Teams (through a Workflows webhook).
- Reads
- Nothing: nothing is run from chat.
Linear and GitHub Issues
Exports only
- Sends
- A task, exported as a new issue with a link back (Linear needs an API key and a team id).
- Reads
- Nothing.
Other Git hosts
- Reads
- Threads, tasks, teammates' files and your team's rules work with any Git host. Review results, merge conflicts and main changes need GitHub. A repository AgentMingo doesn't know from GitHub can be added from its folder with
repos add.
REST API
- How
- Organization API tokens, for projects, tasks, workflows, runs, findings and approvals.
Not here: a Slack app, Linear or GitHub Issues read into AgentMingo, Shortcut, and Git hosts other than GitHub for review results. Questions about a connection? Write to hello@agentmingo.com.
Questions
Is there a Slack app?
No app. AgentMingo posts notices to a Slack channel through an incoming webhook you add. It doesn't read Slack or run anything from it.
Is there an API?
Yes: a REST API with organization API tokens, for projects, tasks, workflows, runs, findings and approvals.
Where's the list of GitHub permissions?
On the Security page, with what each one is used for.
Connect your repositories, and your threads report.
Sign up, run one command on your computer, and keep working. Free during the open beta.