AI-WorkDeck/aiworkdeck

AI WorkDeck brings that infrastructure to lawyers — organised by matter, every answer sourced, every change on the record.
 
 
Free community edition · Windows / macOS · English · 简体中文
▶ Click the screenshot to watch the 2-minute film. Real interface; the matter is fictional.
## Why an IDE
The AI chat box is the command line of the AI era. A big matter means hundreds of documents, months of work and several people. Lawyers, like programmers, work in text — piles of files, draft after draft, citations to check everywhere. They deserve their own infrastructure too.
| Chat box | AI WorkDeck |
| Start from scratch every time | The context lives with the matter |
| Paste the materials in, one by one | The AI reads the case file and edits the documents |
| Copy the answers back out, piece by piece | Every step leaves a record |
Just a quick question? Switch to chat mode. For the longer argument, read our thesis →
## What it does
AI edits the document itself. It writes straight into the real Word file as tracked changes, and you accept or reject each one.
Every conclusion has a source. Click a citation to land on the supporting passage; changed or missing anchors are flagged.
The field and the office, connected. Photos and recordings taken on your phone land in the matter on your computer, filed by date.
Extended by the community. Install Skills, plugins and MCP servers in one click — or publish your own; authors keep 85% of net receipts on paid listings.
Screenshots use fictional demo matters. The interface is shown in Chinese; it ships in 20 interface languages.
## Video tutorials
Two minutes, one task — 19 short episodes on the website. Tutorials are in Chinese for now.
Why a workspace?
Linking evidence into the complaint
Hiding party details before the AI edits
Who on the team is busy?
## Try it
Use it: macOS / Windows releases · try it in the browser · website.
Run from source: Getting started · Architecture. The contributor stack uses JDK 21, Maven, Node/npm and PostgreSQL; optional sidecars have additional requirements.
Know the data paths: desktop editing uses local storage by default; cloud models, platform services, hosted add-ins and sync have different data paths. Self-hosting requires configuration and deployment-specific verification. See Privacy and service data flows.
## Build with us
The repository contains the desktop app, workbench, agent backend, document-editor integration and plugin runtime. The foundations map to code you can read:
| Foundation | Where to look |
| Document-native agent edits, tracked changes and checkpoints in the embedded LibreOffice WASM editor | Editor primitives · Editor bridge |
| Source links with anchor-change detection; a pluggable evidence-provider interface | Evidence contract · Provider example |
| Git-backed history, three-way document merge, paragraph-level provenance | Version engine |
| Web panes, Java tools, declarative templates and reusable Skills | Plugin guide · SDK · Skill spec · Examples |
| Built-in workflows and entry points | Skills · Litigation visualization · Desktop · Office/WPS add-in |
Build a plugin. Start with the minimal web plugin (plain HTML and JavaScript, no build step) or the declarative plugin, or let an agent help you through the developer walkthrough. Web plugins run in a sandboxed iframe behind a permission-checked bridge; Java plugins run in the backend process and must be trusted. The developer program initially has no application fee; basic profile review is not identity certification, and each plugin version undergoes separate review and signing. The plugin guide explains the boundaries and the publication process.