minddy keeps issues, plans, agent runs and pull requests together. Its public core is open source and self-hostable.

Free for 2 projects. No credit card.

MIN-42

The Stripe webhook returns a 500

  1. The agent writes the plan

    • Reproduce the 500 in a test
    • Check the signature before parsing
    • Handle Stripe's retry
  2. It runs, in its own machine

    fix/stripe-webhook-5004 files changed, checks green
  3. The pull request lands on the issue

    #128+82 −14
  4. You review, then you merge

    ApproveRequest changes

Use the managed service today. The same public core can run on infrastructure you control.

Minddy Cloud

Open a workspace in your browser. Minddy handles the service behind it.

  • Minddy manages the infrastructure, backups, and updates.
  • Invite your team and start without a deployment.
  • Start free and upgrade when your workspace grows.

Self-host the public core

Install minddy on infrastructure you manage. The application core is the same one used by Minddy Cloud.

  • Choose where minddy runs.
  • Manage access, updates, and backups yourself.
  • Use the documented installation and operations path.
Read the self-hosting guide

Inspect minddy's tracker, run it yourself, and see how releases and security work.

minddy is released under the GNU AGPL v3.0 only.

  • Inspect it

    The application code, release process, and security model are out in the open.

  • Run it yourself

    Follow the documented path from a fresh host to a working tracker.

  • Help improve it

    Report an issue, join the discussion, or send a pull request.

Projects, issues, objectives and cycles stay visible without a setup project of their own.

A minddy project board: issues grouped by status, with priorities, assignees and an agent badge.
Your board: every issue, grouped by status.
  • Issues and views

    Columns by status, saved views, bulk actions.

  • All your projects at once

    One board for all your projects, with cross-project views.

  • Inbox

    What's assigned to you, mentions, and the agent waiting on your answer.

  • Objectives

    A group of issues sharing one goal, with its progress.

  • Cycles

    Your fortnight, across every project. minddy can fill it for you.

  • Triage

    Issues your agents create wait for your approval.

The built-in MCP server gives coding agents the issue context and tools they need to report back.

  • Read an issue with its full context.
  • Write its plan onto the issue, then tick it off.
  • Change status, priority, assignee, objective.
  • Create issues and objectives, and link them together.
  • Report back in a comment.
  • Read and write the project's wiki pages.
  • Review the pull request opened on the issue.
  • And the notebook, your cycle, your user feedback too.

Works with

  • Claude Code
  • Claude Desktop
  • Codex
  • Cursor
  • Gemini CLI
  • VS Code
  • Windsurf

The MCP server and Numo agent are included in every plan, including Free. With your own API key, its runs are uncapped and billed by your provider.

One issue carries it all: the plan, the agent, the branch, the pull request.

The new issue dialog, with a title, a short description and three properties set.

You describe

A title, two sentences, a priority. The agent doesn't need more.

An agent run in progress, showing its tool calls and the issue it is working on.

The Numo agent runs

It explores the repo, writes its plan, then codes and runs your checks in an isolated machine.

The pull requests page, with the agent's changes shown file by file.

You review

The pull request attaches to the issue: diff, comments, merge. Without leaving minddy.

The Numo panel open over a board, showing the issues it found and the ones it changed.

The built-in assistant: it opens over the screen you're on, and it has already read the board.

  • It looks, then it answers

    “Where are we on payments?” It goes through issues, comments and diffs before answering.

  • It acts on the tracker

    Create an issue, change ten statuses, save a view: in one sentence.

  • It knows where you are

    The screen in front of you is its context. Nothing to paste back in.

For example

  • What's waiting in triage?
  • Assign me the urgent issues
  • Create a view of urgent bugs
  • Help me create an issue

Use the keyboard, dictate a change, or keep a task in the notebook until it is ready.

The command palette open on a search returning issues and actions.

⌘K palette

Search, create, change a status or an assignee, without leaving the keyboard.

You speak. minddy fills the title, description and issue fields.

What you say

Dictate an issue

Five seconds is enough. No account, no recording kept.

No mic? Play a sentence

What minddy makes of it

Your issue shows up here, filled in.

Priority
Due date
Assignee
Categories
  • Dictate a whole issue

    One sentence, and the form comes back filled.

  • Fix it out loud

    “Move it to in progress, and add that the webhook returns a 500.”

  • And everywhere else

    Comments, pull requests, instructions to Numo: the same mic button.

The notes file you kept open in your editor, except your agents can read this one.

  • Free text, checkboxes, a task you dictate.
  • A line, a section or the whole notebook copies out as a prompt.
  • Or goes straight to Numo, without going through an issue.
  • A note that outgrows the notebook becomes an issue.
  • Your agents read it, add to it and tick it off over MCP.
The notes window, with sections of finished and pending tasks.

Specs, notes, write-ups: what explains the tickets lives next to them, not in another tool.

A project wiki page, with the page tree on the left and its content on the right.
A project's pages, with their subpages.
  • Pages, and subpages

    A block editor: headings, lists, checkboxes, code, images, files.

  • Wired to your tickets

    A mention opens the ticket, objective or page it names.

  • Your agents write in them

    They read, search, draft and comment on pages over MCP.

  • Published, exported, recoverable

    A read-only link, a Markdown or PDF export, thirty days of history.

Feedback arrives, groups itself and sorts by votes. Without ever entering your tracker.

A public feedback board sorted by votes, with status badges and categories.
Public side: they suggest, they vote.
A user request seen from the team side, with its votes and the promote action.
Team side: the same request, and what you do with it.
  1. They post

    An email, a six-digit code, and the feedback goes off for review.

  2. Numo screens it

    It turns away spam, files it under your categories, merges duplicates.

  3. You decide

    You answer publicly, or promote the request to an issue.

  4. The status follows

    The issue moves, the public board moves with it.

Bring existing work in, share progress out, and connect your own tools through the API.

  • Shared views

    Any view can be shared as a read-only link.

  • CSV import

    The Linear export, the Jira export, or any CSV.

  • Public API

    Your own tools post issues and feedback into minddy.

These monthly plans pay for the Minddy-managed Cloud service. They do not change the public self-hosted core.

Free

Track your work, with up to three guests.

0forever

 

  • Base AI usage
  • 2 projects
  • 300 issues per project
  • 3 guests per project
  • Models up to 1×
  • Numo agent
  • Bring Your Own Key
Start for free
Recommended

Go

Unlimited workspaces, with more AI usage.

8/ month

 

  • 10× more usage than Free
  • Unlimited projects
  • Unlimited issues
  • Unlimited guests
  • Models up to 15×
  • Numo agent
  • Bring Your Own Key
Start for free

Pro

More AI usage and storage for larger workloads.

20/ month

 

  • 30× more usage than Free
  • Unlimited projects
  • Unlimited issues
  • Unlimited guests
  • Models up to 40×
  • Numo agent
  • Bring Your Own Key
Start for free

Payments through Stripe. Switch or cancel at any time.

Self-hosted minddy is the same public core. See how to self-host minddy.

Any agent that speaks MCP. Claude Code, Codex, Cursor, Gemini CLI, VS Code, Windsurf: the install is ready to paste, and authorization happens over OAuth.

The code agent then runs on your key (Anthropic, OpenAI, Google, OpenRouter or any compatible endpoint): its runs are uncapped and your provider bills them. The subscription pays for minddy, not for your tokens.

Every plan includes a monthly AI usage budget, reset each month. You can see what has been spent at any time.

It is never sold or used for advertising. One email to hello@minddy.app is enough to get a copy or have your account deleted.

Yes, on every plan: two guests per project on the free one, five on Go, as many as you want on Pro. You invite them by email.

You drop the CSV export into the project settings. Titles, descriptions, statuses, priorities, categories and sub-issues all come across.

Create your first project, add an issue, and connect your coding agent.