I Wrote a Sentence My Subtitle App Couldn't Understand. Eight Months Later, It Can.

TL;DR: In March I wrote that a good AI product should make you "dumber" at something, and admitted GeekLink wasn't there yet: you still had to learn its buttons. GeekLink 0.5.0 (October 8, 2026) added Connect AI, which lets an AI assistant operate GeekLink through MCP. You send one message, such as "extract the subtitles, translate them into English, show me uncertain lines, then export an SRT," and the assistant runs OCR, transcription, translation, review and export inside the app. Connect AI is currently Mac-only and included with Lifetime plans. GeekLink itself runs on Mac and Windows.

This is a founder's note about a GeekLink feature. The capabilities and limits below describe the current release, not a promise that an AI assistant gets every subtitle right.

The sentence my app couldn't understand

On March 2, 2026, I posted a short note on Xiaohongshu. For about a month I had been dictating almost everything to an AI voice-typing tool while I wrote code at home. I'd hold a key, ramble through half-formed thoughts and filler words, let go, and get back a tidy paragraph.

Then I noticed something uncomfortable: I was getting worse at writing on my own. The AI covered for me so reliably that my brain had stopped bothering to organize the words.

At the end of that note I wrote down a sentence I wished I could say to my own product:

GeekLink couldn't understand that. It understood buttons.

Why a good AI product should make you "dumber"

My conclusion sounded harsh, but I still believe it. People don't buy software to train themselves. They buy it so they can stop thinking about something. If an AI tool needs real expertise before it's useful, it's an assistant for experts, not a product for everyone else.

Every big tool has done this. Calculators took away mental arithmetic. Cars took away the need to handle a horse. Traditional software built its moat the other way: years of muscle memory. Designers can find a Photoshop filter with their eyes closed, and that habit keeps them from switching.

When you can describe the result in a sentence, that muscle memory stops being worth much. Understanding intent replaces operating the tool. The AI does the tedious work; the person makes the decisions.

GeekLink wasn't there yet

In the same note I admitted the gap. GeekLink was an automation workflow: drop in videos, click run, get subtitles. That's useful, but you still had to learn where everything was. Which lines on screen are subtitles. Which language each line is in. Where the review flags are. Which export format you need. I wrote that the "understands plain language" version was still some distance away.

How the gap actually closed

It closed faster than I expected, and for a less glamorous reason than styling.

When GeekLink extracts burned-in subtitles, it flags lines it isn't sure about. Checking those flags meant going back to the video, finding the frame and comparing it with the text, one line at a time. In late September I built an MCP server so an AI assistant could do that part for me: read the flagged lines, pull up the frames behind them and tell me which ones were actually wrong. At first it was only for my own work.

Once the assistant could check frames, it was a short step to letting it run the rest of the workflow. Less than two weeks later, GeekLink 0.5.0 shipped Connect AI in the app. In 0.5.1 we added a general config, so any local AI app that supports MCP can connect, not only the two with one-click setup.

What your AI assistant can do in GeekLink now

Click Connect AI (MCP) in GeekLink's top bar, pick your AI app, restart it, and keep GeekLink open. Then you describe the result you want. A typical message:

The assistant plans the steps and GeekLink does the processing:

• Extract burned-in subtitles. It looks at the candidate subtitle regions, chooses the lines and languages, and runs OCR.
• Transcribe speech. Local, Whisper-based transcription produces timed subtitle drafts. It asks how many people are speaking before it starts.
• Translate. It uses the translation service you've selected in GeekLink, or runs transcription and translation as one task.
• Review uncertain lines. It reads flagged lines and inspects the matching video frames. A flag is a reason to look, not proof of an error.
• Edit and export. It works through GeekLink's own editor controls, then exports SRT or TXT, a toggleable subtitle track, or a burned-in video.

You can watch real, unedited runs on the Connect AI page: three episodes of burned-in Chinese subtitles translated into English, and three videos with no subtitles turned into checked German subtitles, each from a single message.

The rule that mattered most: what the AI must not do

The hardest design work wasn't making the assistant capable. It was deciding what it must not do on its own.

In OCR, deleting a real subtitle line is the worst kind of mistake. Nothing crashes and nothing looks wrong, so nobody notices until a viewer hits the gap. GeekLink's own rule is "detect too much rather than too little," and the assistant has to follow it too:

• Before it removes a suggested subtitle line, it has to look at frames where that line actually shows text, not a single thumbnail.
• Every removal needs a stated reason, and you can see those reasons afterwards on the line-selection screen.
• It must keep at least one line, and it has to state the video's language explicitly instead of falling back to a default.

That's the same split I wrote about in March. The machine does the repetitive checking, and you decide what ships.

What it doesn't do yet

• Mac only, for now. GeekLink runs on Mac and Windows, but Connect AI currently works only in the Mac app. On Windows, the same OCR, transcription, translation, review and export features are available directly in the app.
• Lifetime plans. Connect AI is included with Lifetime plans. It doesn't add a separate credits plan: export limits still apply, and cloud translation uses your GeekLink AI credits.
• Not fully offline. OCR and transcription run on your computer, but tool results and any video frames the assistant asks for are shared with the AI app you connect, under that app's data policies.
• One heavy task at a time. The assistant can queue work across your library, but GeekLink processes one heavy task at a time.
• No ChatGPT web connection. It's a local connection on your Mac, not a remote MCP endpoint.

And the sentence from March? Before publishing this post, I sent it to my AI assistant word for word: "Make the subtitles white with a yellow outline, and put them 20% from the bottom." It worked out that 20% of a 720-pixel-tall video is 144 pixels, saved GeekLink's burned-in subtitle style, and rendered a preview frame. White text, yellow outline, 20% from the bottom. Burned-in exports now use that style.

What I believe now

I used to think of AI as a tool. Now it feels more like an external brain that happens to know where all the buttons are.

For subtitle work, that changes who the product is for. You no longer need to learn subtitle software to get finished subtitles. You need to know what you want, and you need to check the lines that deserve a second look. GeekLink's job is to make that list of lines as short as possible.

If you've used a piece of software for years, which menus would you happily forget forever? Tell me at support@geeklink.dev.

FAQ

For setup details, see the Connect AI guide.

Disclosure: GeekLink is our own desktop app. Connect AI, OCR, transcription, translation, review and export described here are GeekLink features.