Feature Request: Add support for VK (VKontakte) - The largest social network in Russia/CIS

[flobo3]

Hey! First of all, thanks for this amazing tool. The browser bridge approach is exactly what we needed to bypass all these crazy anti-bot protections in 2026.

I'd like to request adding support for VK (VKontakte).

It's the #1 social network in Russia and the CIS region, with over 100 million active users monthly. It's basically the local equivalent of Facebook + Spotify + YouTube combined.

Since VK heavily relies on dynamic CSRF tokens (hash) and internal APIs (al_wall.php, al_feed.php) that are hard to scrape with traditional tools, opencli's browser-based approach would be absolutely perfect here.

Some basic commands that would be super useful:

• opencli vk wall <domain> (get posts from a user/community wall)
• opencli vk feed (get personal news feed)
• opencli vk profile <domain>

I know I could probably write a custom TS plugin for this, but considering the massive user base of VK, having it as a built-in command would be awesome for a lot of people.

Let me know what you think! I can help with testing if needed.

[flobo3]

Just to add some context and numbers to back this up:

• According to recent stats, VK is the absolute leader in content publications in Russia: https://www.statista.com/statistics/284447/social-media-platforms-by-publications-russia/
• Their latest FY 2025 report shows massive engagement and MAU growth: https://www.marketscreener.com/news/vk-q4-and-fy-2025-press-release-ce7e5eded989f321

Let me know if you need any help with the implementation or testing!

[Astro-Han]

+1 on this. VK's reliance on dynamic CSRF tokens and internal AJAX endpoints (al_wall.php) is a strong fit for opencli's browser session approach — exactly the kind of site where traditional scraping falls short.

One tool that might speed up development: opencli record <url> captures all fetch/XHR calls from a live browser session and can generate YAML adapter candidates from the recorded traffic. Running it on VK pages could reveal the internal API patterns without manual reverse-engineering — especially useful for figuring out al_wall.php's response format.

Whether this lands as built-in or starts as a plugin first, happy to help review if you put together a PR.

[flobo3]

Hey @jackwener and @Astro-Han! Thanks for the tips on using opencli record. It turned out VK uses a JSON Hijacking protection (prepends <!--... to JSON responses for legacy endpoints), which is why the heuristic couldn't catch the API calls automatically.

I ended up writing a custom plugin that extracts the access_token from the live session's localStorage/HTML and makes clean requests to VK's new internal API (wall.get, newsfeed.get, newsfeed.search).

It works perfectly and lightning fast! 🚀

For anyone looking for VK support, I've published the plugin here: https://github.com/flobo3/opencli-plugin-vk

You can install it via:

opencli plugin install github:flobo3/opencli-plugin-vk

[Astro-Han]

Nice work! The approach of extracting access_token from the live session and hitting VK's internal API is clever — best of both worlds.

If you'd like to get it listed in the README plugin table, a one-line PR adding it here would do it. Happy to review.