Today we are thrilled to officially announce the opening of 🎭 Shakespeare: Act II. Act II is a dramatic improvement over the first version of Shakespeare. We have completely rewritten the codebase from the ground up to make it the most freedom-respecting AI web builder available. Read more: Try it here: What makes Act II different: 1. Runs entirely in the browser: Unlike Act 1, where your project files were stored remotely on our NSP servers, now all of your projects are stored locally in your browser — so you retain all control and full privacy. 2. Full AI provider and model choice: Before, you were locked into only the providers and models available from NSPs. With Act II, you can configure ANY AI provider you want. Bring your own credentials from your favorite provider like PerPerQ, Routstr, OpenAI, Z.ai, and Anthropic; use our pre-configured Shakespeare AI provider (with both free + paid tiers), or even run your own local model! This is the most choice of ANY AI web builder we’re aware of. 3. Complete development environment in the browser: We’ve built a text editor, terminal, and git version control integration directly into Shakespeare. The new changes we’ve made to the architecture of Shakespeare unlock new possibilities. One feature we’re most excited about is the ability to “Edit With Shakespeare.” Find any compatible open source project and start improving it in Shakespeare with one click! This is the power of open source, and with AI it’s finally accessible to everyone — no matter your technical level. Want to try it? Pick any app or template from our showcase and click “Edit with Shakespeare”! Showcase: Need help? We know debugging is always the worst part of building. We’ve built multiple new tools into Shakespeare to make it easier, including an in-web console to show errors, and a friendly assistant called Quilly who may make an appearance to alert you to key errors. Keep an eye out for him! We’ve also built out a detailed Shakespeare resource center with an FAQ and guides on how to get the most out of Shakespeare. Resource center: Shoutout to our team and community who have been working tirelessly for the past 3 months on this release! @Alex Gleason @MK Fain @chad @MAKE SONGS LONGER @Derek Ross @lemon @Sam @danidfra@danidfra.com @Patrick PReis @shantaram And, finally, thank you to @npub1t5u3...j4c2 @OpenSats and @HRF for making this work possible!

Replies (26)

Let’s go! Incredible work on this. Does the updated codebase have the references in it to build out Nostr compatible login with nsec managers like Nsec.app? I think these are done through NostrConnect and bunker codes. *apologies for my non-technical lingo
.'s avatar
. 8 months ago
This is awesome! Congrats 🔥🔥🔥🔥🔥🔥 Loading up vibes ✨
I'm sorry that happened :( Tbh we're considering turning off the free model entirely because of this pattern. We want people to have something they can try without any cost, but the reality is that only good models work well, and good models cost money. Let us know how the Shakespeare flagship model does? Or if you use another provider, I recommend Claude Sonnet or GLM. More details on the models and what to expect from each here:
Yes I need to find some time to play around with it. Looks like a really nice web builder tool to get something spun up fast. We do need to migrate as we will need a host to allow for merch and payments soon. This might be a good solution. Let's get some ppl doing some testing and due diligence!
Thanks for the update! I'm glad we got it sorted! This is good feedback about the UI format regardless 🙏
> "When using git in the Shakespeare terminal, it does not show of the any local commits that the AI made." Can you tell me more about this? I'm not able to replicate it. If you could do git log in the terminal and screenshot that and compare it to the commits you see under "rollback", that would be super helpful. For example, here is what I see, and they appear to match:
Actually: can you try one more thing, just for my sanity... Can you scroll up to the very top of that git log output and see if the new Shakespeare commit is up there? They are in reverse chronological order from the top, and I think there's a chance its just so much output you can't see it without scrolling 🤞
To be honest the free AI is very hit or miss. Sometimes it's fine for testing and works as a perfect trial and error tool for newbies to learn how to use Shakespeare and to learn how to talk to an AI. But because it's free, and uses a cheap and lean model, it sometimes takes shortcuts and doesn't complete the work. If you have API keys from one of the larger or top models, I'd recommend using that. You'll see an incredible difference.
This is the key here. It's not full git that you're using to using on your terminal on your computer. We can probably improve some functions perhaps.
> What we built (often with AI-assistance in the terminal and code editors) is a website The exact thing which can be built with no coding skills, by just telling the model to build it and watching it. How did that take so much work? > We did use our own tools to build it! But we also had to build, update, and maintain those tools in the first place, too :) Why? If the model is the same, and if it can build websites on its own, why was it a tool and not straight up the developer? > Yes, there are limitations on what AI can build Really, because the website says "Just tell Shakespeare what website you want to build, and watch it create professional sites". How does the frontend to the existing model not qualify as a professional site?