Patent Office Actions
Patent Practitioner Tools

Download Patent Practitioner Tools

See each item an Office Action states and prepare the reply one item at a time, on your own computer. The same download drafts continuation claims.

New in 0.14.0: the app reports how it is used, anonymously and never with your papers or your clients' (what is sent, and how to turn it off), and a citation of a reference's drawings such as "FIGS. 5 and 6A-6C" is read for every figure it names. For Office Action responses, since 0.11.0: Import from Patent Center, the file history from the USPTO with your own Portal key, the claims against the examiner's citations before the response, and the action's dates, each an estimate beside the docket warning.

  1. Download

    Download for Linux

    continuation-drafter-linux-amd64: Linux on x86-64; the arm64 build is under the command-line binaries below. Free to download and use, with no account and nothing to activate. Installing it takes under a minute.

  2. Open the app

    On Linux: mark it executable with chmod +x continuation-drafter-linux-amd64 and run it from a terminal with serve; on arm64, take that build from the command-line binaries below.

    The interface opens in your browser, on this computer. There is no Dock icon or window of its own: the browser tab is the whole interface, and Stop there quits it.

    On a Mac

    On a Mac: double-click the downloaded .dmg, drag Patent Practitioner Tools to your Applications folder, and double-click it there. macOS asks once whether you are sure you want to open something downloaded from the internet; the button is Open. No Terminal, no permissions to change.

    On Windows

    On Windows: the file downloads as continuation-drafter-windows-amd64.exe and needs nothing done to it. Double-click it to get a console window, or run it from a terminal where you saved it. There is no permission to change and no flag to clear. Windows shows Geeks in the Woods as its verified publisher; a new release may still be called not commonly downloaded, with Delete preselected, and the publisher line is what to check before choosing Keep.

  3. Try the sample

    On the app's opening page, under Draft a response to an Office Action, press Try the sample. It opens the public non-final rejection of application 18/541,216 (US 12,299,058) with the claims it examined and the specification, already read: The action and Address the Rejections and Objections open with no model, and a model is needed only once you ask for a draft.

    The sample, step by step, with pictures of each.

  4. Set up drafting

    Reading what an Office Action states, and drafting, use a model. Choose where it runs:

    • A model on this computer. The text of the papers is not transmitted anywhere; on 16 GB, gemma4:12b, whose memory use stays at about 12 GB while it drafts. A local model is a download of several gigabytes, once, which is under an hour on a fast connection.
    • Your own provider key at OpenRouter, OpenAI or Anthropic. A provider key needs no download, and the text of the papers the model reads reaches that provider.

    Choosing a model or pasting a key takes a few minutes. For the sample neither choice exposes anything of yours, so take whichever is quicker.

  5. Your own papers

    Press Start a reply and add the Office Action, the current claims and the specification under Papers, as a PDF, a Word file or text. They stay on this computer, with the matter.

    Most papers in a Patent Center file history are scanned images, so reading them needs an OCR engine, tesseract, on the same computer. On a Mac: brew install tesseract. On Linux: your package manager's tesseract-ocr. On Windows: the Tesseract installer, into its default folder. Without it, a paper with no text layer is listed and left unread, and the app says so.

    What happens to a file history you open

Need help getting started? Write to hello@obviouslynot.ai; it goes to a person.

Read a public record first

Before you open a client's file in it, read a granted application's public record: US 12,299,058, application 18/541,216.

  1. Download its Patent Center file history (a 13 MB PDF, exactly as Patent Center serves it), its specification and its allowed claims.
  2. Press Start a reply. Under Papers, add the PDF under Earlier papers, or the complete file history and the specification under The specification. It picks out the Office Actions, the responses and the allowance and reads them on your computer; the scanned pages take a few minutes.
  3. Open The action: whether it is final, its estimated response date beside the warning to check it against your docket, which is the system of record, and each rejection, objection and requirement with its claims, ground and references in the examiner's words, every quotation checked against the paper.
  4. Open Address the Rejections and Objections, choose a response approach for an item under Choose an approach, and add its drafted units to your reply with Add to draft.
  5. Open The reply, read it as a Document, add a note under Notes on this reply, and download it with Reply in Word. The note stays with the matter and out of the export.

A quotation it could not find word for word in the paper is marked rather than dropped, so how often that happens on a record you know shows how far to trust its reading of one you do not.

Before you install

What does it cost?

It is free to download and use, with no account and nothing to activate. With a local model there is no cost per use; with a provider key you pay that provider directly, with no markup from us. More on cost.

What setup does it need?

To open it, none. To read scanned pages, an OCR engine (tesseract) on the same computer. To read what an Office Action states, and to draft, a model: one on your computer, through Ollama or another server that speaks the OpenAI API, such as LM Studio or llama.cpp; or your own key at OpenRouter, OpenAI or Anthropic. Try the sample opens with no model, because its Office Action is already read; a model is needed once you ask for a draft. More on setup.

What stays on my computer?

With a model running on your own computer, your application documents, the text read from them, and your drafts are processed on that computer and are not sent to us or to an AI provider. A model your Ollama server would send on to another machine, such as an Ollama cloud model, is refused. Other network activity, such as an update check you ask for, is listed on /security. More on where the papers go.

What reaches a provider if I use my own key?

The text of the papers the model reads and, for a draft, what that draft is built from, sent to the provider you chose, under your key. More on what a provider receives.

Can I try it without client documents?

Yes. Try the sample opens a sample matter for either task: the public Office Action of application 18/541,216 for a reply, or a short published-style application for continuation claims. The public papers of 18/541,216 (its Patent Center file history, specification and allowed claims) can also be downloaded from /download and added yourself. More on the sample.

Does it work with Word?

Yes, both ways. Every paper can be added as a Word file, as well as a PDF or text, and struck-through text in one is read as deleted. Claims save as Text, Word or PDF wherever they are shown, and a reply downloads as Word, from Reply in Word or Report of the action in Word; notes on claims or a reply are never written into a download. More on the Word file.

Need help getting started? Write to hello@obviouslynot.ai; it goes to a person.

What is checked, and how you can check it

Every claim here is one you can confirm yourself. None of it asks you to take our word.

Reviewing it for a firm? The IT and security page lists every network connection it makes, where it keeps its files and how each download is signed.

A file history is read on your machine

Sorting the papers, reading scanned pages and building the timeline happen on your own computer with no network call. Asking what the examiner said, and a draft of the reply when you ask for one, use a model; choose a remote one and the interface names the company that will receive the text, as soon as you select it.

Its publisher is named on both systems

On Windows the verified publisher is Geeks in the Woods; right-click the file, then Properties, then Digital Signatures, to see it. On a Mac the app carries a Developer ID signature and is notarized by Apple, which scans every build.

Each file's fingerprint and contents are published

The release's checksums.txt carries a SHA-256 for each download, which is how you confirm the file you have is the one that was built; a signature alone does not show that.

Since v0.2.4 every binary comes with a bill of materials naming each library in it and its version, down to the Go runtime, so anyone can tell whether a build contains a library a later advisory names, without rebuilding it.

Since v0.4.0 the checksums file is signed, and updating relies on that: after you press Check for updates in Settings, a newer version installs only once its signature, its checksum and, on a Mac, Apple's signature verify. It checks only when you ask, or when the app opens if you turn that on.

A known vulnerability blocks a release

Every release is checked, code and libraries, against published security advisories before it goes out, and one that this code can reach fails the release instead of shipping.

The app is for registered patent attorneys and agents. It reports what each paper says and does not judge it.

For a terminal, and when something goes wrong

Command-line binaries

The same program without the wrapper. File histories are read in the browser interface it serves; the command line drafts and scores continuation claims.

On a Mac, take the double-clickable app rather than a raw binary: continuation-drafter-macos.dmg. The two bare macOS builds below are for a terminal, a script or CI.

chmod +x continuation-drafter-darwin-arm64 && \
  mv continuation-drafter-darwin-arm64 continuation-drafter

It makes the file executable and shortens its name. Run it with serve to open the interface: ./continuation-drafter serve. Reading a file history happens only there.

Which Mac is yours: Apple menu, then About This Mac. An Apple M1, M2, M3 or later chip is Apple silicon; a chip named Intel is Intel.

Checksums and signatures

The app and the raw binaries are signed with a Developer ID certificate and notarized by Apple, so neither needs anything done to it after download. Notarization says Apple scanned the developer's build, not that the file you hold is that build. Its SHA-256, published with the release, is what shows that.

The Windows binary is signed with a certificate issued to Geeks in the Woods, the name Windows shows as its verified publisher. A new release can still be called not commonly downloaded, a score that rises as each build is downloaded; trust the publisher line, and the SHA-256 to confirm the file.

Release notes and checksums

Troubleshooting

Windows offers to delete it. Windows tends to call a new release not commonly downloaded and preselect Delete, which is about how new the file is rather than whether it is signed. If the dialog's Publisher line reads Geeks in the Woods, choose Keep.

A scanned paper reads as empty. Its pages are images, so it needs tesseract on the same computer, or a PDF you have already run text recognition on; the app says which is missing rather than reporting an empty file.

The app has another name in Applications. Before version 0.6.2, Patent Practitioner Tools was called Continuation Drafter, and a copy you updated from inside the app keeps that name.

One question, if you have a minute

We do not know how many practitioners will read a file history with a model on their own hardware rather than their own provider key, and that sits underneath most of how this is built. If you downloaded it, telling us which you chose, or that you chose neither and why, is genuinely useful.

hello@obviouslynot.ai. It goes to a person. There is no list to join and nothing follows.