Open-source legal operations

Ship agreements faster, without black-box legal tooling.

Q: Does OpenAgreements send agreement data to remote servers?

OpenAgreements is local-first and template fill runs on your machine; you control any external services you connect.

Q: Can I use OpenAgreements with Claude Code?

Yes. You can use the CLI directly, the Agent Skill, and the contracts workspace MCP package.

Q: How is template licensing handled?

Licensing is enforced through metadata and validation. Non-derivative templates are preserved unchanged, and non-redistributable templates are recipe-driven.

Q: How do I deploy this landing page to Vercel?

Import the repository into Vercel and deploy the root project. The included vercel.json serves the static site directory.

Q: Does OpenAgreements replace legal counsel?

No. It automates document workflows; teams should still involve qualified legal counsel for legal advice.

OpenAgreements fills standard legal templates from local data, keeps every step auditable, and works with the coding-agent workflows teams already use.

Start with CLI Use as Agent Skill

Start paths

Pick the integration path that fits your team now. You can run only the pieces you need: template filling, contracts workspace tooling, or both.

CLI

Fastest way to run template fill and validation locally.

npx -y open-agreements@latest list --json

Claude + skills

Use OpenAgreements from Claude Code with guided interviews.

npx skills add open-agreements/open-agreements

Workspace MCP

Organize contracts by lifecycle with local-first tooling.

npx -y @open-agreements/contracts-workspace-mcp

Live workflow preview

From prompt to signed-ready NDA output in one agent-driven run.

OpenAgreements Mutual NDA fill demo — Demo clip: Common Paper Mutual NDA filled through Claude Code + OpenAgreements.

Q&A

Quick answers for legal ops teams evaluating OpenAgreements.

What is OpenAgreements?

OpenAgreements is an open-source CLI and library for filling standard legal agreement templates (DOCX) with structured inputs. It is designed to work directly with coding agents and local workflows.

Does OpenAgreements send agreement data to remote servers?

The core tooling is local-first. Template fill runs on your machine and outputs local files. You control any external services you choose to connect.

What templates are supported today?

The project includes internal templates (for example Common Paper and Bonterms), external vendored templates (for example YC SAFEs), and recipe-driven templates downloaded from official sources at runtime.

Can I use OpenAgreements with Claude Code or other agent workflows?

Yes. You can use the CLI directly, install the Agent Skill, and connect the workspace MCP package for lifecycle-focused contract organization workflows.

How is template licensing handled?

Licensing is enforced by template metadata and validation rules. Non-derivative sources are kept unchanged, and non-redistributable sources are handled through recipe instructions and runtime download.

What is the contracts workspace package?

It is a separate package for organizing contract directories by lifecycle, generating status indexes, and validating folder/file conventions without requiring template fill adoption.

How do I deploy this landing page to Vercel?

Import this GitHub repository into Vercel and deploy the root project. The included vercel.json serves the static site/ directory as the deployed output.

Does OpenAgreements replace legal counsel?

No. OpenAgreements automates document assembly and workflow structure. Teams should still involve qualified legal counsel for legal advice, negotiation strategy, and jurisdiction-specific interpretation.

Built for legal teams that need control.

OpenAgreements is local-first, test-covered, and source-visible. No hidden prompt chains, no opaque hosted logic.

Open GitHub View npm package