Seems stable and feature-full enough now.
What does the user community think?
What does Jesse think?
Jesse says yes! Or at least time to update the docs. It’s still going to be at least a few weeks of docs + website + etc. But fingers crossed that code changes are slowing way down.
2 Likes
I think so! Bike 2 is excellent & I have been using it ~daily for quite some time now.
1 Like
These things happen in their own time.
When a melon is ripe it falls from the vine …
I’d love to see an updated support document specifically about extensions, because I’m a bit lost with them at the moment.
When they were first introduced, I played around with them a little, but since then a lot seems to have changed and improved. Right now, I’m not really using any of them, although I’m pretty sure they could make a big difference once I get back into them.
I know there are already some documents available, but a simple, beginner-friendly extension manual would be really helpful – something that makes it easier to understand how to create and use them step by step.
Yes, updating extension docs is on my list. Another problem is the docs have moved a few times. They now live here on github. I think I will keep that same general level of detail. If you think there’s a need for something higher level please describe what you would like to see. Also note, I want to keep same level of detail, but I haven’t reviewed those docs for quite a while, so they are likely out of date in places.
Last, LLMs have lots of problems, but in my experience they are really good at the level of complexity required to build Bike extensions. Specifically the ones that have file system access, like Claude Code, I think you can just give them the URL of Bike’s extension kit. Also to create a new extension that does X, and it should get you pretty far.
2 Likes
Will dig in to github for the docs.