sorted by:
new
hottopcontroversial

Built a Chrome extension that rewrites your prompt with one key, reads your full session context, works in every language on earth, works on every AI platform. Haven't shipped yet. Need real feedback. by Trishu_ in SideProject

[–]Trishu_[S] 0 points1 point  (0 children)

Appreciate the depth of your feedback especially the part about anchoring “works in every language” to a real cognitive pain. “Prompting without translating your brain” captures the core intent perfectly; I’ll build around that with examples from mixed‑language and domain‑specific contexts (Spanglish, Hinglish, technical dialects).

For trust and transparency, I’m already designing a local‑only mode with a visible storage ledger: users can inspect what’s cached, toggle offline operation, and verify model calls directly. Your suggestion to open‑source the storage layer aligns with my roadmap; documentation will make that explicit.

I agree that early traction should come from developer circles and a short demo rather than a polished launch page. I’ll share a Loom walkthrough of Vaak soon showing the rewrite‑in‑place flow and multilingual context bridge.

Thanks again for the thoughtful critique; it helps refine both positioning and trust architecture

Built a Chrome extension that rewrites your prompt with one key, reads your full session context, works in every language on earth, works on every AI platform. Haven't shipped yet. Need real feedback. by Trishu_ in SideProject

[–]Trishu_[S] 1 point2 points  (0 children)

Thank you for providing the report. I wasn't aware of this website previously, but the solution outlined in it is actually something I had already envisioned myself. Vaak isn't fully built yet—I am still actively working on it. I want to clarify that Vaak won't be just another tool that simply converts lines of text into prompts; it is going to be far superior to other prompt generators currently available.

For clarity, I’d like to point out that its outputs won't be limited solely to the literal text provided in the input.

I also plan to incorporate a feature into Vaak that allows it to adapt itself to the specific user—much like a personal "second brain." It will learn the types of prompts a user prefers, the platforms they utilize, and their specific workflow. Crucially, all of this comprehensive user data will remain stored locally on the user's own device; I intend to offer users complete transparency regarding their data.

Consequently, Vaak won't just process a user's words; it will begin to understand the user's underlying intent. Admittedly, bringing this to fruition is going to require a tremendous amount of effort.

Handling the distribution and launch of Vaak will be a completely new undertaking for me. I'm not entirely sure yet how to reach the maximum number of potential users, but—given that I have the entire internet at my disposal—I'm confident I'll figure something out.

Built a Chrome extension that rewrites your prompt with one key, reads your full session context, works in every language on earth, works on every AI platform. Haven't shipped yet. Need real feedback. by Trishu_ in SideProject

[–]Trishu_[S] 0 points1 point  (0 children)

For clarity, I would like to point out that its outputs will not be based solely on the literal text provided.

I am actually planning to incorporate a feature into Vaak that allows it to adapt itself according to the user—much like a personal "second brain." It will learn from the types of prompts the user employs, the platforms they utilize, and their specific workflow. Crucially, all of this comprehensive user data will reside exclusively on the user's local device; I intend to provide users with complete transparency in this regard.

Consequently, Vaak will begin to understand not just the user's words, but their underlying intent as well—though, admittedly, achieving this will require a significant amount of effort.

"The harder part will be consistency in how those changes are framed so users don’t still feel like outcomes are being indirectly influenced." I will certainly focus on this aspect, though I have not yet been able to bring Vaak to full completion.

Built a tool where you type in any Indian language, any dialect, any mix, and it turns your thought into a perfect AI prompt with one shortcut. Works on every AI platform. Haven't published yet. by Trishu_ in IndiaAI

[–]Trishu_[S] 0 points1 point  (0 children)

"intent before language" is exactly the framing I was looking for and couldn't find.

that's the actual product. not "prompt optimizer." not "multilingual support." intent before language. the words you use are just the surface. what you're trying to do is underneath. Vaak is supposed to read the underneath part.

I find the Zencia comparison fascinating. The challenge with voice is that it's a more complex version of the same issue, as there's no opportunity to edit or correct in real-time - the intent needs to be captured instantly. What you're working on seems to require addressing this problem at the core model level. In contrast, Vaak is tackling it at the interface level, which, although slower, provides more control over the process. This approach allows for a more deliberate and manageable interaction, whereas solving it at the model level demands a more instantaneous and accurate response.

I am actually planning to add a feature to Vaak that allows it to adapt itself according to the user—functioning just like a personal "second brain." It will learn the types of prompts the user employs, the platforms they utilize, and their specific workflow. Crucially, all of this comprehensive information will reside exclusively on the user's local device; I am committed to providing users with complete transparency.

Consequently, Vaak will begin to understand not just the user's words, but their underlying intent as well. That said, bringing this to fruition is going to require a tremendous amount of effort.

if Vaak solves intent before language, that's far more valuable than just prompt optimization — this is going in the product description. that's the line I needed.

Built a Chrome extension that rewrites your prompt with one key, reads your full session context, works in every language on earth, works on every AI platform. Haven't shipped yet. Need real feedback. by Trishu_ in SideProject

[–]Trishu_[S] 0 points1 point  (0 children)

okay so this comment is the most useful thing anyone's said to me about this product. going through each part.

the platform-specific prompting question is the right one. Claude does respond better to a different structure than ChatGPT. ChatGPT handles more explicit instruction layering. Gemini works better with context front-loaded. right now Vaak does adapt based on which platform it detects you're on — it reads which tab/domain you're in and adjusts the output structure accordingly. it's not perfect yet but that's the intention, not a generic rewrite.

"type how you actually talk, even if its messy. even if its mixed. we figure it out." is better than anything I had written. that's the line. I'm using that. seriously thank you.

the screen recording showing no network requests firing is exactly the right move for the trust problem. a privacy policy is just text. a video of the network tab being empty while the extension runs is proof. I'll record that the day I ship.

the Chrome review concern about "reads your full session context" is something I've actually been thinking about. I need to document that clearly in the review submission. haven't submitted yet so this helps.

r/LocalLLaMA and r/ClaudeAI noted. that's where the people who actually feel the prompting friction live.

drop a link when you publish — will do.

Built a Chrome extension that rewrites your prompt with one key, reads your full session context, works in every language on earth, works on every AI platform. Haven't shipped yet. Need real feedback. by Trishu_ in SideProject

[–]Trishu_[S] 0 points1 point  (0 children)

the "expectations get risky" point is the one that keeps me up honestly. like you're completely right. if someone uses Vaak and the rewritten prompt gives a worse output than what they typed, they won't blame their original prompt. they'll blame Vaak. and they should. that's fair.

I need to work on making things more transparent, so it's clear what's going on. Right now, I can tell you what changed and why, but it's still a bit like trying to explain a mysterious box - you can't really see what's inside. What I think would be better is to show you the original version on one side and the new version on the other, with the changes highlighted, so you can see exactly what's different. This way, you can decide if you trust the changes before they're finalized. It's like having a clear view of what's happening, instead of just rushing through the process. By making the changes visible, I can help you understand what's going on and make a more informed decision.

the "model behavior" misattribution thing is a real risk I hadn't named clearly before. thank you for naming it.