A brutalist task board for coding with AI. Notes live in your repo: copy the context with one key, or let an agent work the board over MCP and answer in each note. Standing rules, cross-project links and a map of your pages, APIs and tables. Free, open source.
Hi Product Hunt 👋
I built Bruto because working on a project with an AI meant explaining the same things again and again, in a chat that forgets. My tasks lived in one place, the context in another, and the AI's answers got lost in old conversations.
Bruto keeps a project's tasks as notes in a file inside the project itself (.bruto/workspace.json), so you and every AI you use work from the same source:
1. Write tasks on the board: what's wrong, which files, links, screenshots.
2. Copy exactly the context the AI needs with one key (Q, W or E): clean Markdown with short instructions for the model, and a preview of how many tokens it is.
3. If the AI can edit files (Claude Code, Codex, Cursor…), it answers inside the note and marks it for review. Bruto picks up the change live. If something is still wrong, write what and send it back with all its context.
A few things I cared about:
• Local only: no account, no server. Your notes never leave your folders, and it works offline.
• Safe with other tools: every save merges changes made elsewhere, note by note, and never overwrites a broken file.
• Standing rules: a note marked "Loop" ("run the tests before finishing") goes into every copy.
• It draws your project: pages with their components, API endpoints and database tables, with your notes on top.
It's free and open source (MIT). Opening your own folders needs Chrome, Edge, Brave or Opera on a computer, but you can look around the example project first, right in your browser: https://jimy-k4.github.io/bruto/...
I'd love to know how you keep track of tasks when you code with AI, and what would make Bruto fit your workflow.
One from building a board like this: keep a task's age when it changes hands. On mine a task passed to someone else keeps its clock, otherwise something bounced back and forth for a week always looks like it arrived today. A small "sent back 3 times" on the note would do a lot of it here, since the round trip with the AI is the loop that repeats.
We came to the same approach too. We create a markdown file for each task. At the start we write the status and state. The approach is simple and works fine. I ran through your code because I was curious how you do the sync. And I think I found a possible problem there. The sync itself works well and is written carefully, but there is this scenario. Say we have an unsaved change to a note's state locally. At that same moment the AI agent changes the state of the same note. Then the local copy wins and rewrites the file. And it all looks fine. But the problem is that the AI agent thinks everything went through and that it made the change. And the log will say so. No errors. But in fact it's not true. How do you feel about adding a short line at the top, like "state was changed back"?
About Bruto on Product Hunt
“A task board that lives in your repo, for you and your AI”
Bruto launched on Product Hunt on September 30th, 2026 and earned 74 upvotes and 8 comments, placing #15 on the daily leaderboard. A brutalist task board for coding with AI. Notes live in your repo: copy the context with one key, or let an agent work the board over MCP and answer in each note. Standing rules, cross-project links and a map of your pages, APIs and tables. Free, open source.
Bruto was featured in Task Management (84.3k followers), Developer Tools (520.4k followers), GitHub (41.4k followers) and Vibe coding (685 followers) on Product Hunt. Together, these topics include over 128.7k products, making this a competitive space to launch in.
Who hunted Bruto?
Bruto was hunted by jimy. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Bruto stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
jimy