Tool Radar: Local-First Tools and the Export Test

Welcome back to Tool Radar, our running note on the adjacent tools worth a freelancer's attention — the AI you draft with, the editor you ship from, the design app you mock up in. Not other freelance-management apps; the rest of your stack.

Nobody pays to be here, and this is not a review site. It is the kind of message we would send a freelancer friend who asked "what should I be paying attention to right now?"

The filter this week: can you get your data out?

Every tool below passes one unglamorous test: if its maker disappeared tomorrow, you could still open your files and take them with you. That is the second question we bring to every tool, and it earns its own edition this week because the tools that changed recently happen to be the ones that answer it well.

The first question is the one we ask about everything: does it remove a decision, or does it just add a tab? A good tool folds a recurring choice into a default. A bad one demos well and then sits open in a browser tab you forget about by Thursday.

A tool you can walk away from is working for you, not the other way around.

Hold both questions against every tool below — and against anything anyone recommends to you.

Ollama: drafting with AI that stays on your laptop

Ollama shipped v0.32.15 on August 19, adding a first-launch onboarding flow to its desktop app and caching that makes a model start responding noticeably faster on repeat runs.

The freelancer angle is not the speed bump — it is where the drafting happens. Ollama runs language models locally, on your own machine, so the client names, rates, and project details you paste into a draft never leave your laptop. If you have ever hesitated before pasting a client's brief into a cloud tool, that hesitation is the whole point.

New cloud models keep landing at a pace that is hard to keep up with, and most of them are genuinely capable. But the question a freelancer can actually act on is not "which model is best this month" — it is "where does my client's information go when I use it." A local runner is one clean answer.

This is also the shape we trust for AI inside our own product: our AI-Assisted Drafting on templates produces a draft that a human reviews before anything goes out. Draft, then review — whether the model runs in the cloud or on your desk.

Zed: a code editor that now reads your spreadsheets

Zed's v1.17.2 release on August 26 added built-in previews for CSV, TSV, and similar delimited files — sortable and resizable columns, row filtering by value, and right-click copying — alongside new Git blame and stashing actions.

For a freelance developer, this quietly removes a decision. A client sends a data export; instead of opening a separate spreadsheet app to eyeball it, you read it where you already are. And Git blame is underrated as a record: it answers "when did this change, and in which commit" without you writing a paragraph from memory. When a project starts to drift, that history is evidence of what you actually did and when.

Zed is developed in the open on GitHub, which is the export test passing in the background — the thing you write is a plain file in a repo you control, not a document trapped in someone's cloud.

Penpot: design files developed in the open

Penpot's current 2.17 line moved the prototype viewer to a WASM (Skia) rendering engine in 2.17.0 (July 22), and the most recent release, 2.17.2 (August 27), is a maintenance and security update rather than a headline feature.

So there is no shiny new thing to chase this week — and that is fine. The durable reason a visual freelancer might keep Penpot on the radar is the same export test: it is built in the open on GitHub, and your design files stay yours to move. A slow-news week for a tool you can walk away from is a good problem to have.

The freelancer reading here mirrors the developer one above: the tool that keeps a clear, portable history of what you delivered and when is doing double duty. It speeds up the work, and it quietly documents it — which matters the moment a client says "go back to the version from last week."

The gap none of these tools touch

The agreement around the work — what was promised, what counts as extra, and when you get paid — is the one thing none of the tools above manage, no matter how portable your files are. Your editor, your AI runner, and your design app all help you do the work. They stay silent on the deal.

That silence is the entire reason Drift Catch exists. We are glad for the rest of your stack to be the best it can be, and we do not connect to any of it — we just want the business side to stop leaking. If "small extra requests that were never agreed to" sounds familiar, that pattern has a name — scope creep — and there is a calmer way to handle it: writing it down. Our guide on how to write a change order is the practical version of that. And if keeping your own data close is a running theme for you, our note on privacy-first freelance software explains how we think about it on our side of the fence.

This is general information, not legal or financial advice.

We run Tool Radar regularly. If there is an adjacent tool you think every freelancer should know about, tell us at ideas@driftcatch.app — we read every message, and good suggestions tend to show up in a future edition.