Vificil
Code locally with ChatGPT & Claude — no API required
I use browser-based AI tools like ChatGPT and Claude a lot while developing software, but I kept running into the same problem: getting enough project context into the browser and then manually moving all the generated changes back into my local codebase.
So I built Vificil.
Vificil prepares a cleaned Full Source Context of a local project that you can give to the AI. The AI generates a structured patch ZIP, and after you download it Vificil automatically detects, validates, and applies the changes back to the correct project.
It can also run verification commands, keep backups, and roll back changes when verification fails.
The main idea is that Vificil is AI-independent. It doesn't require an API key, a specific AI provider, a new IDE, or local-model hardware. You can keep using your existing IDE and browser AI workflow.
This can also reduce costs for developers who already have access to AI through consumer subscriptions and don't want every coding task routed through separately billed APIs.
Tutorial: https://www.youtube.com/watch?v=yRLzD6Z7HBg
Vificil Basic is free with no usage quotas.
For the launch, I'm also giving Vificil Pro free to the first 100 users through a Microsoft Store promotional link:
http://go.microsoft.com/fwlink/?LinkId=532540&mstoken=WFRJ3-QTJH6-KXJCV-4WXG9-HDM3Z
Vificil originally started as something I built for my own workflow, so I'm especially interested in hearing whether other developers run into the same problem.
I'd love feedback on the context → AI → patch → verification workflow, and particularly where it still feels cumbersome.
4 Comments
The AI-independent angle is probably the strongest part here.
Curious whether early users are adopting Vificil mainly to avoid the copy/paste workflow, or because the verification + rollback layer gives them enough confidence to let browser-based AI make larger changes.
That’s exactly what I’m trying to learn from this launch.
I originally built Vificil to get rid of the copy/paste workflow, but once I started using it for larger multi-file changes, verification and rollback became just as important.
My guess is that copy/paste is the initial hook, while verification + rollback becomes more valuable as people trust it with larger changes. But it’s still too early to know — I’m hoping the first users will tell me which matters more.
Thanks for your interest.