Caret gets to know you and autocompletes you across every app on your Mac. It learns your work, your friends, your style and suggests completions that actually sound like you. Just press Tab.
We kept noticing the same frustration on our team. Typing in Slack, filling out a Jira ticket, writing a commit message, replying to an email. Our brains already knew the rest of the sentence. Our fingers just hadn't caught up yet. Autocomplete exists in code editors. Everywhere else on your Mac? Nothing. So we built Caret.
What it does: Caret sits invisibly in the background and finishes your thoughts, anywhere you type on your Mac. Press Tab and it completes your sentence. One keystroke. No copy-pasting into ChatGPT, no switching windows, no waiting for a chatbot to load.
How it works:
You grant one accessibility permission and Caret reads the context of whatever you're working on: the app, the text field, what's on screen
No screen recording, no screenshots. It reads text, not pixels.
No integrations, no plugins, no per-app setup. It just works everywhere.
What makes it different: Behind the scenes, Caret turns your sessions into chains of thought, building a second brain that learns how you write, what you're working on, and what you're likely to say next. Those memories are stored locally on your Mac. The longer you use it, the sharper it gets. It stops feeling like autocomplete and starts feeling like an extension of your own thinking.
We're a tiny team and this is a v1. We love feedback and ship fast. Thanks so much for checking us out! 🙏🏼
@dschwartz18 the 'tab to complete' interaction is exactly what’s been missing. i’m so used to it in vscode that i find myself hitting tab in slack and being disappointed when nothing happens lol. definitely giving caret a spin today.
How do you envision Caret balancing speed and personalization as it learns—do you see it leaning more toward instant utility (fast completions anyone could use) or toward deeply individualized suggestions that reflect each person’s writing style?
@odeth_negapatan1 Great question! We lean heavily toward personalization. The core bet is: the better Caret knows you, the higher the chance it predicts exactly what you would have written - not just something generic and plausible.
A suggestion that's perfectly tailored to your style and context is worth a tiny bit of latency. A fast suggestion you don't actually want is just noise.
That said, we're very aware that speed is table stakes for autocomplete - if it doesn't feel instant, people stop using it. So we're working hard to make sure personalization doesn't come at a meaningful cost to responsiveness. The goal is for it to feel both fast and like it knows you.
@rooly_ I actually configured it as ⌘V 🤘 (you can do it in Caret's settings)
Report
This is such a real pain point -- the context-switching tax is invisible until you actually measure how much time you lose to it. How does Caret handle sensitive fields like passwords or internal finance docs? Curious how you think about the trust layer when it's reading across every app. Also does the 'second brain' piece work across machines or is it purely local?
@andrasczeizel Hey Andras! Thanks for the comment and believing in us! In general about privacy - the information is local (sharing feedback is optional) and sent to LLM providers (who commit to not train on the data). We are thinking about features to blacklist or pause Caret. Would love to hear your thoughts! The second brain is local, your memory and connections become more elaborate as you keep using Caret on you desktop. We see it continuing to more sensors and devices to truly become a second brain.
@dschwartz18 That makes sense on the privacy side, local storage + optional sharing is a solid default. And the multi-device vision is exciting, rooting for you to get there. Good luck with the launch! :))
@andrasczeizel Thanks and looking forward to hearing your feedback 😁
Report
every editor plugin promises AI anywhere you type. the value gap is always timing - knowing when to suggest vs when to stay quiet. availability is the easy part.
Editor plugins only see what's in the editor - Caret sits at the OS level, so it sees everything you've been working on across apps.
That's what makes timing solvable at all. If you know enough about what the user is doing, you can make a much better call on when to suggest vs. stay quiet.
Report
That's a genuine differentiator. Most of my writing context lives across 3-4 apps - the reference doc, the brief, the Slack thread. Editor plugins never see any of that. OS-level access is the only way to bridge it.
Replies
Caret
Hey everyone! Dan here, cofounder of Caret 👋🏼
We kept noticing the same frustration on our team. Typing in Slack, filling out a Jira ticket, writing a commit message, replying to an email. Our brains already knew the rest of the sentence. Our fingers just hadn't caught up yet.
Autocomplete exists in code editors. Everywhere else on your Mac? Nothing. So we built Caret.
What it does: Caret sits invisibly in the background and finishes your thoughts, anywhere you type on your Mac. Press Tab and it completes your sentence. One keystroke. No copy-pasting into ChatGPT, no switching windows, no waiting for a chatbot to load.
How it works:
You grant one accessibility permission and Caret reads the context of whatever you're working on: the app, the text field, what's on screen
No screen recording, no screenshots. It reads text, not pixels.
No integrations, no plugins, no per-app setup. It just works everywhere.
What makes it different: Behind the scenes, Caret turns your sessions into chains of thought, building a second brain that learns how you write, what you're working on, and what you're likely to say next. Those memories are stored locally on your Mac. The longer you use it, the sharper it gets. It stops feeling like autocomplete and starts feeling like an extension of your own thinking.
We're a tiny team and this is a v1. We love feedback and ship fast. Thanks so much for checking us out! 🙏🏼
trycaret.com
@dschwartz18 the 'tab to complete' interaction is exactly what’s been missing. i’m so used to it in vscode that i find myself hitting tab in slack and being disappointed when nothing happens lol. definitely giving caret a spin today.
Raycast
Caret
@chrismessina I love you and Raycast! 🥇
Caret
@chrismessina
Lancepilot
Caret
@odeth_negapatan1 Great question! We lean heavily toward personalization. The core bet is: the better Caret knows you, the higher the chance it predicts exactly what you would have written - not just something generic and plausible.
A suggestion that's perfectly tailored to your style and context is worth a tiny bit of latency. A fast suggestion you don't actually want is just noise.
That said, we're very aware that speed is table stakes for autocomplete - if it doesn't feel instant, people stop using it. So we're working hard to make sure personalization doesn't come at a meaningful cost to responsiveness. The goal is for it to feel both fast and like it knows you.
Caret
@odeth_negapatan1 Speed and personalization Odeth just described our day to day @Caret better than us
Caret is my new ⌘V
Caret
@rooly_ exactly! It's a whole new world!
looking forward to getting more of your feedback ✌🏼
Caret
@rooly_ I actually configured it as ⌘V 🤘 (you can do it in Caret's settings)
This is such a real pain point -- the context-switching tax is invisible until you actually measure how much time you lose to it. How does Caret handle sensitive fields like passwords or internal finance docs? Curious how you think about the trust layer when it's reading across every app. Also does the 'second brain' piece work across machines or is it purely local?
Congrats on the launch, rooting for you 🙌
Caret
@andrasczeizel Hey Andras! Thanks for the comment and believing in us!
In general about privacy - the information is local (sharing feedback is optional) and sent to LLM providers (who commit to not train on the data). We are thinking about features to blacklist or pause Caret. Would love to hear your thoughts!
The second brain is local, your memory and connections become more elaborate as you keep using Caret on you desktop. We see it continuing to more sensors and devices to truly become a second brain.
Caret
@andrasczeizel @dschwartz18
Also check out the memory tab on the toolbar app! it became my personal crm at this point 😙
@dschwartz18 @ron_adin1 Haha okay that actually sold me, checking it out now :D
Caret
@dschwartz18 @andrasczeizel YESSSS
@dschwartz18 That makes sense on the privacy side, local storage + optional sharing is a solid default. And the multi-device vision is exciting, rooting for you to get there. Good luck with the launch! :))
Caret
@andrasczeizel Thanks and looking forward to hearing your feedback 😁
every editor plugin promises AI anywhere you type. the value gap is always timing - knowing when to suggest vs when to stay quiet. availability is the easy part.
Caret
@mykola_kondratiuk The difference with Caret is context.
Editor plugins only see what's in the editor - Caret sits at the OS level, so it sees everything you've been working on across apps.
That's what makes timing solvable at all. If you know enough about what the user is doing, you can make a much better call on when to suggest vs. stay quiet.
That's a genuine differentiator. Most of my writing context lives across 3-4 apps - the reference doc, the brief, the Slack thread. Editor plugins never see any of that. OS-level access is the only way to bridge it.
Caret
@mykola_kondratiuk Exactly 🤘 Waiting to hear your feedback on the product!
Caret
@mykola_kondratiuk Thanks for the support!
Wion - Audio Dating
Excited
Caret
@tanjum super 😻
Wion - Audio Dating
@ron_adin1 Appreciate team
Nori
Been using it for a while and it’s like it’s reading my mind
Caret
@matiszz love to hear it! That’s the goal.
As we progress and add more you’ll feel that more and more with no configurations
Caret
@matiszz Tab for mind reading! 📖
@dschwartz18 Congratulations. And happy product launch.
Caret
@dschwartz18 @huisong_li thanks for the love!
Caret
@huisong_li @ron_adin1 much appreciated
Earth.fm
Big fan of small teams shipping fast—keep it up!
Caret
@1mirul It's the best way!
let us know if you try it out and how we can make it any better
Caret
@1mirul small team hitting a lot of tabs 🥹