What's new

CaseDesk is in free beta. Every build carries its own version number, shown in the app and in the installer filename, and from v1.0.1 onward the app offers new builds in-app — nothing installs without your click. The SHA-256 on the download card lets you verify any download. Your 90 free days are tied to this machine's first run, so installing a newer build doesn't restart them.

September 16, 2026 v1.0.49 — current build, Windows, Linux & macOS You’re here

The phone companion grows up. The phone app now talks to your sync account directly and ships as a real build rather than a prototype. An enrolled phone goes straight to your cases — it no longer shows the join form every time you open it. The case list groups by status and sorts the ways a practice actually reads: by carrier, with each carrier’s matters grouped under its own heading, or by firm, so Hartford matters and your own filings stay in their own piles. A carrier chip on each row tells you whose file it is at a glance.
Case briefs on the phone stop losing text. The brief that feeds the phone view is cleaned of the boilerplate that used to ride along — and the cleaner itself was fixed. It no longer eats characters out of the sentence it is tidying, and when a line carried both a document reference and something the brief actually needed to say, the whole line used to go; now the reference goes and the facts stay. Counsel is filed under the party it represents, so the phone shows who is acting for whom instead of a flat list of names.
A deleted case stays deleted. Deleted matters could reappear on a phone after a re-download, because the sync history replay put them back. The download path now clears what it is replacing first, and the server’s snapshot bookkeeping was corrected so deleted rows are not re-materialised. The one-time cost is a single fresh download on each phone; after that, deletions stick.
Sync that tells you where it is stuck. When a phone cannot finish pulling, Settings now names the exact change it is blocked on instead of sitting at “syncing”. Writes that a phone could not have read are refused at the door, with the reason, rather than landing in the database and failing silently on the device.

September 15, 2026 v1.0.48 — Windows, Linux & macOS

Today: one list of what needs you first. Deadlines, follow-ups, outstanding discovery and the email pile used to live on four screens with nothing ranking them against each other. Today puts them in one ordered list — a hard court date that is overdue at the top, a stale follow-up that has already been nudged twice above a soft internal target a week out — and every row says in a few words why it sits where it does. You can mark a deadline done, move it, log a nudge, or mark discovery responded without leaving the page. CaseDesk now opens on Today; Settings → Appearance switches it back to the Dashboard.
AI advise, on request only. A button on Today asks the AI you have configured for a short read of the list: what to do first, what can wait, what looks like it is slipping. It sees titles, matters, dates and ages — never your notes, never email text — it names the model that answered, and it never runs on its own.
Email sorted into piles before you read it. Pending mail is now split into Needs review, Case mail, Sent by me, Marketing, Automated notices and Personal. Your own sent mail, job-board blasts, vendor receipts and verification codes are sorted by rules with no AI at all; the AI Sort button works only on what is left, and each pile can be cleared with one click. A pile is a label, not an action: nothing is filed or deleted until you say so.
Moving a deadline now records why. A Move button on every deadline takes the new date, a reason and a note, and keeps the history. Soft and internal target dates move freely and have one-click snooze; a hard court or statutory date moves only on a court order or a stipulation, and the app refuses anything else. The firm-wide Deadlines list gains Edit, Delete, a matter filter and a search box.
Overdue deadlines now actually notify. The desktop reminder fired only on exactly 7, 3, 1 or 0 days out, so a deadline missed while the app was closed stayed silent forever. An overdue deadline now reminds you once a day until it is done or moved, and every reminder is written to the log.
Follow-ups became a work queue. Search; filters for matter, person, age, priority and how many times you have nudged; sort by oldest wait, priority, matter, person, or “what to chase first”; holders collapse when there are many; priority and matter number on every row; checkboxes with Chased all and Done all.
Reassigned matters leave your desk. A matter transferred to another attorney at the firm no longer appears on your dashboard, deadline list, discovery list, badge or notifications. A checkbox brings it back when you want the firm-wide view. Calendar cleanup and sync still treat it as owed, so nothing is removed from a real calendar.
Discovery page fixed. The table no longer clips its Status column and Mark responded button off-screen, matter names no longer wrap into a sliver, and an Extend button moves a due date with a reason.
Fewer one-click surprises. Deleting a trust bank account now asks first. Rounding a matter’s time entries to six-minute increments says how many entries it will change and asks first. Resolving a pending question can be undone for eight seconds. Contact cards show the matter number and their edit and delete buttons are reachable by keyboard. Several tables that clipped their action column now scroll.

September 9, 2026 v1.0.47 — Windows, Linux & macOS

Follow-ups: a list of everything you are waiting on someone else for. A deadline is a date the court imposes. A follow-up is a ball in somebody else’s court — a draft sent to a partner for approval, responses owed by a client, a stipulation sitting with opposing counsel. Nobody sets a due date when a draft goes out, so a follow-up is tracked by age instead: who has it, and how long they have had it. There is a new Follow-ups page for the whole firm, a Follow-ups tab on each matter, and a “Waiting On” panel on the dashboard showing the oldest ones first.
Grouped by the person, not by the matter. When you chase someone you chase them once, about everything — not once per file. The list gathers every open item by whoever is holding it, oldest wait at the top, so one person’s whole backlog reads as a single block. Items age from grey to amber at three days and to red at a week, counted from the last time you nudged rather than from the day it went out.
One click writes the whole chase email. Next to each person is a button that opens a message listing everything they owe you, grouped by matter, each line carrying how long it has been out, when you last followed up, and the real deadline it is holding up if there is one. You choose the recipient every time — CaseDesk never fills in an address for you.
Your private notes stay private. The note you attach to a follow-up is for you: your reasoning, what it cost, where it came from, what you think of the other side’s position. A chase email is often addressed to opposing counsel, a carrier or a client, so the message CaseDesk writes carries only what a chase needs — what is outstanding, how long it has been, and the deadline it is holding up. Nothing you wrote privately is ever put into it. The one thing that does go out is the item’s title, and the app tells you so where you type it.
One person is one entry, however you typed their name. Follow-ups gather by the contact, not by the spelling, so items logged against “Todd Knudsen”, “Todd P. Knudsen” and “todd knudsen” are one list rather than three partial ones. Two different people who happen to share a name stay separate.
“Chased” restarts the clock without losing the history. Marking that you nudged someone today moves the item back down the list and counts the reminder, while still showing the date it originally left your hands. A thing sent three weeks ago and chased yesterday reads as exactly that, rather than looking either urgent or handled.
A follow-up never becomes a deadline. Nothing here writes to your calendar or your deadline list, because two entries claiming the same date is how a calendar stops being trusted. If a follow-up is holding up a real deadline you can link it, and the item then shows that date as context — “needed before June 21” — while the deadline itself stays the single copy.
The assistant can read and update the list. It can log what you sent and to whom, record a nudge, mark items done, and draft the day’s chase emails from what is actually outstanding. It reports what it cannot do rather than reporting success, and it will not guess an email address.

September 8, 2026 v1.0.46 — Windows, Linux & macOS

California discovery cutoffs were landing days early. When a discovery cutoff falls on a weekend or a holiday, the Civil Discovery Act moves it to the next court day closer to trial — forward, which is the opposite direction from almost every other deadline. CaseDesk moved it the other way. On a trial set for July 19, 2027 that put the discovery cutoff on Thursday June 17 instead of Monday June 21, and the expert cutoff on Friday July 2 instead of Tuesday July 6, each one marked as a hard court date. An early cutoff is not the safe kind of wrong: it contradicts the date you calculated by hand, and it teaches you to stop trusting the automatic ones.
You can now correct the trial date those cutoffs count from. California measures them from the date trial was initially set, not from the current one, so that original date matters long after it has passed. CaseDesk recorded it the first time it saw a trial date — which, for a matter added after a continuance, was already the continued date, with no way to put it right. It is editable now, and changing it recalculates the dates that depend on it.
The assistant now tells you when it cannot save something, instead of saying it did. If you asked it to fill a field it had no way to reach, it reported success and wrote nothing — and the reply looked exactly like a real one. It now names the field it could not write and changes nothing, so a record never quietly disagrees with what you were told. The same is true of editing or deleting something that is no longer there: that used to come back as done.
The assistant can edit a deadline’s description, its priority, its time and its location. Previously it could change only the title, date, status and notes, so correcting a misleading description meant deleting the deadline and building it again — which loses the original and anything pointing at it.
A deadline’s notes are shown when the assistant reads it back. It could write them but never see them, so notes you added through it were invisible to it afterwards, and a note stored on a deadline could look as though it had never been saved.
Recording something that already happened no longer puts a new deadline in the past. Entering a deposition that took place last month, or discovery served last year, was generating fresh hard deadlines dated before today. When you are filling in history rather than starting a clock, you can now say so.
A deposition noticed by the other side no longer creates an obligation on your calendar. The notice deadline belongs to whoever noticed the deposition; CaseDesk was calendaring it for you either way.
Matters no longer claim binding arbitration unless someone said so. The field defaulted to yes, so a matter with no arbitration anywhere in its file still read as being in binding arbitration. The same applied to insurance: a layer with nothing entered was recorded as the primary policy and as one whose carrier pays your fees. Nothing entered now reads as nothing entered, and existing records created that way are corrected on upgrade.
An expert’s status on a matter can be changed after you add them. Every expert stayed on whatever status they were created with, so people who had served reports months earlier still read as pending.
Names can no longer be stored with web punctuation in them. A firm called Rodman & Associates could end up saved with the raw & in place of the ampersand and then print that way on anything that used the name. CaseDesk refuses the value and tells you, rather than storing it.

September 8, 2026 v1.0.45 — Windows, Linux & macOS

You can finally read how a deadline was calculated. For every automatic deadline CaseDesk has always recorded the rule it applied, the date it counted from, the base deadline before service extensions, and the last day to serve by each method — and it kept all of it in the deadline’s notes field, which no screen ever displayed. An automatic deadline now carries a How this date was calculated link that shows exactly that.
And it can no longer be wiped by accident. Notes is the same field you type into, and anything that rewrote it replaced the whole thing — so a single edit made through the assistant could erase how four deadlines were computed, with nothing to restore from. The engine’s record now lives somewhere an edit cannot reach. Your notes on a deadline are yours alone.
A deadline that was already overdue when it was calculated says so on the list. That warning had been stored in the same notes field, so it vanished along with everything else whenever the field was rewritten.
A matter you only monitor no longer counts against you. Where you are monitoring counsel, another firm answers the discovery and calendars the dates — the point of monitoring is to notice when they are about to miss one. CaseDesk had been treating those dates as yours, so a set of form interrogatories on a monitored matter read as 314 days overdue when the response was never yours to serve. Those deadlines are now softened: they stay in every list, keep their real dates, and are marked Monitoring, while leaving the reminder badge, the overdue count and the red styling. Nothing is hidden — a monitored deadline that disappeared would take away the very thing monitoring counsel is there to do. A matter whose role you have not recorded is treated as yours, so an unfilled field can never quietly switch off a warning.
One name per kind of discovery. The same request could be stored under several spellings depending on where it came from — the form, the assistant, an imported document — and only some of them were recognised. That is what stopped requests recorded under their full names from producing a response deadline earlier this month. There is now one list used everywhere and existing records are converted to it. A name CaseDesk does not recognise is left exactly as you entered it rather than being quietly changed into something it is not.
Mark a set responded straight from the Discovery dashboard, instead of opening the matter to find the row. It asks for the date the response was served rather than assuming today, because that date starts the 45-day clock for a motion to compel further responses. The type filter also offers every type now — it listed six of the ten, so a matter whose only discovery was an inspection demand could not be filtered to at all.
Calendar entries for matters that left your firm can be removed. CaseDesk stopped sending new ones for closed, dismissed and transferred-out matters last release, but anything already on your Google or Outlook calendar stayed. Settings now lists exactly which entries those are and removes them on your say-so — never automatically, because deleting reaches into a calendar other people may share. A matter reassigned to another attorney at your own firm is deliberately left alone: the firm still owes those dates.
Sort the case list by any column, and see which firm a matter belongs to. You could already filter by firm without being able to see it. Matters with nothing in the column being sorted always sort to the bottom, so an empty trial-date column never reads as a list of imminent trials.
Undo after marking a deadline complete. One click marks it done; the only way back was to find the row and click again. The confirmation now offers Undo, and it restores the status the deadline actually had.
Nine of the assistant’s tools asked for information under one name and CaseDesk read it under another, so what it sent was thrown away. Creating a deadline, adding a docket entry and recording discovery were the serious three — each dropped something the record cannot be saved without. Adding insurance lost the carrier; recording a settlement offer lost who made it and its terms; editing or deleting a cause of action or docket entry could not find the record; and saving practice-area details accepted everything, stored nothing, and reported success. All nine now ask for exactly what the program reads.

September 8, 2026 v1.0.44 — Windows, Linux & macOS

Discovery you had already recorded went back to producing its deadlines. The previous release stopped CaseDesk from inventing response deadlines for devices nobody had served — but it recognised only the short way of naming a device. Requests for production and requests for admission recorded under their full names were read as a kind of discovery CaseDesk had never heard of, and produced no deadline at all, silently. Every spelling the app has ever stored is now recognised, and a name it genuinely does not know is written to the log as a gap rather than passing unnoticed.
A discovery type CaseDesk didn’t have in its list no longer looks blank — or quietly changes when you save. If a request was stored under a name the dropdown didn’t offer, the box rendered empty, so the item read as untyped; opening the form and saving replaced the stored name with whatever the box happened to show. The stored value now appears in the list, marked as stored, and survives a save untouched.
A case status CaseDesk didn’t recognise no longer hides the matter’s deadlines. The firm-wide deadline list, the reminder badge, the assistant and the charts each worked from a list of statuses they would show. Anything outside that list — a status written by the assistant, or one from an older build — fell through and took the matter’s deadlines off every one of those surfaces at once. They now work the other way round: a matter is shown unless it is closed, dismissed, or transferred out of the firm, so an unfamiliar status can never make a deadline disappear.
Handing a file to another attorney at your own firm no longer takes its deadlines off your calendar. Transferred, added last release, covered two different things: a matter reassigned inside the firm, where nothing was filed and the firm is still counsel of record, and one substituted out to another firm, where it isn’t. Treating both as gone hid dates the firm still owed. A transferred matter now records which of the two it was, and only an out-of-firm transfer removes it from firm-wide lists. Leaving it unrecorded is a valid answer and keeps the matter on those lists — a transfer is often known before the paperwork exists, and dates you still owe should not vanish on the strength of an assumption.

September 8, 2026 v1.0.43 — Windows, Linux & macOS

CaseDesk no longer invents discovery response deadlines. Recording that any discovery had been served produced the same three deadlines every time — interrogatories, requests for production and requests for admission — whatever had actually been served. A matter whose only discovery was a subpoena, and one whose only records were deposition categories, each got three deadlines citing a Code section for a demand nobody had served. CaseDesk now looks at what was served: interrogatories produce the interrogatory deadline and nothing else, and a subpoena or a deposition notice produces none, because neither carries that response clock.
Serving a second set no longer erases the first one’s deadline. Recording an RFP deleted the interrogatory response deadline recorded the week before. Each served item now keeps its own.
Deadlines on matters you have closed, dismissed or transferred stop following you. The overdue list, the reminder badge, the assistant, and the deadline charts all counted them, so a file that had left the firm kept demanding attention and the badge could disagree with the list it sat above. All of them now agree. Settled matters are deliberately still included — a settlement still owes the dismissal, the release and the liens. Nothing is deleted: every deadline is still on its own case.
Deadlines for transferred and closed matters are no longer sent to Google Calendar. Entries already there are left alone rather than deleted.

September 7, 2026 v1.0.42 — Windows, Linux & macOS

A matter that leaves your firm is no longer recorded as closed. When a case is substituted out or the file goes to another firm, nothing has ended — someone else is carrying it, and your malpractice and tail-coverage position is not the same as on a closed file. There is now a Transferred status, with its own place to record where the file went, when, and why. None of it is required: a transfer is often known before the paperwork exists, so a transferred matter with no transferee recorded reads as “not recorded yet” rather than an error.
Time already billed somewhere else stays billed. If you bill through another system and mirror the work into CaseDesk, those entries used to look like unbilled work in progress — and an invoice run would have swept them up a second time. An entry can now be marked as billed outside CaseDesk, and every place that asks what is still billable — invoices, the unbilled alerts, the recurring schedule and the four work-in-progress figures in reports — honours it.
A lien can be recorded before its amount is known. A provider serves a notice naming no sum; until now the amount was mandatory, so the only options were to invent a figure or leave the lien out of the case entirely. A $0 lien misstates the record and a missing lien hides an encumbrance. The amount is now optional, and nothing prints it as $0: lien tables show it as not stated, and every lien total says how many liens it excludes for want of a figure.
A settlement statement will not understate what a client owes. If a matter has a lien with no amount, the disbursement sheet now names it instead of showing $0, and marks the net to client as provisional — because an unpriced lien cannot yet be deducted from it.
The assistant stops recording a lien it was told nothing about as $0. When a document states no lien amount, or the assistant is not given one, the lien is now stored with no amount rather than zero.

September 7, 2026 v1.0.41 — Windows, Linux & macOS

Contact details entered before encryption was switched on were never encrypted. Turning encryption on protected only what you typed afterwards; anything already in the address book stayed readable on disk, in the columns the rest of CaseDesk treats as protected. Nothing showed it — a readable value reads back exactly like an encrypted one — and changing your password did not repair it. CaseDesk now finds anything left unprotected and encrypts it when it starts, when you switch encryption on, and when you unlock. Contact records sync between your devices, so an unprotected value was also what a sync server received.
Saving practice-area details could report success while discarding them. Each practice area keeps a list of the details it can store, and anything outside that list was thrown away while the save still reported success — there was no way to tell a real save from one that did nothing. On a copyright matter, 32 of its 60 details could not be saved at all, including publication status, the rights asserted and every defence. All of them save now, a save reports how many fields it stored and names any it could not, and the build checks that every detail on every practice area can actually be written.
The assistant was refused by CaseDesk’s own rules. Some tools asked for one thing while the program required another, so a correct request was rejected with an unhelpful message; on one run of 758 records, 128 were turned away at the last step. An expert’s CV was accepted and then discarded. Each tool now asks for exactly what the program accepts, and the build checks that they stay in step.
The assistant can attach an existing contact to a matter, and it is no longer told it cannot enter email addresses, phone numbers or addresses — a restriction that had been lifted long ago but was still written into its instructions.
Contact types are consistent across the app. Some contacts had a type the program could not display, so their type box appeared blank and saving quietly changed it. There is now one list everywhere, and paralegal, court reporter, arbitrator and vendor are selectable.

September 7, 2026 v1.0.40 — Windows, Linux & macOS

CaseDesk stopped inventing deadlines. A start-up check created court-rule deadlines for every case with a filing date and a defendant, and skipped a case only while one of those deadlines still existed — so deleting a wrong one removed the protection and the next start put it back. It now runs at most once per case and remembers that it has run, so a deadline you delete stays deleted.
Case records no longer state things nobody entered. Every new case asserted binding arbitration, and every insurance layer asserted that coverage was confirmed and that the carrier pays defence fees. All three now stay empty until someone records them, and the insurance form offers “Not stated” instead of only yes or no.
Fields that were silently discarded now save. A case’s claim number could not be stored at all, and a discovery date or date of death entered while creating a case was dropped. Every field the case form accepts is now checked automatically to have a real place to save.
A deadline with a time is no longer marked all-day, so hearings and trial calls show their time instead of appearing as an all-day banner.
Contacts reach their matter. A contact created for a case is now linked to it, and counsel can be attached to their contact record.

September 6, 2026 v1.0.39 — Windows, Linux & macOS

CaseDesk no longer deletes document records at startup. A clean-up that ran on every launch removed all but the newest document sharing a filename and folder within a case, regardless of where the file lived. It now runs once per database and only merges records that point at the same file.
Database updates no longer fail on edited data. Update steps 310 to 341 stopped requiring exact deadline-rule totals; a database whose built-in data had been seeded while an earlier update was blocked now updates end to end.
Creating a case or adding a file is one transaction; a rejected request leaves nothing behind. Built-in reference data is seeded once per version instead of every launch.
A second CaseDesk window no longer opens the database and fails; a signature check that failed when launched from PowerShell 7 is fixed; a Gmail sign-in that has expired pauses syncing and says so in Settings; the Documents tab loads large matters faster.
Outlook: connect several mailboxes (for example the firm mailbox beside your own); when an organisation requires administrator approval, CaseDesk shows the exact approval link.
AI Assistant (MCP): new tools to link files where they live, to list, file and dismiss pending emails, paging on long lists, an option to skip duplicates, a lighter tool set for everyday work, and the MCP server now ships inside the installer.

September 6, 2026 v1.0.38 — Windows, Linux & macOS

Database updates no longer stop on an edited reference library. Nine of the update steps between database versions 297 and 311 required exact corpus-wide counts, so a single "Mark verified" on a legal reference, an imported reference, or deadline rules seeded while an earlier update was blocked could stop every later update and leave CaseDesk running on the old schema. Those counts are now logged checks, the deadline-rule freeze is proven by comparing before and after, and the only hard stops left are real data-loss conditions.

September 6, 2026 v1.0.37 — Windows, Linux & macOS

CaseDesk now uses a local AI server that is already running on your computer instead of starting a second one beside it. At startup it looks for an OpenAI-compatible server on the usual local ports (Ollama, LM Studio, vLLM, llama.cpp and others); the first that answers is used for every local AI feature, and Settings → AI shows which one, with a switch back to the bundled model.
The bundled AI model is never loaded onto a graphics card that another program has already filled. CaseDesk now sizes from the card's free memory; an automatic start on a busy card is skipped with a visible notice, and a manual start falls back to the CPU with the reason shown.
New Local Server settings: start on launch, device (auto / GPU / CPU) and GPU layer count.
A database update that stops part-way is now reported at startup, and CaseDesk no longer writes its built-in reference data while an update is blocked, so one failed update can no longer jam the next ones.

September 6, 2026 v1.0.36 — Windows, Linux & macOS

Voice-note recordings now live in your CaseDesk data folder. They were being saved next to the program itself, where the next update would have removed them. Notes you recorded before this build keep working from where they are.
A build-time check now prevents any user data from ever being written next to the program again.

September 6, 2026 v1.0.35 — Windows, Linux & macOS

Every value the AI reads out of a document is now traced back to the document. When CaseDesk’s importer or upload analysis extracts case data — case number, parties, counsel, dates, amounts, bar numbers, phone numbers — it now looks for each value in the document text itself, by code, and matches dates and amounts in every common spelling (“18th day of December, 2019”, “$1,250,000.00”).
A source check before you import. The review step shows how many values were found, which matched only partially, and which are not in the document at all and therefore came from the AI. The AI’s own classifications and written summaries are marked as its own and left unchecked.
The sentence behind every value, kept with the case. The Documents tab gains an “AI extraction sources” panel listing, per source document, each extracted value with the sentence and page it came from — not-found values first. Nothing in it leaves your machine or syncs.
Completes the AI trust work begun in v1.0.34.

September 6, 2026 v1.0.34 — Windows, Linux & macOS

Every citation the AI gives you is now checked, by code, before you see it. Language models invent case names and attach real citations to the wrong cases; asking them not to does not stop it. CaseDesk now extracts every case, reporter citation, statute and court rule from an AI answer and checks each one against its own reference library and, when online checking is on, against two public databases — CourtListener for cases and the California Legislature’s leginfo for California statutes. Each citation carries a visible status: verified, unverified, could not check, not found (presumed fabricated) or name mismatch (a real citation attached to the wrong case name).
Quotations are checked against your own documents. Any quotation of four words or more in an AI answer is compared word-for-word with the extracted text of the case’s documents, and flagged when it is not there.
A flagged draft cannot be applied by accident. In the email assistant, “Apply Draft” waits until you acknowledge any citation that could not be found or any quotation that is not in the documents, and the draft it applies carries the warning tags with it.
Privacy. Online checking sends only the citation text — never your case data — and CaseDesk tells you this once, the first time it is used, with a one-click option to keep checks library-only. A lost connection never counts as verified.

September 5, 2026 v1.0.33 — Windows, Linux & macOS

A full code audit, every finding fixed. We ran an independent review of the whole application and closed everything it found in one release. Nothing here changes how CaseDesk looks or works day to day; it makes the things you rely on hold up under the conditions that break software: an unplugged drive, a lost connection, an odd date, an email attachment with a hostile name.
Your data folder is never silently replaced. If CaseDesk cannot reach the folder you chose for your data at launch — a network drive that has not reconnected yet, an external disk that is unplugged — it now stops and asks, instead of quietly starting with an empty database.
Backups always contain your latest work. The database keeps recent changes in a separate journal file before folding them in; backups now fold that journal in first, so a backup taken a minute after you finish typing includes what you typed. Deleting a case now refuses to go ahead if its safety backup failed.
Cloud sync no longer removes a case’s records when the case is edited on another device. If you sync across two computers, a change to a matter on one of them used to arrive on the other as “replace the case”, which also cleared that case’s notes, deadlines and related records there. Changes now merge into the existing case. Remote changes that cannot be applied are retried and reported rather than dropped.
Deadlines for New York, New Jersey, the Carolinas, the Dakotas, New Hampshire, New Mexico, Rhode Island, West Virginia and the District of Columbia. Cases in two-word states were quietly generating no automatic deadlines at all. They do now. An impossible date can no longer freeze the application, California’s day-after-Thanksgiving court holiday lands on the right Friday in every year, and a New Year’s Day observed on 31 December is recognised.
Paid licences are honoured everywhere. The read-only and expiry screens now recognise a valid licence, and a licence key can be entered on those screens directly.
Practice-area tabs. Edits made just before switching tabs are saved rather than lost; a failed save is shown on screen; typing in the Antitrust, Defamation, Education Law and Privacy tabs no longer drops your cursor after each character; “Today” and “Tomorrow” deadline badges are correct.
Security hardening. Email attachment names and AI-tool file paths are confined to CaseDesk’s own folders; the outdated “Enable File Encryption” option is no longer offered on databases that are already encrypted, and turning field encryption off decrypts everything first; diagnostic logs no longer include document contents or stored values; the local AI engine is shut down cleanly on every exit, including before an update installs.
All three platforms ship the same code. Elevated Windows installs no longer stop with “CaseDesk is already running”.

August 30, 2026 v1.0.32 — Windows & Linux

The built-in AI now suggests a newer, stronger model. CaseDesk matches a local AI model to the graphics card in your machine. That matching had not been revisited since the Qwen 3.8 models were added to the catalogue, so it kept suggesting an older generation even on cards that could run the newer one. It now suggests Qwen 3.8 on every card able to hold it.
Far more working room on mid-range graphics cards. The same choice decides how much text the AI can keep in view at once. On a 20 GB card that went from roughly 2,000 tokens to about 36,800; on a 24 GB card it more than doubled. Cards with memory to spare now switch on the faster drafting mode automatically as well.
A model you have already downloaded and selected yourself is left alone. This changes what CaseDesk recommends, not what it runs.

August 28, 2026 v1.0.31 — Windows

Two graphics cards in one Windows PC are handled properly now. CaseDesk could not read how much memory a graphics card has on Windows, so on a machine with two cards it split the AI model across both instead of keeping it on one. Keeping it on one card is the safer arrangement, and it is what CaseDesk now does whenever the model fits. Machines with a single card are unaffected.
Windows-only release; Linux stays on v1.0.30, which already had this fix.

August 28, 2026 v1.0.30 — Windows & Linux

Local AI now uses Intel Arc graphics cards on Linux. CaseDesk could not recognise Intel’s current Arc cards on Linux — the name Linux reports for them differs from the one Windows reports — so the app concluded there was no graphics card at all and quietly ran local AI on the processor instead. That is many times slower. These cards are now detected and used, and detection no longer depends on the card’s marketing name, so a future model will not silently fall back the same way.
Better use of AMD graphics cards on Linux. CaseDesk now reads how much memory an AMD card actually has, instead of treating it as unknown. It uses that to choose a model sized for your hardware, and on a machine with two cards it keeps the AI on a single card rather than splitting it across both.
Windows and macOS behave exactly as they did in the previous build — both fixes are specific to Linux. This release ships on Windows too, so every platform runs the same code.

August 27, 2026 v1.0.29 — Windows

CaseDesk now starts on a brand-new Windows PC. The app — and its local AI — quietly assumed a Microsoft system component (the Visual C++ runtime) that most computers acquire over time from other software, but a factory-fresh Windows install does not have. On such a machine, previous builds froze silently at launch. The needed files now ship inside CaseDesk itself, in every place they are used, and our release checks were extended so a build missing them can never pass again. If CaseDesk already runs on your machine, you were never affected — but the update is still recommended.
Verified on NVIDIA’s three current GPU generations. This build’s local AI was exercised end to end on Ampere (RTX 30-series) hardware in addition to the Ada and Blackwell cards we already test, confirming every bundled engine — both CUDA generations and Vulkan — detects the card and generates at full speed.
Windows-only release; Linux stays on v1.0.28 (it is unaffected — this was a Windows-specific gap).

August 20, 2026 v1.0.28 — Windows & Linux

A security update to the PDF viewer — worth installing promptly. The component CaseDesk uses to display PDFs had a publicly documented weakness in the version we shipped: a maliciously crafted PDF could, in principle, run code of its author’s choosing when previewed. Attorneys open PDFs from opposing counsel, courts and clients all day, which is exactly the situation that weakness targets, so the viewer has been moved to the current generation of that component. The application framework underneath CaseDesk was brought up to its latest security fixes in the same pass, along with several smaller libraries used for zip and email import.
Evidence timestamping now actually works. The Evidence tab’s Bitcoin anchoring — which stamps a document’s fingerprint into a public timestamp so you can later prove it existed on a given date — failed with a “library not available” error in every installed copy to date. The library it needs was left out of the packaged app by a build misconfiguration; it now ships. Nothing ever fabricated a timestamp: the feature reported its failure honestly, it just could never succeed.
Internal hardening. A security review of the app’s internals tightened what the visible window is allowed to ask the privileged side to do: file deletion is now limited to files CaseDesk manages, storage-cleanup is limited to CaseDesk’s own previous data folder, hidden print windows can no longer navigate anywhere, and every field on case creation is validated. None of this changes how the app behaves day to day — it narrows what a compromise of the display layer could reach.

August 18, 2026 v1.0.27

NVIDIA graphics cards on Linux now use CUDA. Linux ran every graphics card through Vulkan, including NVIDIA ones. NVIDIA cards now use CUDA instead, which is both faster — on the card we test on, prompts are read about a third quicker and answers come out roughly a tenth faster — and, more importantly, the same engine Windows has always used for those cards. That matters beyond speed: the same question, the same model and the same settings can be worded differently by different engines, so a firm running Windows and Linux side by side was getting two slightly different drafting assistants. Now they match. AMD and Intel cards continue to use Vulkan, and nothing needs configuring.
The Linux download is considerably larger. The .deb goes from about 262 MB to about 807 MB, because the NVIDIA engine and its supporting libraries ship inside the package rather than asking you to install anything separately. This is the same trade the Windows build already makes.
The Mac build is signed and notarised by Apple. macOS is still not offered publicly and the site still says planned, but the build now carries Apple’s notarisation, so it opens without the “unidentified developer” warning when it is handed out.

August 16, 2026 v1.0.26

Intel Arc Pro graphics cards are recognised again. CaseDesk identifies your graphics card by name, and the list it checked against did not include Intel's Arc Pro workstation cards — so a machine with one was treated as having no graphics card at all and quietly ran AI on the processor instead, many times slower. The same check was too generous in the other direction: Intel now uses the “Arc” name for the built-in graphics in recent laptops too, and those were being sent down the graphics path even though the processor is the faster choice for them. Both are corrected, and the real card names are now pinned in our tests so this cannot drift again.
Property Tax and Unemployment Insurance matters open their own tab. Both practice areas could be chosen when creating a matter, but neither opened the specialist tab that belongs to it — you got the general tabs and nothing else. The fields existed the whole time; they simply were not connected to those two choices. They are now, and the tab is labelled for the practice you picked.
Three buttons now tell you when they fail. “Restart to update”, and “Lock Database Now” and “Check for Updates” from the menu bar, previously did nothing visible if the action failed. Locking matters most: believing the database is locked when it is not is worse than being told it did not work.

August 16, 2026 v1.0.25

Your graphics card is described correctly in Settings. AMD and Intel cards were shown as having “0GB” of memory, with a blank driver line beside them. The card was working perfectly the whole time — CaseDesk deliberately ignores the memory figure those drivers report, because it is often wrong in a way that would make it load a model too large to run, and it sizes models from your system memory instead. Settings now says that plainly rather than printing a zero, and confirms that AI is still running on the graphics card. Relatedly, when no usable graphics card is found at all, the message no longer says “No NVIDIA GPU detected” — which read as though it did not apply to AMD and Intel owners, who were exactly the people it applied to.
A note about wording. Settings now mentions something that has always been true and was never stated: answers can be phrased slightly differently on different graphics cards. Every answer comes from the same model on your own machine; different hardware rounds its calculations differently, so two computers can word the same answer differently. Neither is wrong, in the same way two lawyers would not draft an identical paragraph — but if you compare a colleague's result to yours and the wording differs, that is why.

August 16, 2026 v1.0.24

Updating an existing installation works again. When v1.0.23 opened a database that already had data in it, one step of the routine upgrade check compared an internal count against a figure that had gone out of date, decided something was wrong and stopped. Nothing was damaged and nothing was lost — the app opened and ran normally — but that step never completed, and because these steps run in order and stop at the first problem, it would also have blocked later updates from applying. This build corrects the figure. If you installed v1.0.23 fresh you were never affected; if you upgraded into it, this build finishes the job on the next launch. The eight California entries that v1.0.23 meant to merge in Legal References are merged now.

August 16, 2026 v1.0.23

Local AI now uses your graphics card on Linux. Until this build the Linux app only ever ran AI on the processor — a couple of tokens a second, slow enough to be unusable, and it stayed that way no matter how good your graphics card was, because the GPU engines simply were not in the Linux package. They are now. AMD, Intel and NVIDIA cards all run through Vulkan; on the AMD card we test on, that is close to ten times the speed of the old CPU-only path. Nothing to configure — the app picks the fastest engine your hardware can actually run and falls back on its own if anything is missing. Intel Arc owners get an extra option in Settings: a one-time download that is about half as fast again as Vulkan on those cards.
A top bar, and a menu with the app in it. The window's menu bar was the stock one — File, Edit, View and nothing of CaseDesk, with no way to reach Settings from it at all. There is now a real menu: new matter, new deadline, search, quick entry, lock the database, Settings, the main pages, theme, keyboard shortcuts and check for updates. The strip across the top of the window also carries quick controls now — switch theme, see at a glance whether local AI is loaded and whether cloud sync is up to date, lock the database, and a "restart to update" button when a new build is ready.
Light mode now reaches the whole window. The navigation rail down the left stayed dark whichever theme you chose, and so did the title bar and menu bar, so choosing light mode left you with a half-dark window. The rail now follows the theme properly, and the window frame follows it with them.

August 15, 2026 v1.0.22

You can add a deadline from the Deadlines page. The dashboard's "Add Deadline" shortcut used to open a page that had no way to add one — deadlines could only be created from inside a matter. There is now a proper entry form (matter, title, date, time, type, priority and notes), reachable from the Deadlines page itself or straight from the dashboard shortcut, which opens it for you. Deadlines you enter by hand are yours: the deadline engine records them as manual and never recalculates them.
California is one jurisdiction again in Legal References. A handful of entries filed under the abbreviation sat in their own group, separate from the rest of the California material, and every jurisdiction chip was shouting in capitals. Both are fixed — the filter now reads California, Texas, Federal and so on, and California covers all 1,243 entries.
The left sidebar no longer looks broken in light mode. The sidebar is dark whichever theme you use, but its dividers and scrollbar were being drawn with light-mode colours, which put pale lines and a grey bar down the dark rail.

August 15, 2026 v1.0.21

Dark mode is readable again in the practice-area tabs. If you work in dark mode, the field labels on the specialised tabs — Administrative, Elder Abuse, Wage & Hour, International Trade and around a hundred others — were rendering in a dark grey on a dark background. Some section headings were being drawn in exactly their background colour, which made them invisible rather than merely faint. Every one of those labels and headings now has a proper dark-mode colour, and the app checks the readability of every piece of on-screen text against its own background before a build can ship.
Light mode is unchanged: the fix only adds colours that apply when dark mode is on.

August 15, 2026 v1.0.20

Search boxes are readable again. In search fields across the app, the magnifying-glass icon was sitting on top of the first character — "Search history…" rendered with its S underneath the icon. One styling rule was quietly overriding the spacing each of those fields had asked for, so every search box in CaseDesk is corrected by the same fix.
The conflict check's "Proceed" button stays reachable on small screens. On a short laptop display, a long results list could push the only button that carries you forward in the new-case flow below the fold, with nothing on screen to suggest it was there.
A blocked "Next" in the new-case wizard now shows you what it wants. When a required field is missing, CaseDesk scrolls to that field instead of leaving the button looking like it did nothing.
Settings section links land where they should. Jumping to a section from the sidebar no longer tucks its heading under the bar at the top of the window.
Denser data tables get back the tighter field spacing they were designed with.

August 15, 2026 v1.0.19

Qwen 3.8 27B joins the local catalog — the latest-generation dense 27B in three sizes (a near-lossless ~29 GB build, ~17 GB for 24 GB cards, ~13 GB for 16 GB cards), each with a 262K-token context and the multi-token-prediction speed-up where video memory allows.
A 512K extended-context option for the largest case files: the same Qwen 3.8 weights extended to 524,288 tokens of context on workstation-class hardware — it shares its download with the standard build.
Updated local AI engine with a fix that matters at long range: without it, certain very long prompts (roughly 90,000 tokens and up) could stop the AI server without any error message. Verified against 100K–300K-token prompts across the catalog's model families before shipping.

August 14, 2026 v1.0.18

Faster local AI on machines with headroom. The two Qwen 3.6 27B models carry a built-in draft head (multi-token prediction) that CaseDesk previously never used. When your graphics card has room for it — or on CPU-only machines, where it costs nothing extra — CaseDesk now switches it on, and generation is substantially faster in our tests; the exact gain depends on content and hardware. Speed never comes at the cost of your working window: on cards where the draft allocation doesn't fit, nothing changes.
If the faster path fails to start on your hardware for any reason, CaseDesk retries without it automatically — local AI keeps working either way.
Linux catches up from v1.0.16 on this same build — including v1.0.17's fix for smaller graphics cards.

August 13, 2026 v1.0.17 — Windows

Local AI now works on smaller graphics cards. On GPUs around 6 GB the assistant previously rejected every message before answering — the request CaseDesk assembled was bigger than the card's working window. Found and fixed testing on a GTX 1060: CaseDesk now sizes what it sends (including its tool list) to the card, so every supported GPU can chat. Verified end-to-end on that 1060.
Linux receives this in its next build; v1.0.16 remains current there.

August 13, 2026 v1.0.16

The app asks you to review the updated Terms and Privacy Policy. The August 12–13 revisions (Cloud Sync in both documents) now reach the app itself — one review on next launch.
Clearer Cloud Sync explanations in Settings — what syncs (everything except device-specific settings; document files stay on your machines for now), and that field-encryption passwords must match across devices.
Disconnecting a computer now also revokes its access on the server, not just locally.
The installer's license screen now states the actual beta license and points at the Terms and Privacy Policy.
First release verified on RTX 50-series 16 GB hardware — the recommended local model for that tier (Gemma 4 26B MoE) answers in about 7 seconds.

August 12, 2026 v1.0.15

Linux catches up. Linux moves from v1.0.11 straight to v1.0.15 — Cloud Sync and everything below included, both platforms on the same build again.
Your edits reach your other computers in seconds. Cloud Sync used to wait for its next half-minute check-in; saving a change now nudges it immediately.
Cloud storage stays tidy on its own. Old sync history that a newer backup already covers is cleaned up automatically; a computer that was away long enough to miss it simply re-syncs from the backup.
Updated Privacy Policy (August 12) and Terms of Use (August 13), and the app will ask again. The policy now describes optional Cloud Sync in detail, and the Terms gain a Cloud Sync section — including the rule that matters most: lose your passphrase, recovery code, and every connected device, and the synced copy is unrecoverable by anyone, us included. CaseDesk shows the updated summary for your review on next launch.
Cloud Sync now connects through sync.casedesk.law.

August 12, 2026 v1.0.14

Cloud Sync (optional). Keep your practice in sync across computers, or don't — CaseDesk stays fully local unless you turn it on. When you do, your data is encrypted on your machine before upload with a key only you hold, protected by a passphrase and a one-time recovery code. The server — and we — can never read it. Contacts, matters, deadlines, document records and details (the document files themselves stay on your machines for now), billing, and trust accounting all sync; conflicting money-record edits are never merged silently — you decide which version wins.
Trust accounting and contact edits now travel with Cloud Sync. The field-level encryption that protects contact details and trust records now uses one key across your devices (same passphrase everywhere), so those records read correctly on every machine you connect.
Changing your encryption password now re-encrypts your existing data. Previously a password change could leave earlier encrypted fields unreadable; that's fixed.
Practice-area dates you confirm onto the calendar sync too. A deadline confirmed from a practice-area tab now reaches your other computers like any deadline you created by hand.
This build is Windows only; Linux remains on v1.0.11 for now.

August 12, 2026 v1.0.13

The AI assistant answers in seconds instead of over a minute. Every message used to re-read the whole case file before it could start; now it re-reads only what actually changed. On a machine with no graphics card that took a question from about 70 seconds down to about 5, and on a machine with one, under a second.
Local AI now uses your graphics card, whatever card you have. The engines for current NVIDIA cards (including the RTX 50 series), older NVIDIA cards, and AMD or Intel cards all ship inside the installer — CaseDesk picks the right one for your machine, and falls back on its own if anything goes wrong. On a tested machine this was roughly 20 times faster than running on the processor alone.
Local AI now starts on machines with two graphics cards. It previously failed to start at all on those machines, and said nothing about why. It now starts, and when something does go wrong it tells you what happened.
CaseDesk suggests a model that suits your machine. It reads your memory and graphics card rather than assuming the smallest option, so a well-equipped machine is no longer handed the weakest assistant.
A saved prompt library, and your own reference material. Keep the prompts you rely on, and give the assistant your preferred templates or authorities to follow. It can also rewrite a rough question into a more precise one before you send it.
CaseDesk Pro. Subscriptions, receipts, and licensing are live, with the cancellation and renewal disclosures California law requires.
This build is Windows only; Linux remains on v1.0.11 for now.

August 11, 2026 v1.0.11

A clearer warning where AI is actually used. The reminder that AI output can be wrong, incomplete, or fabricated — and needs your review before professional use — now sits in the AI panel itself, not only in the terms you accept at first run.
Updated Terms and Privacy Policy. Both were revised on August 11 to describe exactly what the app does — including the update check, what email and calendar access actually covers, and how Bitcoin evidence anchoring publishes a document fingerprint permanently. CaseDesk will ask you to review and accept the updated terms the next time you open it.
Ownership details corrected throughout: CaseDesk is published by Fulks, Inc.

August 11, 2026 v1.0.10

Every file in the Windows package is now digitally signed — not just the executables, but all 81 bundled libraries as well. Nothing CaseDesk ships on Windows is unsigned, and the build refuses to produce a download if anything is.

August 10, 2026 v1.0.9

Everything in the Windows package is now digitally signed. Previously only the installer carried the Fulks, Inc. signature — the application itself, the uninstaller, and the bundled AI engine did not, so uninstalling raised an “Unknown publisher” warning. Every executable we ship is now signed and verified before release.
Signing is enforced by the build itself: a release that would ship any unsigned executable fails and never produces a download.

August 10, 2026 v1.0.8

Windows catches up. This is the first Windows build since v1.0.3 — it carries everything from the Linux releases below: startup failures exit cleanly with a clear message (no more lingering background processes), a helpful dialog when the system credential store is unreachable, case-brief exports that follow a custom data folder, working local AI on CPU-only machines, and AI errors that show up in the chat instead of an endless “Thinking…”.
Updated local-AI engine on the CPU path. The bundled CPU inference engine now matches the GPU engine's version on both platforms.
Crash-proof AI engine restarts. If CaseDesk is force-killed or loses power, the local AI engine it left behind is now detected and replaced on the next launch instead of being silently reused with stale settings.
Windows and Linux now ship the same code at the same version. (v1.0.7 was superseded the same day by v1.0.8, which completes the crash-recovery work — the replaced AI engine now comes back in a single launch.)

August 10, 2026 v1.0.6 — local AI on Linux

Local AI now ships in the Linux build. The same on-device inference engine as Windows (CPU mode — NVIDIA GPU acceleration on Linux comes in a later build). Download a model in-app and everything runs on your machine; nothing is sent anywhere.
CPU-only machines can actually chat now (all platforms). On machines without a GPU, the AI context window was capped so low that the assistant's own case context couldn't fit — every message failed before reaching the model. Context is now sized from your system RAM. This fix reaches Windows with the next Windows build.
AI errors surface instead of spinning. If an AI request fails, the chat now says so instead of showing “Thinking…” forever.
v1.0.5 was a short-lived interim Linux build superseded the same day by this one.

August 10, 2026 v1.0.4 — Linux beta debut

CaseDesk now runs on Linux. Two packages: a .deb for Ubuntu and Debian (recommended — it installs the security profile the Chromium sandbox needs on Ubuntu 24.04+) and an AppImage for other distributions. Same local-first app, same encrypted database — the encryption key lives in your system keyring (GNOME Keyring / any Secret Service provider).
What's verified: full case management, the deadline engine, conflict checks, document templates, and encryption at rest were all exercised end-to-end on Ubuntu 24.04 before this release.
What's not there yet: local AI models aren't bundled on Linux in this build — that arrives in a later release. Bring-your-own-key cloud AI works today. If you use automatic login, note that Linux leaves the login keyring locked until you sign in with a password — CaseDesk now explains this instead of failing silently.
Also in this build (reaches Windows with the next Windows release): startup failures exit cleanly with a clear message instead of lingering in the background, and case-brief exports now follow a custom data directory instead of always writing to the default location.

August 10, 2026 v1.0.3

Conflict check in New Case works as designed again. The names you add in the wizard now carry into the conflict-check window and the search runs automatically — previously the window could open empty, inviting you to skip a step you shouldn't skip.
Cloud-sync refresh fixed. Reloading the database to pick up changes from a synced folder failed quietly on every launch after the first; it now works every time.
Future updates install silently. From this build on, clicking “Restart now” on an update installs it in the background and relaunches — no installer wizard to click through.
Accurate encryption messages. Backups and synced files were warning “contains unencrypted data” even though your database file is encrypted at rest on every current install. The warning now appears only when it’s actually true.

August 9, 2026 v1.0.2

The judge directory now arrives on a brand-new install. A data gap meant fresh installs shipped with the judge-profiles directory empty — two federal courts (S.D.N.Y. and E.D. Tex.) referenced by the directory were missing, which silently blocked the whole set from loading. Both courts are now included, and installs that hit the gap heal themselves on their next launch.
Unattended uninstalls no longer stall. A silent (scripted) uninstall used to wait forever on an invisible confirmation dialog. It now completes on its own — and keeps your data unless you explicitly say otherwise.

August 7, 2026 v1.0.1

CaseDesk updates itself now. The app quietly checks for new builds and offers them in a small in-app card — download with a live progress bar, then restart when you choose. Nothing downloads or restarts without your click, and a download you defer simply installs on your next quit.
Real version numbers. This build is v1.0.1, and the splash screen, About dialog, sidebar, and installer filename all say so — builds are no longer identified by hash alone.
Smoother first run on a brand-new machine. Antivirus first-touch scanning can no longer be misread as “no GPU” during local-AI hardware detection, and the first load of a large local model gets the time it actually needs instead of giving up early.
No more frozen buttons during big file work. Backups, data-folder moves, and cloud-sync copies now run off the interface thread — the app stays responsive even while gigabytes move.
The download page now explains the Windows SmartScreen prompt a brand-new build can show, and exactly which buttons to click.

July 22, 2026 Sentinel

Sentinel goes live. Email-SLA tracking now has three modes — Off, Reminders, and Escalation. Reminders is the default and only surfaces what's gone unanswered; Escalation actively fires tiered follow-ups. Sentinel recognizes opposing counsel, clients, adjusters, and co-counsel and measures against a business-hours clock.
Your free window now starts at first run, not at the build date — so a build that sat on your drive for a month doesn't cost you a month.
"Report this issue" on the error screen, with a full review step: you see exactly what would be sent before anything leaves your machine, and nothing sends without your click.
First-run beta terms acceptance gate, plus an in-app feedback link.
Fixed: two crashes in the Analytics tab when a matter had partial or empty financial data.
A2P 10DLC registration notice in SMS settings, so Twilio setup doesn't surprise you.

July 19, 2026 Sentinel, shadow mode

The "Awaiting Your Reply" dashboard panel arrived in a watch-only mode — ranking unanswered mail by urgency without taking any action, so the behavior could be checked against real inboxes before anything was allowed to fire.

July 2026 deadline engine

Insurance deadlines — first-party suit-limitation and proof-of-loss periods across the states, including the states where a policy may lawfully shorten the window (flagged, with a warning to check the policy).
Property-tax appeal deadlines, including the fixed-annual-date and nth-weekday rules that don't count from a trigger date at all.
Foreclosure redemption periods, scoped to judicial-foreclosure states.
Unemployment matters now reach the agency deadline set from the case picker.
The corpus is at 4,734 jurisdiction-specific rules as of this build.

Earlier in 2026 coverage

Probate coverage completed across all 50 states and DC.
Family law became its own area, with its own deadline set rather than inheriting civil defaults.
Bankruptcy deadlines gained chapter scoping, so a Chapter 7 matter stops showing Chapter 13 dates.
Unlawful detainer rebuilt and re-verified against official sources.

How updates reach you

There's no auto-update during the beta — you install a new build when you choose to, from the download link. Your data is untouched by an install; it lives in its own encrypted database outside the application folder. If you want an email when a build ships, the signup on the download card is the list.