<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Wrenio Studio</title>
    <description>The latest articles on DEV Community by Wrenio Studio (@wrenio_studio).</description>
    <link>https://dev.to/wrenio_studio</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4094310%2Fb6547937-6da0-4630-8cb3-d2c670317592.png</url>
      <title>DEV Community: Wrenio Studio</title>
      <link>https://dev.to/wrenio_studio</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/wrenio_studio"/>
    <language>en</language>
    <item>
      <title>I Work All Day in a Language That Isn't My First. So I Built the Tool I Kept Wishing Existed.</title>
      <dc:creator>Wrenio Studio</dc:creator>
      <pubDate>Tue, 25 Aug 2026 13:55:46 +0000</pubDate>
      <link>https://dev.to/wrenio_studio/i-work-all-day-in-a-language-that-isnt-my-first-so-i-built-the-tool-i-kept-wishing-existed-ckc</link>
      <guid>https://dev.to/wrenio_studio/i-work-all-day-in-a-language-that-isnt-my-first-so-i-built-the-tool-i-kept-wishing-existed-ckc</guid>
      <description>&lt;p&gt;&lt;em&gt;A solo founder's honest look at ClipWise, an AI reading and writing assistant for Windows and macOS, including the things it deliberately doesn't do.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I read and write in English all day, but it isn't my first language. That creates two kinds of friction. Incoming text takes longer to understand, especially when it's dense or unfamiliar. Outgoing messages take longer because I keep checking the grammar, phrasing, and tone before I dare hit send. And sometimes I know exactly what I want to say, but speaking the thought is much easier than typing it clearly.&lt;/p&gt;

&lt;p&gt;My fix, for years, was a stack: a grammar checker in the browser, a translation tab, a chatbot for the important emails, an OCR utility for text stuck in screenshots, a speech-to-text app, and a clipboard manager. Each solved one part of the problem. Together they meant several subscriptions, several shortcuts, and a workflow that was mostly switching, prompting, copying, and pasting.&lt;/p&gt;

&lt;p&gt;At some point I noticed that almost all of those trips started the same way: with something I had just selected, copied, or wanted to say. So I built ClipWise: an AI reading and writing assistant for Windows and macOS that lives in the system tray or menu bar and works across almost any app. The promise I built it around: understand what you read, say what you mean.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works
&lt;/h2&gt;

&lt;p&gt;Two ways to begin. Select or copy text and choose an action. Or press the voice shortcut and speak.&lt;/p&gt;

&lt;p&gt;The 13 one-click actions (10 for text, 3 for images) sort into the two jobs. For understanding what comes in: Summarize, Clarify, Translate across 21 languages (including right-to-left Arabic and Persian), Fact Check, and Action Items. For saying what goes out: Rewrite, Shorten, Expand, Structure, and Draft Reply. The result pastes straight back where you were working; there's no chatbot window in the loop.&lt;/p&gt;

&lt;p&gt;The workflow that changed my own day: I draft a reply in my language, fast and precise, the way I actually think. Then Rewrite to clean it up, and Translate to turn it into natural English. A couple of clicks, and the finished reply lands back in the same email field.&lt;/p&gt;

&lt;p&gt;Voice is the second starting point, not an afterthought. Press the shortcut, speak for up to 60 seconds, and the recording becomes a clean transcript you can copy, rewrite into clear prose, or translate. Nobody speaks the way they want to write; ClipWise assumes your spoken draft is the rough version and helps you finish it.&lt;/p&gt;

&lt;p&gt;And when text is trapped in a screenshot, a slide, or an unselectable PDF, the built-in capture plus Extract Text pulls it out and feeds it into the same actions.&lt;/p&gt;

&lt;h2&gt;
  
  
  The privacy part
&lt;/h2&gt;

&lt;p&gt;The clipboard sees everything, so this mattered to me from day one. Clipboard history lives in a local database on your own machine and never syncs anywhere. A detector with 21 patterns recognizes passwords, API keys, and tokens, keeps them out of history, and blocks them from ever being sent to any AI provider. Your own API keys live in the OS keyring. And if you want zero cloud, you can run a compatible local Ollama model: supported actions run entirely on your machine, free, no API key involved.&lt;/p&gt;

&lt;p&gt;Otherwise, pick your engine: ClipWise's managed AI (sign in, no API key, free daily allowance), or your own OpenAI or Anthropic API key.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it deliberately doesn't do
&lt;/h2&gt;

&lt;p&gt;I want to be straight about the trade, because the specialist tools are good at what they do. ClipWise has no live as-you-type underlines; it works on demand, on text you select or copy, so Grammarly still owns that trigger model. It translates the snippets you copy, not whole documents with formatting, so DeepL keeps that job. It records voice notes rather than streaming dictation into your cursor, and it doesn't transcribe offline. The clipboard history has no search or sync yet. There are no mobile apps: it's Windows and macOS (Apple Silicon, macOS 12+).&lt;/p&gt;

&lt;p&gt;For any single one of these jobs, the category leader goes deeper. What I wanted, and what I built, is the everyday version of all of them in one place, where the work is already happening.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it costs
&lt;/h2&gt;

&lt;p&gt;The free plan has no time limit: currently 10 managed AI actions a day, with clipboard history and screenshot capture free regardless. Paid plans start at $4.99/month. BYO-AI is $29.99/year for unlimited ClipWise actions with your own OpenAI or Anthropic API key (the provider bills its own usage separately), or a compatible local Ollama model at no cost. For comparison, a grammar-checker subscription plus a dictation subscription typically runs about $24 a month, and neither translates.&lt;/p&gt;

&lt;h2&gt;
  
  
  The build, for the curious
&lt;/h2&gt;

&lt;p&gt;Since this is DEV, a few notes on how it's put together. ClipWise is a Tauri 2 app: a Rust backend paired with the system webview, with the UI in React 19 and TypeScript. Clipboard history is local SQLite. Voice capture runs through native Rust (16-bit WAV from the OS microphone), not the browser recorder. The sensitive-content detector runs twice, once in the frontend and again in the Rust backend, as defense in depth. BYO API keys go into the OS keyring (Windows Credential Manager / macOS Keychain), never into config files or the web layer. Updates are ed25519-signed independently of the platform code-signing. And the Ollama integration means the whole AI path can stay on your machine: point ClipWise at a compatible local model and supported text and image actions never touch the cloud.&lt;/p&gt;

&lt;h2&gt;
  
  
  The point
&lt;/h2&gt;

&lt;p&gt;I didn't set out to beat any specialist at its own game. I set out to remove a specific, daily, compounding friction: the trip your text makes between the app where you work and the tools that make it better. If you work in a language that isn't your first, that trip happens forty times a day, and shortening it changes how confident everything you send sounds.&lt;/p&gt;

&lt;p&gt;If that friction sounds familiar, ClipWise is at &lt;a href="https://wrenio.studio/clipwise" rel="noopener noreferrer"&gt;wrenio.studio/clipwise&lt;/a&gt; and the free plan needs no API key and no credit card, so you can find out in an afternoon whether it sticks. I'd genuinely like to hear what's missing: &lt;a href="mailto:support@wrenio.studio"&gt;support@wrenio.studio&lt;/a&gt; reaches me directly.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Understand what you read. Say what you mean.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>ai</category>
      <category>rust</category>
      <category>buildinpublic</category>
    </item>
  </channel>
</rss>
