One workspace for every AI coding assistant.
`` Delimit
One workspace for every AI coding assistant. Switch models, not context.
Your tasks, memory, and governance carry between Claude Code, Codex, and Gemini CLI. Persistent ledger, API breaking change detection, security audit, multi-model deliberation — all shared across assistants.
GitHub Action
Add to any repo with an OpenAPI spec:
name: API Contract Check
on: pull_request
jobs:
delimit:
runs-on: ubuntu-latest
permissions:
pull-requests: write
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: delimit-ai/delimit-action@v1
with:
spec: api/openapi.yaml
That's it. Delimit auto-fetches the base branch spec, diffs it, and posts a PR comment with:
- Breaking changes with severity badges
- Semver classification (major/minor/patch)
- Step-by-step migration guide
- Policy violations
View on GitHub Marketplace → · See a live demo (23 breaking changes) →
Example PR comment
Breaking Changes Detected
Change Path Severity endpoint_removed DELETE /pets/{petId}error type_changed /pets:GET:200[].id(string → integer)warning enum_value_removed /pets:GET:200[].statuswarning Semver: MAJOR (1.0.0 → 2.0.0)
Migration Guide: 3 steps to update your integration
CLI + MCP Toolkit
Governance tools for AI coding assistants (Claude Code, Codex, Cursor, Gemini CLI):
npx delimit-cli setup
No API keys. No account. Installs in 10 seconds.
CLI commands
npx delimit-cli lint api/openapi.yaml # Check for breaking changes
npx delimit-cli diff old.yaml new.yaml # Compare two specs
npx delimit-cli explain old.yaml new.yaml # Generate migration guide
npx delimit-cli init --preset strict # Initialize policies
npx delimit-cli doctor # Check setup health
What the MCP toolkit adds
When installed into your AI coding assistant, Delimit provides:
- API governance -- lint, diff, policy enforcement, semver classification
- Test verification -- confirms tests actually ran, measures coverage
- Security audit -- scans dependencies, detects secrets and anti-patterns
- Persistent ledger -- tracks tasks across sessions, auto-creates items from governance
- Multi-model consensus -- Grok, Gemini, and Codex debate until they agree
- Zero-spec extraction -- generate OpenAPI specs from FastAPI, Express, or NestJS source
What it catches
10 categories of breaking changes:
| Change | Example |
|---|---|
| Endpoint removed | DELETE /users/{id} disappeared |
| HTTP method removed | PATCH /orders no longer exists |
| Required parameter added | New required header on GET /items |
| Field removed from response | email dropped from user object |
| Type changed | id went from string to integer |
| Enum value removed | status: "pending" no longer valid |
| Response code removed | 200 OK response dropped |
| Parameter removed | sort query param removed |
| Required field added to request | Body now requires tenant_id |
| Format changed | date-time changed to date |
Detection is deterministic — rules, not AI inference. Same input always produces the same result.
Policy presets
npx delimit-cli init --preset strict # All violations are errors
npx delimit-cli init --preset default # Balanced (default)
npx delimit-cli init --preset relaxed # All violations are warnings
Or write custom rules in .delimit/policies.yml:
rules:
- id: freeze_v1
name: Freeze V1 API
change_types: [endpoint_removed, method_removed, field_removed]
severity: error
action: forbid
conditions:
path_pattern: "^/v1/.*"
message: "V1 API is frozen. Changes must be made in V2."
Supported formats
- OpenAPI 3.0 and 3.1
- Swagger 2.0
- YAML and JSON
Links
- delimit.ai -- homepage
- Docs -- full documentation
- GitHub Action -- Marketplace listing
- Quickstart -- try it in 2 minutes
- npm -- CLI package
- [Pricing](htt
Tools (3)
lintCheck an OpenAPI specification for breaking changes.diffCompare two OpenAPI specifications.explainGenerate a migration guide between two OpenAPI specifications.Configuration
{"mcpServers": {"delimit": {"command": "npx", "args": ["-y", "delimit-cli", "mcp"]}}}