I checked the last commit on the readme file and there seems to only be one adding support for mobile friendly?
I’m only asking as that’s where I look for an overall progress of this project. I’m certain there is so much going on in various corners and maybe there is a better place to get a high-level progress overview?
I’m not used to diving into PR and the actual git repository, but I’m sure I could get many questions answered there.
Thanks for everyone’s hard work, this is really interesting to follow!
Thank you very much for clarifying this for me @digitalchild. I will investigate now. I believe a simple place for “non-coders” interested in this project to see the latest updates will be beneficial for the project in the long run. For those that understand git it seems obvious
Readme may become a big unamangable thing if we add everything to it.
But I could agree that we may need a better way to communicate changes.
People like @ColeMedin and me and few others are making videos once a week with updates.
Thanks a lot @wonderwhy.er that’s also very helpful! I’m particularly wanting to stay in the loop on the feature for not re-writing full files when it makes changes. Is there a way to “subscribe” to that or see where it is?
Oh and btw, I’m really amazed to see all the activity in the issues and PRs! It’s incredible to see so much happening! My initial post was in no way intended to insinuate that progress isn’t happening
Hey man, not sure if anyone yet actively works on this
I would say that import/export of projects is more urgent.
Prompt optimisations, context use optimisations, and selective updates are there too, may be coming a bit later.
Its bit of a tricky feature, especially considering we are supporting many providers and many models. And models would react differently to such a feature.
I’m actually going to poke around at something like this to generate a changelog as time allows me to. Great idea and provides a one-stop shop to decide whether to pull latest changes, I’ll respond here if/when that happens.
I’ve found the most success screening the “Contributing.md” files of repos in trying to reverse engineer the best way to implement. I’ve got about 30 days coding experience myself, haha.
we can use github actions to setup semantic-release pipeline this can generate change log and commit it to the main branch with each release (once a tag is pushed we can setup it to generate changelog)
That could also be useful in the future for say building a benchmark tool to see which models pass and fail what test prompt. Also could be used for prompt injection (drop-down, features, etc). Idk, the idea has potential.
I’m not sure if this is the right place for this and I wasn’t sure if I should start a new topic about it. I tried searching the forum here but I didn’t see anything that seemed relevant.
Is there any set release date for bolt.diy? Is there any published roadmap or projected release date? Is it on the readme and I didn’t see it?
I don’t know if you’re getting at what I’ve been thinking about (but it almost seems like it)…
It would be super useful to be able to save prompts and reuse them at will and to be able to organize them and associate them with specific projects (maybe like a library sort of feature - like the old figma used to have - that gets made available to projects through a configuration item or ui component??).
I think it should definitely rely on git as a a backbone though and give the flexibility to manage it in your repo however you need to (eg: an independent long running branch, etc). At least that way you would have the option available to keep your prompts in your git repo, you own it, its portable if you want to move it around or whatever (its just there in your repo - not some other independent repo or even different vcs).
It just feels to me like the whole prompt management thing should be somewhat independent of the codebase (even if were in the same repo). Or another way to think about it is the codebase itself should not be poluted with prompts. But not I’m getting picky and probably a bit opinionated (sorry).
That’s my 2 cents on it anyway. I hope I’m not going off on something totally different but when I saw your post here it made me think of it and this is something that’s been weighing on me for a bit (handling prompt management).
Well… but this reads as if there is a stable release now (already). I have been able to run bolt.diy (both with the development option as well as the production option) but it is still unusable to me. I talk about this in another thread trying to resolve the issue but I’ve been installing and trying to make it work for a couple weeks now I think and I still have never been able to use it once.
