Understanding FSL-1.1 license restrictions compared to OpenCode's MIT license

[hakan-77]

We have a GenAI platform that includes a built-in VS Code environment (via code-server). Right now we ship with OpenCode (MIT licensed) and it works great for us. I recently discovered Crush and wanted to try it out, but the FSL-1.1 license is a bit tricky to interpret.

Could you clarify what counts as a “competing product”?
We’re not planning to fork Crush or modify its code. We just want to understand whether bundling it as part of our platform would be considered a competing use under the license.

Any guidance would be appreciated.

[meowgorithm]

Thank you for the thoughtful question!

Using Crush server-side as part of a broader platform (for example, inside your hosted VS Code environment) is allowed under FSL-1.1-MIT. The main restriction is that Crush itself can’t be repackaged into a competing agent product or offered as a standalone service.

If you ever want to extend the integration or explore a deeper partnership, feel free to reach out.

And definitely let us know what you’re building!

[hakan-77]

Thank you for the prompt response, @meowgorithm.

We build a GenAI development platform, which comes with an IDE (code-server), inside which the user can open up a terminal and use OpenCode. As far as I understand, this use case is also OK for Crush FSL-1.1 license. I am closing the question as answered. Please feel free to comment if I'm misinterpreting anything.