For lawyers and contract teams reviewing Word redlines

Ask Claude what changed. Get your counterproposal back in Word.

Compare the drafts, check the exact wording Claude found, and prepare a separate Word document with the edits shown in Word’s Track Changes. Your original files stay unchanged.

Runs on your computerOpen sourceEarly public version

Veqtor's document tools run on your computer. Text they return becomes part of your Claude conversation. See what information may leave your computer.

What happens after you ask
You ask Claude

“What changed across these drafts? Prepare our counterproposal in Word.”

Claude works through your request
You get a separate Word document

Veqtor checks whether it can make each requested document change exactly.

The quote is checked against a specific changeAll requested changes are tested togetherIf a document change is unclear, Veqtor stops
Counterproposal · Word documentOriginal unchanged

The familiar problem

A chat answer is not a revised Word document.

When contract text is copied into chat, it is separated from the Word file and the tracked changes around it. You still have to compare drafts, confirm quotes, and put proposed wording back into Word yourself.

01

Several drafts still need comparing

02

Quoted wording still needs checking

03

Suggestions still need putting back into Word

Ask → get

Ask Claude as you normally would.

Each question leads to a result you can check against the Word documents or review as a separate file.

01
“What changed in the liability clause across these drafts?”
A draft-by-draft explanation based on the tracked changes Veqtor can read.list_rounds · extract_redlines · deterministic filename order
02
“Does this quote match the change in the counterparty’s draft?”
A clear answer about that specific change, including any differences.verify_quote · anchor required · exact / normalized / not_found
03
“Prepare our counterproposal in Word with tracked changes.”
A separate Word document for review. Your original stays unchanged.preflight_edits · complete atomic batch → apply_edits · new output only
04
“Show me what Veqtor checked and changed.”
A short summary in Claude of the work Veqtor recorded on your computer.export_decision_record · compact JSON · best-effort local provenance

Watch the workflow

From four Word drafts to a counterproposal you can review.

1:44 · Veqtor v0.1.2 · Sample documents · No client data

Claude compares the drafts, checks a quote, and creates a separate Word document with tracked changes.

Recorded with Veqtor v0.1.2 · Real Claude prompts · Sample documentsCompare drafts → check wording → create the next Word document · Read transcript

The “one command” line in the narration refers to Claude Code. Claude Desktop currently needs a short configuration edit. One correction: Veqtor 0.1.2 checks the new Word document before saving it; it does not reopen the saved copy for a separate final check.

How to use it

Set it up once. Then work in Claude as usual.

After setup, keep your Word drafts together and ask Claude questions in your own words.

STEP / 01

Connect Veqtor

Choose the Claude app you use and follow its step-by-step setup guide.

Claude Code on macOS/Linux: one registration command after installing uv. Claude Desktop on macOS: a short configuration edit and restart.
STEP / 02

Put the Word drafts in one folder

Add 01, 02, 03 to the beginning of the file names to show their order, then tell Claude where the folder is.

Deterministic filename order · not reconstructed chronology
STEP / 03

Ask Claude normally

Ask what changed, check wording, or request a counterproposal. Review Claude’s answer and the new Word document before using them.

Safety and limits

Veqtor refuses document changes it cannot make exactly.

Early public version · Mac and Linux · Community support only

Your original stays unchangedEvery successful edit creates a separate Word document. Veqtor will not replace your original or an existing file with the same name.

All requested changes are checked togetherIf even one requested change cannot be completed, Veqtor does not create the final Word document.

Veqtor refuses changes it cannot make exactlyIt stops rather than risk changing the wrong text.

Veqtor can keep an activity historyThe history is a helpful record on your computer, but it is an ordinary file—not independent proof that nobody changed it.

Claude's answer still needs your reviewVeqtor checks supported document operations, not the legal judgment or every statement Claude makes.

What information may leave your computer?

Veqtor does not send whole Word documents anywhere on its own. Text that Veqtor gives Claude becomes part of your Claude conversation and may be processed by the AI service you use. Veqtor also normally tries to save an activity history on your computer. It may include contract wording, so keep it confidential.

For readers who want the technical explanation

How Veqtor works with Claude.

You ask Claude in normal language. When Claude needs to read, check, or make a supported change in Word, it asks Veqtor to do that document work on your computer.

In precise terms, Veqtor is a local, open-source MCP server. MCP is the standard connection Claude uses to call Veqtor’s document tools.

You ask Claudenormal language
Claude asks VeqtorMCP connection
Veqtor checks Wordread · check · test
Veqtor creates a new filetracked changes · original unchanged

Local stdio MCP · list_rounds · extract_redlines · verify_quote · preflight_edits · apply_edits · export_decision_record

Contract guidance

Practical guides to common contract clauses.

The guides explain the clause. Veqtor helps you work with the actual changes in Word.

115 guides across 17 topics

Start with sample documents

Ready to connect Veqtor to Claude?

Start with the setup guide and sample documents before using a real matter.