📊 Quick Stats

📦 900KB Code • ✅ 356 Tests • 📚 1,000KB Docs • 🎨 WCAG 2.1 Built-In • 💰 $0 Spent • ⏱️ 8 Months • 👥 2-Person Team • Made in India 🇮🇳

🎯 What is VebGen?

VebGen is the first AI-powered development agent that understands your code without reading it.

While tools like Cursor and GitHub Copilot help you write code faster, VebGen builds complete, production-ready applications from natural language—with innovations no other agent has:

📢 Early Feedback:

"VebGen is the future of AI development - I built a full Django REST API in 10 minutes!" - Early Adopter

"Finally, an AI agent that doesn't break my code!" - Beta Tester

Major Additions

📖 Full v0.3.0 Release Notes: releases/v0.3.0.md
📖 v0.2.0 Historical Release: releases/v0.2.0.md

🏆 World Firsts

💎 How is VebGen Different from Copilot or Cursor?

While tools like GitHub Copilot and Cursor are amazing for helping you write code faster, VebGen works on a whole different level. Think of it less like a code-completion assistant and more like hiring an entire development team to build a project for you—from scratch to deployment.

📊 VebGen vs. The Competition

TL;DR: VebGen is the only agent with AST-based intelligence, built-in sandboxing, AND dual-agent remediation—all for free. 🚀

The Game-Changing Differences

🧬 Zero-Token AST Parsing

VebGen reads your entire codebase without consuming any API tokens. While Cursor charges you to analyze your own code, VebGen uses Abstract Syntax Trees (AST) to parse Python/Django projects locally.

💡 What this means: Cursor and Copilot charge you (in tokens) to read your own code. VebGen never does. Your existing codebase analysis is 100% free, 100% instant.

📖 Technical Deep Dive: See Code Intelligence Service Documentation for AST parsing implementation details.

🛡️ Military-Grade Command Security

Afraid of AI agents accidentally running rm -rf / or exposing your secrets? VebGen has production-ready security validation that never trusts the LLM:

• ✅ Whitelist-only execution (only approved commands run: pip, git, django-admin)
• ✅ Regex blocklist (dangerous commands auto-blocked with safe alternatives suggested)
• ✅ Multi-layer path validation (prevents any file access outside your project)
• ✅ User confirmation required for all sensitive operations
• ✅ No direct shell access for the AI—ever

💡 What this means: Other tools let the LLM execute commands with basic validation. VebGen treats every command like a security audit. Your production server stays 100% safe.

📖 Security Implementation: See Command Executor Documentation for whitelist/blocklist mechanisms and Secure Storage Documentation for API key encryption.

💾 Never Lose Progress—Ever

VebGen's Memory Manager ensures you can close the app anytime and continue exactly where you left off—even if something goes wrong.

Here's what actually happens behind the scenes:

📂 Automatic State Persistence Every action (files created, commands run, features completed) is saved to a hidden .vebgen/ folder in your project. Close VebGen mid-development? Reopen it, and you're instantly back in the same state—no need to explain context again.

💡 What this means: Unlike chat-based tools that lose context when you close the tab, VebGen remembers everything. The AI picks up exactly where it stopped—with full memory of what's been built, what's pending, and what failed.

📖 State Management Details: See Memory Manager Documentation for backup algorithms and Project Models Documentation for state schema.

🔐 Corruption Protection with SHA-256 Verification
Every time VebGen saves your project state, it calculates a SHA-256 cryptographic hash of the data. When loading, it verifies the hash matches—if it doesn't (file corruption, system crash, disk error), VebGen automatically restores from the most recent valid backup.

🗂️ 5 Automatic Backups (Timestamped)
Before saving any state changes, VebGen creates a timestamped backup. It keeps the 5 most recent backups, pruning older ones automatically. If all 5 backups are tested during recovery and fail, VebGen notifies you instead of silently using corrupted data.

⚡ Atomic Writes Prevent Partial Saves
State files are written to a temporary file first, then atomically swapped using os.replace(). This means if the system crashes mid-save (power loss, force quit), the old file remains intact—no partial writes, no corrupted state.

🔒 Thread-Safe Operations
All file operations use a threading.Lock to prevent race conditions. Multiple parts of VebGen can request saves simultaneously without data corruption.

🗑️ Soft-Delete Trash System
When state files are "deleted," they're actually moved to .vebgen/trash/ with timestamps. Accidentally cleared project state? Manually restore from trash instead of losing hours of work.

🔄 Intelligent Error Recovery (Self-Healing)

When the LLM makes mistakes (and it will), VebGen automatically fixes them without human intervention.

Here's the multi-layer safety net:

🎯 Automatic Syntax Validation
After every file modification, VebGen compiles Python files to detect syntax errors immediately. If a patch breaks the code, it automatically rolls back to the last working version from the .bak snapshot.

💡 What this means: The LLM can't leave your project in a broken state. Every file modification is validated before being committed. If CASE introduces a syntax error, VebGen instantly reverts the change and tries a different approach.

📸 Snapshot-Based Rollback System
Before every risky operation (file writes, patches, command execution), VebGen creates a lightweight snapshot of affected files. If anything fails, the entire operation rolls back atomically—no partial changes, no corrupted state.

Rollback triggers include:

• Syntax errors after patching
• Failed patch application (context mismatch)
• Command execution failures
• User-initiated abort (ROLLBACK action)

🔁 3-Attempt Remediation Loop
When CASE fails