PromptCoder Isn’t a VS Code Plugin - Here’s Why That Was the Right Decision

When we started working on PromptCoder, building a VS Code plugin seemed like the obvious move. Everyone does it - Copilot, Cody, even the smallest AI helpers.

But we quickly realized: that route wouldn’t give us what we wanted. Here’s why PromptCoder is browser-based - and staying that way (for now).

1. VS Code limits project context

Plugins usually work on one file or tab. That’s fine for suggestions - not for real refactoring.
PromptCoder was built to understand entire projects: structure, modules, dependencies.

2. The browser means zero friction

Click a link → start working. No installation, no config, no conflicts.
Perfect for quick tests, freelance projects, and side ideas.

3. We own the UX

The browser gives us full freedom to design project views, history, and versioning the way we want.
(GitHub sync is already in development.)

4. Onboarding is instant

No install guide. No barriers. Just send a link and go.

---

PromptCoder is still evolving. The product’s not perfect - but the foundation is working.
And it’s working well.

✨ This is part of our build-in-public journey. Feedback is welcome! Try PromptCoder → https://promptcoder.it.com