Suggestions for Lexkit

[novincode]

Hey, feel free to suggest features, or report issues.
enjoy using Lexkit.

[vineetdigit]

This is a great initiative!

I'm wondering if you have any plans on supporting AI features like auto-complete or steaming markdown?

[novincode]

This is a great initiative!

I'm wondering if you have any plans on supporting AI features like auto-complete or steaming markdown?

Hey, thanks for the suggestion — really appreciate it.

AI is definitely interesting, and yes, it can still be done in a headless way. The idea would be to ship it as optional extensions so the core editor stays clean and unopinionated. Things like AI autocomplete or streaming Markdown can be achieved by exposing commands/hooks rather than baking UI or providers into the core.

That said, real-time collaboration (Y.js) is currently a higher priority for me before AI features. I’m building this step by step and so far it’s been a solo effort, so growth and contributors will help unlock more advanced features faster. AI extensions, streaming Markdown, and collaboration are all on the roadmap — no limits here.

Thanks again for the input — keep the ideas coming!
— Shayan

[vineetdigit]

I love that you are thinking about AI features as headless, and that would be the right direction. I'm surprised that we haven't seen any AI extensions available in the Lexical itself so far.

What exactly are you planning for collab-editing with Y.js that lexical and its plugins doesn't support already?

[novincode]

Good question @vineetdigit,
Lexical does have some Y.js experiments, but they’re not production-ready and don’t cover custom nodes, undo history per user, or proper presence APIs. The idea for LexKit is to provide a clean, plug-and-play Y.js extension so people don’t have to wire everything manually.

To be clear — I haven’t shipped this yet. I’m building LexKit step by step as a solo dev, so I need to prioritize core stability and adoption first. But solid real-time collaboration support is definitely on the roadmap.

If you have specific requirements or use cases, feel free to share ;) it helps shape the direction.

[vineetdigit]

Thanks. If you are open to accepting contributions, I'd like to contribute if possible. Do you have any particular area or specific tasks where you need help? I understand that sometimes it's hard to carve out specific tasks when you're starting out. But even without specifying exact work, if you could just write down an initial set of features that you are prioritizing for Y.js, that would be great.

…

On Fri, Oct 24, 2025 at 6:36 PM Shayan ***@***.***> wrote: *novincode* left a comment (novincode/lexkit#2) <#2 (comment)> Good question @vineetdigit <https://github.com/vineetdigit>, Lexical does have some Y.js experiments, but they’re not production-ready and don’t cover custom nodes, undo history per user, or proper presence APIs. The idea for LexKit is to provide a clean, plug-and-play Y.js extension so people don’t have to wire everything manually. To be clear — I haven’t shipped this yet. I’m building LexKit step by step as a solo dev, so I need to prioritize core stability and adoption first. But solid real-time collaboration support is definitely on the roadmap. If you have specific requirements or use cases, feel free to share ;) it helps shape the direction. — Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACUGSRKH24J5I6O4R3O3IQD3ZLH3DAVCNFSM6AAAAACG4IG4AKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINBVGQ2DANZVG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[novincode]

Hey @vineetdigit — awesome to hear you’d like to contribute! 🚀
I’d love to collaborate.

About the roadmap: earlier I mentioned Y.js as a priority, but honestly I’m open to contributions in any direction that makes LexKit better. If you have ideas for collaboration, AI features, new extensions, or tooling — I’m all ears. Feel free to share what you think should be the next move for LexKit.

If you're up for a quick chat to plan things, reach me here:

Telegram: @codeideal_support
Discord: https://discord.com/invite/RAMYSDRag7
Email: ideyenovin@gmail.com

Looking forward to hearing your thoughts!