texAi 2.0.4

texAi should now open every time.

Why it did not open. 2.0.2 was built as a single-file exe, and that kind of build leaves WPF's five native _cor3 DLLs outside the exe. The installer only copied the exe, so every launch crashed before any window or tray icon existed. The event log on the machine it was tested on shows 16 of these crashes between 21 and 23 September. 2.0.3 already shipped the full folder, but on that machine it was installed from a sandboxed terminal and never replaced the real copy. Installing 2.0.4 normally fixes that.

If a file is ever missing again, texAi now shows a message naming the file and the Windows error. Before, it just vanished.

Opening texAi shows the dashboard. Clicking texAi from the Start menu or desktop opens the dashboard, including when it is already running in the tray. That second click used to do nothing at all. Starting with Windows still stays quietly in the tray.

The auto-updater could have looped. It never deleted the installer it had downloaded, so after an update texAi would have found it and run it again, over and over. It now checks the installer's version and throws it away once that version is installed.

Installing over any earlier version keeps your model, tone and hotkeys in %AppData%\texAi\settings.json.

texAi 2.0.3

Fixes an install that started but never opened a window.

The app would not open. texAi was published as a single-file exe, which unpacks its native WPF libraries into %TEMP%\.net every launch. When that unpacked copy is missing or half-written, the first window WPF creates throws DllNotFoundException from inside a window procedure, and Windows kills the process with nothing on screen. The tray icon would appear, or not, and the dashboard never came up. texAi now ships as a normal folder of files, so there is no unpacking step to fail. It also opens about a second faster.

The updater would have looped. 2.0.3 was tagged v2.0.2 but built from a project still versioned 2.0.1, so the background updater compared the tag against its own version, decided it was out of date, and would have reinstalled the same release every twelve hours. The project, the installer and the tag all say 2.0.3 now.

Installing over 2.0.2 or earlier is safe: your model, tone and hotkeys in %AppData%\texAi\settings.json are left alone.

texAi 2.0.2

An app icon (exe, taskbar, installer), a readability pass on the dashboard's UI font, and a silent background auto-updater: texAi now checks this repo's releases every 12 hours and stages a newer installer without interrupting anything. It's applied automatically the next time the app starts.

texAi 2.0.1

A bug fix on top of 2.0, plus a walkthrough video.

Fixed

texAi gave up on a busy clipboard far too quickly. The retry budget was three attempts 30ms apart, so it stopped trying 90ms after the first refusal and reported "Clipboard is locked by another app", leaving your text unchanged. Clipboard managers, sync agents and remote desktop clients hold the clipboard longer than that as a matter of course.

This showed up as roughly one failure in four during ordinary use. Retries now back off over about a second.

Video

texai-walkthrough.mp4 is a 65 second run through all four hotkeys and the dashboard. The shorter loop is at the top of the README.

Install

Run texAi-Setup.exe. Per-user, no administrator rights. You need Ollama and a model first. Upgrading over 2.0 keeps your settings.

texAi 2.0

texAi is now an application rather than a background process you have to take on faith.

The bug this fixes

Pressing a hotkey in Firefox opened the developer tools and did nothing to your text. A global hotkey fires on key-down, so texAi ran while you were still physically holding the chord, and injecting Ctrl+C on top of a held Shift made the app receive Ctrl+Shift+C. That is the DevTools element picker. Nothing was copied, so the rewrite then failed on empty input. The intermittent red dot and the Firefox popup were the same defect.

texAi now waits for you to release the chord before injecting, and forces the key-ups if you are still holding after 400ms.

Hotkeys have changed

Ctrl+Alt+G / T / R / F for grammar, translate, rewrite and tone.

They were Ctrl+Shift, which was a mistake: a global hotkey outranks whatever app is focused, so texAi was taking "reopen closed tab" away from every browser, hard reload, and find-in-files in VS Code. All four are now rebindable.

Failures say what happened

Every failure used to look identical: one red dot. The dashboard's Errors list now distinguishes nothing selected, the app not responding, the clipboard being locked, Ollama not running, the model not being installed, a timeout, and an empty response.

A dashboard

Open it from the tray. Activity is what you rewrote this session, Errors is what went wrong, Models lets you pull, delete, switch and compare models with real download progress, and Settings holds the model, tone and hotkeys.

Your rewrites are kept in memory only. The one file texAi writes is %AppData%\texAi\settings.json, and it contains no text you have rewritten.

Other fixes

• The progress indicator now sits beside the caret's line rather than floating above it, and is positioned in physical pixels so it lands correctly on scaled displays.
• Your clipboard is properly restored. It was being emptied.
• keep_alive: 30m and a preload at startup, so coming back after a break no longer times out while Ollama reloads the model.

Which model

Default is qwen2.5:7b. Tested against aya-expanse:8b and gemma2:9b on an RTX 2060 6GB; the table and the reasoning are in the README. Short version: gemma2 is the only one that handles romanised Bangla, at about three times the latency, and it is one click away in the dashboard.

Install

Run texAi-Setup.exe. Per-user, no administrator rights. You need Ollama and a model first.