I forked a vibecoded IDE scaffold because it was Qt (not)

One Georgian guy with a lot of expendible Claude Opus had a vibe-coding spree in May to make an AI-native IDE in Qt and C++, and called the project Exorcist. His prompts were pretty much to make it have Copilot.

The chat view was at some point migrated by his Claude to a WebView — based on proprietary Ultralight engine to save RAM rather than picking QtWebView. The tests stopped even building without it — the old Qt-native chat pane was dead code. I made a PR to fix that at first, and he merged it after a while.

On personal branch, I applied a lot of Deepseek to it, starting with

• removing Ultralight and going back to the Qt-native chat view,
• removing the JS plugin system because it was meant for the chat web view and redundant with a Lua plugin system
• removed Copilot branding and made setting up BYOK tidy, with a way to maintain many providers and models, as well as OpenRouter OAuth
• started attempting to refactor the 116 tools set into virtual MCPs

I used OpenSpec all along to have some brownfield spec for the changes.

I don't think there is any patch management functionality done in it yet. Tools weren't even properly injected into BYOK prompt when I started, only in case of Claude connection where they go elsewhere in the API call.

The whole idea of multiple types of providers, a connection to the real Github Copilot, to cloud Github Copilot, to Claude, each having a different feature set already implemented… an awful lot of feature creep.

I gave up when I fell once again into perfectionism about what do I really want to make of it.

• The lack of diff hunk management system made me want to take the approach of Aider-Chat to just commit every single file edit call,
• I got interested in the ways of Entire.io and Git AI to keep the whole transcript in the same Git repo,
• MemFit paper (Piehl, Ye) came out and I got interested in implementing its semantic search for the transcripts,
• codemode also entered Pi and thus the old ways of progressive disclosure distinguishing tools and MCP servers became obsolete and unworthwhile.

And a lot of that daydreaming I could approach from the side with some OOP, but I side-tracked into reading more daily arXiv papers, social activities, and another pet vibe-coding project I have. Although OpenSpec helps with returning to a project after a while.