You can.
Evidype is the installable VS Code agent. EvidyTS is the compiler/dialect it targets. Evidype
can replace a general-purpose AI coding sidebar for TypeScript projects when you want stricter structure,
specs, tests, and compiler feedback in the loop.
Tools like Cursor, Claude Code, and Copilot are useful because they optimize for generation: produce code quickly, edit files, answer prompts, and make the demo work. Evidype does that inside VS Code, then keeps feeding the result through stricter EvidyTS rules.
EvidyTS focuses on the shape of the resulting codebase.
The question is not who writes the code
The important question is what condition the project is in after generation, review, correction, and repeated change.
EvidyTS asks:
- Did the code stay decomposed?
- Does each file have one primary concept?
- Does the filename match the exported symbol?
- Does behavior have a stated spec?
- Are tests mechanically discoverable?
- Is behavioral verification possible?
- Is coverage debt visible?
- Did the project become easier or harder to extend after repeated changes?
Generation still needs pressure
AI coding assistants are good at moving fast. That speed is valuable, but it can also hide decay until the codebase has already become harder to change.
EvidyTS adds structural pressure while the project is being generated and changed. It keeps
naming, file layout, specs, and test discovery visible enough that the assistant has a more constrained
target and the reviewer has a more inspectable result.
Use the packaged agent, or bring your own assistant
The simplest path is to install Evidype for VS Code, choose OpenAI or OpenRouter, and describe the project or change you want in normal language.
If you already have a preferred assistant, you can still use EvidyTS as the compile target
and quality gate for generated TypeScript code.
The VS Code extension is the packaged workflow. It can code against the stricter rules and run the compiler natively inside the workflow. You can download it from the download page.