Bracket
Your business, remembered. Automatically.
107 followers
Your business, remembered. Automatically.
107 followers
Bracket connects to the tools your business already runs on — Gmail, Slack, Figma and GitHub — and turns conversations, updates and meeting notes into a living business memory. It automatically tracks requirements, decisions, scope, deliverables, deadlines and changes, then uses that context to answer questions and generate relevant replies. Instead of constantly updating another tool, Bracket keeps itself updated.
This is the 2nd launch from Bracket. View more
Bracket
Launched this week
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.
Free Options
Launch Team / Built With
TinyFishSearch, fetch and browse for AI agents. Claim 30% bonus!
Promoted
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
@saksham_shukla28 congrats on the launch!
@dmtsepelev Thanks Dmitrii! 🙌 Would love for you to actually give Bracket a spin too. It’s completely free right now, and feedback from a fellow builder like you would genuinely mean a lot. Especially the things you think we should improve 😄
@saksham_shukla28 Does the change detection work across Gmail, Slack, Figma, and GitHub ?
@dipanshu_kushwaha5 Yes, that's exactly the idea! Bracket connects with Gmail, Slack, Figma, and GitHub, and keeps track of relevant changes across conversations and project activity, whether it's a new requirement, a scope change, a decision, or an updated deadline.
Instead of manually checking four different tools to figure out what changed, you can see that context together in Bracket.
Would love for you to try it with a real project, Dipanshu. It's free right now, and I'd genuinely appreciate your feedback on how well it works for your workflow! 🙌
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 @Bracket today 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.
Be brutally specific. We’re listening.
@product
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.
Great question, @karimbenkeroum. Bracket doesn’t silently overwrite one piece of context with another. When information conflicts, it keeps the source and timeline behind both, so you can see what changed and where it came from. If recency alone can’t resolve it, we’d rather surface the conflict than confidently remember the wrong thing.
Would actually love for you to try Bracket with a real project once. It’s free right now, and given the exact problem you pointed out, I’d genuinely be curious to see where it works or breaks for you. Would love your feedback.
+1 to this. Conflicting context is exactly the kind of thing that gets interesting once Bracket is connected to a real project😅
@karimbenkeroum , would genuinely love for you to throw a real project at it and tell us where our assumptions break.
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?
@galdayan Great question. We don’t want “most recent” to automatically mean “correct.”
In a case like that, Bracket keeps the source and timeline of both pieces of context. If Slack says the scope changed but Figma still reflects the older version, it can identify that inconsistency rather than silently replacing one with the other.
Where the intent is clear, Bracket can understand what changed and preserve the history. Where it’s genuinely ambiguous, we’d rather surface the conflict for someone to resolve than confidently make the wrong assumption.
This is actually one of the areas we’re actively refining, so I’d love for you to throw a real-world case like this at Bracket and see where it breaks 😄