Interesting license choice, modified MIT it seems, with this additional clause:
> No licensee or downstream recipient may use the Software (including any modified or derivative versions) to directly compete with the original Licensor by offering it to third parties as a hosted, managed, or Software-as-a-Service (SaaS) product or cloud service where the primary value of the service is the functionality of the Software itself.
Doesn't that kind of conflict with the "including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software" part of regular MIT, which your custom license also includes for some reason?
I think you might be better of with just not trying to do it "kind of open source but also not" and just say "Copyright 2026 Sandgarden.com" or whatever, instead of the mix of proprietary and open source. Then you get 100% "full control" over what people can do with the source, and don't have to worry about anything when it comes to licensing :)
author here! the decision was mine; if anything, the senior leadership was fine with an unencumbered open-source license. What I didn't want was someone using it to make a business out of this tool without me in the mix.
In a sense, a futile effort; because if you reverse engineer a nlspec and rebuild it, then you can have it with any license you may want.
I wasn't doubting it wasn't you making the decision! :)
I was more curious why go with modifying a FOSS license (which clearly isn't the right choice if you want to prevent others from doing whatever with it) instead of just straight up keeping full copyright to yourself/the company and a "regular" license?
Then you get exactly what you want, without also sending double-messages about that people can do whatever they want, which is what you're trying to prevent.
I have been working on this for my own use until recently, when I shared with the rest of the team, and we thought it would be nice to let the world see it.
I have been interested in autonomous code development for quite some time (at least since March/April 2025) - and summer '25 is when I felt the models were good enough to be pushed to autonomy.
I wrote a bit about it[0], and sgai is the incarnation of my take on AI autonomous coding.
sgai is not even v0 yet, a lot of work to be done to improve its implementation - but I think it should be usable enough for those willing to give it a try.
author here! it is my daily driver for quite some time; with that said, its current shape is a bit of a more recent development. Initially, I would manually handle jj workspaces and fire out screen/tmux sessions; but over time, I figure it would be nice to have an UI that I could browse from anywhere through a VPN.
It does take some investment -- by adding customizations through the overlay folder (`sgai/` directory at the root of the repository) -- but eventually it should be able to code in a way that you would approve in a PR.
Sgai (pronounced "Sky") - That's a bit of a stretch
Depends on the language no? Works in German
Interesting license choice, modified MIT it seems, with this additional clause:
> No licensee or downstream recipient may use the Software (including any modified or derivative versions) to directly compete with the original Licensor by offering it to third parties as a hosted, managed, or Software-as-a-Service (SaaS) product or cloud service where the primary value of the service is the functionality of the Software itself.
Doesn't that kind of conflict with the "including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software" part of regular MIT, which your custom license also includes for some reason?
I think you might be better of with just not trying to do it "kind of open source but also not" and just say "Copyright 2026 Sandgarden.com" or whatever, instead of the mix of proprietary and open source. Then you get 100% "full control" over what people can do with the source, and don't have to worry about anything when it comes to licensing :)
author here! the decision was mine; if anything, the senior leadership was fine with an unencumbered open-source license. What I didn't want was someone using it to make a business out of this tool without me in the mix.
In a sense, a futile effort; because if you reverse engineer a nlspec and rebuild it, then you can have it with any license you may want.
I wasn't doubting it wasn't you making the decision! :)
I was more curious why go with modifying a FOSS license (which clearly isn't the right choice if you want to prevent others from doing whatever with it) instead of just straight up keeping full copyright to yourself/the company and a "regular" license?
Then you get exactly what you want, without also sending double-messages about that people can do whatever they want, which is what you're trying to prevent.
He said why, he wanted to open source it with the mentioned exception.
I think there are also licenses that do that, and revert to full MIT after some time, but the author decided to roll their own.
What’s the problem with that? He can license it however he wants and the reason he mentions is perfectly valid tbh
author here!
I have been working on this for my own use until recently, when I shared with the rest of the team, and we thought it would be nice to let the world see it.
I have been interested in autonomous code development for quite some time (at least since March/April 2025) - and summer '25 is when I felt the models were good enough to be pushed to autonomy.
I wrote a bit about it[0], and sgai is the incarnation of my take on AI autonomous coding.
sgai is not even v0 yet, a lot of work to be done to improve its implementation - but I think it should be usable enough for those willing to give it a try.
0: https://cirello.org/aifactory.html
Very nice, the automated setup instructions for opencode are a genius touch, more people should do that.
Is this already your daily driver for coding projects?
author here! it is my daily driver for quite some time; with that said, its current shape is a bit of a more recent development. Initially, I would manually handle jj workspaces and fire out screen/tmux sessions; but over time, I figure it would be nice to have an UI that I could browse from anywhere through a VPN.
It does take some investment -- by adding customizations through the overlay folder (`sgai/` directory at the root of the repository) -- but eventually it should be able to code in a way that you would approve in a PR.