Autonix — Spec Compliance Guard
Real-time spec compliance checking, Scrum task autopilot, and AI-assisted fixes — all inside VS Code and Cursor. Like ESLint, but for your architecture and business logic. What it doesAI coding tools (Cursor, Copilot, Claude, Codex) generate code that looks right but silently drifts from your specs. Tests pass, the PR merges, and six weeks later you realize the auth flow doesn't match the ERD and the API returns a 200 where the spec says 201. Autonix fixes that. It validates your code against your specs on every save, shows violations inline as you type, and one-click injects spec context into Cursor Composer or VS Code Chat so the AI can fix it correctly. Features🔍 Real-time spec validation on saveSave any file → within ~1 second, Autonix shows inline squiggles and Problems panel entries for every place your code deviates from the spec. Each violation includes:
Rate-limited client-side (30 req/min, 5-minute content cache) so it scales to monorepos without hammering the API. ⚡ Fix with AI (
|
| Setting | Default | Description |
|---|---|---|
autonix.serverUrl |
https://mcp.autonix.dev |
MCP Gateway URL |
autonix.apiKey |
"" |
API key (starts with anx_). Prefer .autonix/config.json or AUTONIX_TOKEN env var |
autonix.projectId |
"" |
Project UUID. Auto-detected from .autonix/config.json or .cursorrules |
autonix.validateOnSave |
true |
Run validation on every save |
autonix.validateOnOpen |
false |
Run validation when a file is opened |
autonix.debounceMs |
1000 |
Debounce delay after save before validation |
autonix.maxFileSize |
100000 |
Skip files larger than this (bytes) |
autonix.excludePatterns |
[...] |
Glob patterns to skip (node_modules, dist, etc.) |
autonix.severity.violation |
warning |
Diagnostic severity for violations |
autonix.severity.suggestion |
information |
Diagnostic severity for suggestions |
autonix.cli.path |
"" |
Path to local autonix-cli/bin/cli.mjs for contributors running from source |
Commands
| Command | Description |
|---|---|
Autonix: Setup / Connect |
Run the setup wizard |
Autonix: Validate Current File |
Force-validate the active editor |
Autonix: Validate All Open Files |
Workspace-wide scan |
Autonix: Start Task |
Begin a Scrum task (opens files + injects prompt) |
Autonix: Complete Task |
Validate acceptance criteria and mark done |
Autonix: Check Acceptance Criteria |
Run criteria check without marking done |
Autonix: Clear All Diagnostics |
Remove all Autonix squiggles |
Autonix: Show Output |
Open the Autonix output channel |
How it works
┌─────────────────────────────────────────────────────────────┐
│ VS Code / Cursor │
│ │
│ onDidSaveTextDocument │
│ │ │
│ ▼ │
│ Debounce (1s) → Exclude check → Size check │
│ │ │
│ ▼ │
│ SHA-256 content hash → Cache lookup (5min TTL) │
│ │ (miss) │
│ ▼ │
│ Token bucket rate limiter (30/min) │
│ │ │
│ ▼ │
│ POST mcp-gateway /api/v1/validate │
│ │ │
│ ▼ │
│ Parse violations → Diagnostics → Problems panel │
│ │
└─────────────────────────────────────────────────────────────┘
Violations render as squiggly underlines. Hover shows the spec excerpt. Cmd+. offers Quick Fixes.
Development
git clone https://github.com/autonix/autonix-vscode
cd autonix-vscode
npm install
npm run build # → dist/extension.js (single bundle via esbuild)
npm run watch # incremental builds
npm test # vitest
npm run package # vsce package → .vsix
Open the folder in VS Code and press F5 to launch an Extension Development Host with a test workspace.
Running against a local MCP Gateway
If you're running mcp-gateway locally on :8010, point the extension at it via VS Code settings:
{
"autonix.serverUrl": "http://localhost:8010"
}
License
MIT — see LICENSE.
Links
- Website: autonix.dev
- Dashboard: autonix.dev/app
- API keys: autonix.dev/app/settings/api-keys
- Issues: github.com/autonix/autonix-vscode/issues