Bracket turns the conversations already happening across your business into a living, continuously updated memory. Connect Gmail, Slack, Figma and GitHub, or add meeting notes and transcripts. Bracket automatically captures requirements, decisions, scope, deliverables, deadlines and changes as they happen. Then ask Bracket about anything that happened or generate replies using the full context. No more manually keeping another tool up to date.
We’re back — but Bracket is almost a completely different product this time.
When I first built Bracket, the idea was simple: explain your project once, and Bracket would turn that context into a structured workspace.
Then I realized something slightly annoying 😅
The moment you finish organizing your work, it starts becoming outdated.
A decision happens in Slack. A requirement changes over email. Someone leaves important feedback in Figma. Engineering ships something on GitHub. And half the context from a meeting never makes it anywhere.
So Tanay and I rebuilt Bracket around one question: What if your workspace could remember all of this for you?
Today, Bracket connects to Gmail, Slack, Figma and GitHub, and can also understand meeting notes and transcripts.
As work happens, Bracket keeps track of what actually matters — requirements, decisions, scope, deliverables, deadlines and changes.
And because it remembers that context, you can ask Bracket things like:
“Why did the launch date change?”
…and get an answer with the original source.
It can even use that same memory to help you write replies without making you explain the entire situation again.
There’s still a lot we want to improve. That’s actually why we’re here.
Try Bracket with something real and tell us where it breaks, what feels unnecessary, or what you wish it remembered. We’ll be hanging around here all day and would genuinely love to talk.
curious how it resolves conflicts, not just captures info. say a decision gets made in a Slack thread but the Figma doc still shows the old version, or two people say different things about scope in different channels. does Bracket flag that as a contradiction for someone to resolve, or just go with whichever is most recent?
Capturing decisions and scope changes straight from Slack and Gmail is where most teams quietly lose context, so building a memory layer around that is smart. Curious how you handle conflicting information when two threads say different things about the same deliverable.
A small launch-day update 👀
Bracket somehow made it to #8 today, which we genuinely weren’t expecting, especially because this launch accidentally went live while Tanay and I were both out of town 😅
But here’s something I’m curious about:
If you saw @Brackettoday but didn’t try it, what stopped you?
Was it unclear what Bracket does? Too much setup? Not relevant to your workflow? Something else?
Bracket is free to try right now, and I’d genuinely rather hear what’s stopping people than collect more upvotes.
Bracket launched on Product Hunt on October 1st, 2026 and earned 113 upvotes and 13 comments, placing #9 on the daily leaderboard. Bracket turns the conversations already happening across your business into a living, continuously updated memory. Connect Gmail, Slack, Figma and GitHub, or add meeting notes and transcripts. Bracket automatically captures requirements, decisions, scope, deliverables, deadlines and changes as they happen. Then ask Bracket about anything that happened or generate replies using the full context. No more manually keeping another tool up to date.
Bracket was featured in Productivity (663.1k followers), SaaS (44.8k followers) and Artificial Intelligence (481.1k followers) on Product Hunt. Together, these topics include over 356.7k products, making this a competitive space to launch in.
Who hunted Bracket?
Bracket was hunted by Saksham Shukla. 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 Bracket stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Saksham Shukla
Hey Product Hunt 👋
We’re back — but Bracket is almost a completely different product this time.
When I first built Bracket, the idea was simple: explain your project once, and Bracket would turn that context into a structured workspace.
Then I realized something slightly annoying 😅
The moment you finish organizing your work, it starts becoming outdated.
A decision happens in Slack.
A requirement changes over email.
Someone leaves important feedback in Figma.
Engineering ships something on GitHub.
And half the context from a meeting never makes it anywhere.
So Tanay and I rebuilt Bracket around one question:
What if your workspace could remember all of this for you?
Today, Bracket connects to Gmail, Slack, Figma and GitHub, and can also understand meeting notes and transcripts.
As work happens, Bracket keeps track of what actually matters — requirements, decisions, scope, deliverables, deadlines and changes.
And because it remembers that context, you can ask Bracket things like:
“Why did the launch date change?”
…and get an answer with the original source.
It can even use that same memory to help you write replies without making you explain the entire situation again.
There’s still a lot we want to improve. That’s actually why we’re here.
Try Bracket with something real and tell us where it breaks, what feels unnecessary, or what you wish it remembered. We’ll be hanging around here all day and would genuinely love to talk.
Thanks for giving Bracket another look ❤️
— Saksham & Tanay