Launching today
Vida
Clone yourself. Let AI do the work before you ask
412 followers
Clone yourself. Let AI do the work before you ask
412 followers
Vida is an AI that learns how you work, remembers what matters, and becomes more like you over time. The more you use Vida, the more it understands your habits, your projects, and your way of getting things done. Eventually, it works like a second version of you—quietly handling repetitive work in the background before you even ask. Today, we’re launching our first 5 SOTA use cases: Reply Rescue · Prompt Rescue · Resume Rescue · Workspace Cleanup · Daily Wrap 95 more to conquer in public.
'Before you ask' is the bold part - proactive agents live or die on that judgment call. In my experience running agents for a business, the hard threshold isn't doing the work, it's knowing when acting early helps vs when it creates cleanup. How does Vida decide something is safe to do unprompted? Congrats on the launch.
Wegic
@david_marko Thanks so much—and I completely agree.
We actually think that’s the hardest problem in proactive AI.
Our principle is that proactivity should reduce cognitive load, not create more of it—and it should never interrupt your workflow just for the sake of being proactive.
So Vida starts with low-risk, high-confidence work—things like organizing information, preparing drafts, or surfacing context—while actions that could have meaningful consequences always require user confirmation.
Over time, as Vida learns your preferences and consistently earns your trust, it can become more proactive. We believe autonomy shouldn’t be assumed—it should be earned.
Handling memory in agents is the biggest friction point I've seen as a solo dev—it’s either too shallow or it consumes too many tokens. Curious if you're caching interaction styles locally to speed up the learning curve.
Wegic
@ayeshabuilds Great point—we’ve run into the same trade-off.
Yes, local-first memory is a core part of our approach. Vida keeps interaction history on your device whenever possible, which not only helps preserve privacy but also gives it richer long-term context without relying entirely on growing prompt windows.
We also open-sourced OpenChronicle, which explores this direction further. It lets you use local models to summarize memory, keep all your data on your own device, and pause or resume recording whenever you want.
We believe memory can be incredibly useful without becoming all-or-nothing surveillance.
GitHub: https://github.com/Einsia/OpenChronicle
how does Vida actually learn my habits day to day, does it just watch what I do across apps or do I have to feed it examples for it to get useful quickly?
Wegic
@sattapanbmta Great question!
Vida doesn’t require you to manually teach it with examples before it becomes useful.
Instead, it builds understanding from your work context—what you’re working on, your interaction history, and the tasks you ask it to help with. As you use Vida over time, it gradually learns your preferences and working style to provide better assistance.
Our goal is to make the learning process as natural as possible, without creating extra setup work for users.
the "Rescue" naming across the first three use cases is a really nice touch—feels like you mapped a real problem pattern instead of just slapping generic AI labels on them.
Wegic
@nurullahu6yq Thanks—that really means a lot 🙌
We’re intentionally trying to structure around real work patterns instead of feature names, so glad that came across.
More to come as we expand the 100 use cases 🚀
Congrats with a launch!
Do you use any type of am agentic browser automation tools?
I mean, can Vida operate user's browser on their behalf?
Wegic
@valzubkov Thanks for the great question ！
Browser automation is one of the key directions we’re actively building toward, but not fully available in Vida yet.
We’ve open-sourced BrowserBC, which learns reusable agent skills from human browser trajectories—essentially turning one recorded workflow into a generalized capability.
GitHub:
https://github.com/Einsia/Browser-BC
This is part of the foundation we’re building for bringing more real-world execution abilities into Vida over time 🚀
Wegic
@tehreem_fatima5 Thanks! That’s a tough one.
If we had to pick, it would probably be Reply Rescue. It captures what we think Vida should be—a system that understands enough context to take real work off your plate, instead of just generating text.
That said, Workspace Cleanup has also been a lot of fun because it’s such an everyday problem that almost everyone can relate to.
Hopefully we’ll have many more favorites as we work through the next 95 use cases! 🚀
The questions in this cases for me is always the same. How many tokens? How much control? Who is responsible for that?
With this being said, it seems an incredible app with huge potential.
Wegic
@bruno_perez_borrell Great questions—really appreciate you bringing them up.
On tokens, we’ve intentionally avoided tying core capability to usage limits or feature locks. Instead, our pricing is designed to stay simple and low-cost, while letting users choose what fits their own needs.
We’ve also open-sourced parts of our stack, including OpenChronicle and BrowserBC, if you’re interested in how we think about memory and agent skills in more depth:
https://github.com/Einsia/OpenChronicle
https://github.com/Einsia/Browser-BC
For users who want more control, you can even explore or self-host parts of the system locally.
We’re trying to balance flexibility, transparency, and control depending on how people want to use Vida.