Tool Radar: Tools That Keep a Record of Your Work

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 notes app that holds your second brain. 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 two questions we bring to every tool

Before a tool earns a place in our own workflow, it has to answer two things. The first: 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.

The second, especially for solo freelancers: what happens to your data if this company disappears — can you export it? You carry your tools across years and clients, so the boring question of "can I get my stuff out" outranks any single feature.

There is a quiet thread running through this week's updates, and it is worth naming up front: the tools below all got a little better at keeping a record — of what changed, who changed it, and when. That is useful the moment a project starts to drift and you need to show what actually happened.

A tool that remembers what you did is doing two jobs: it speeds up the work, and it documents it.

AI: a new model is not a new workflow

New flagship AI models keep arriving in bursts, and the honest read for a freelancer is that the move which protects your work does not change when they do. Treat every output as a draft you review line by line, and watch what you paste in.

That second habit is the one that matters as the models get better and the temptation to hand them more grows:

• Read every line a client will see. A proposal outline, a scope description, a polite-but-firm payment reminder — all faster to fix than to start, and none safe to send unread. The model does not know your client; you do.
• Mind what you paste. Client names, rates, and project details are real business information. Use a tool you trust with that data, and check its retention and training policy before anything sensitive goes in. If that gives you pause, a local model runner that keeps the drafting on your own machine 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 a human reviews before anything goes out. Draft, then review — wherever the model runs.

Zed 1.18 turns your git history into a paper trail

Zed shipped version 1.18.0 on September 2, adding a "git: toggle diff base" action that flips the diff view between the latest commit and your default branch, inline debugger values for C and C++, a refreshed Markdown preview, and a file finder that now remembers recently opened files from previous sessions. A follow-up 1.18.1 on September 4 cleaned up terminal and navigation fixes.

For a freelance developer, the diff-base toggle is the quiet win. Being able to ask "what has changed since the branch started" in one keystroke is the same question a client asks in plain language — what did you actually do this month — and now you can answer it from the version history instead of memory. Git blame and a clear diff are underrated as a record: they say what changed and when, without you writing a paragraph at 11pm.

Zed is developed in the open on GitHub, which is the export test passing in the background — what you write is a plain file in a repo you control.

AppFlowy 0.14 puts a name on who changed what

AppFlowy released version 0.14.0 on August 28, adding space-level granular permissions — control over who can view or edit content at the Space level — plus two new database properties that automatically show who created a record and who last edited it. A 0.14.1 patch on September 1 fixed board creation on mobile.

Both changes remove a decision. Permissions mean you stop re-deciding, per client, who should see what; the created-by and last-edited-by fields mean the answer to "who touched this, and when" is already written down instead of reconstructed from a chat thread. For a freelancer sharing a workspace with a client or a subcontractor, that trail is worth more than it looks the day a disagreement starts.

AppFlowy is open source and self-hostable, so the export test passes on its own terms: the data can live on infrastructure you control.

Joplin 3.7.16 stops an edit from eating your work

Joplin shipped 3.7.16 on September 6 with a small but pointed fix: when you edit a note in an external editor, it now adds logic to avoid overwriting the note with older content. In other words, a stale sync no longer clobbers the newer version.

That is not a headline feature, and that is the point. The notes app is where your raw material lives — call notes, half-drafted scope language, the running log of what a client asked for. A tool that refuses to lose the newer version of that is doing the most important job a notes app has. Joplin is open source and supports encrypted, exportable notes, so this is the export test and the "your work survives" test in the same release.

The gap none of these close

The agreement around the work is the one record none of these tools keep. Your editor remembers your commits, your workspace remembers who edited a row, your notes app refuses to lose a draft — but what was promised, what counts as extra, and when you get paid still lives in scattered emails and good intentions. That is precisely the gap Drift Catch exists to close, and we are glad for the rest of your stack to be excellent; 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 the calm way through it is writing it down, which is what our guide on how to tell a client something is out of scope is for. 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, and if the recurring worry is the invoice rather than the scope, get paid on time is the practical version.

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.