Can’t wait to see all of this in Observable. Could you provide more details about which features will be free and which ones will be limited to Pro accounts?

Embedding will be paid; I'd guess "Add external collaborators to a notebook" will be too. "Improved multiplayer editing" is inherently a paid feature by virtue of it requiring a multi-person team. I think the rest should be free. In general, we wanna keep pricing relatively simple by mainly charging for fundamental primitives like tokens and (eventually) compute.

Do I now have to go to old.observablehq.com/search to actually search for notebooks? There's no searchbox in the new UI for public notebook listings that I can find...

Yes, that’s right. Search is listed as upcoming above.

Are you planning to add snippets to help with writing charts, maps, or inputs, as was the case in the old version of Observable? For example, Leaflet code snippets.

No; we’re eschewing preset snippets this time around. It was always a little tricky: we could cover a lot of common cases, but there’s an extremely long tail. It felt weird to decide what everyone’s top snippets should be when our users are so diverse. Some mostly use SQL, some never do. Some think of us as synonymous with visualization, some have no interest in it. We originally wanted to make the snippet library customizable, but never got around to it. Today, AI covers so many of these use cases so well, so flexibly, that it’s hard to justify the added concept of the snippet. We do want to continue to improve autocomplete (notably for SQL). And we do recognize that a finite prioritized menu of discrete options offers a more intuitive structure for the possibility space than open-ended AI. People talk about the “blank page problem”, the weird vertigo by which “you can do anything!” curves around to feel like “you can do nothing”. I wouldn’t be surprised if some snippet-like concept came back eventually. But today, with too many priorities already, I think we can say that snippets aren’t among them. (Still — curious how you used them, which you used, which you ignored, which you wished for!)

Snippets were particularly useful for the geography students I teach. They’re not developers, so being able to show them that they could create inputs, make a bar chart, or display a GeoJSON file with Leaflet in a single click often helped them realize that this tool was accessible to them too. It was often a real lightbulb moment. While I understand your arguments and your priorities, it’s really a shame to see this feature go away. As a teacher, I’m going to have to work a bit harder to get my students started. C'est la vie.

For what it's worth, I am happy to see that snippets are not part of 2.0. I recognise that we all have different experiences, but for me, the presence of snippets for my students (who also include those with no technical or programming experience) would often result in 'look, I've got a plot in may page!' but without the requisite understanding of how its design elements related to the code, and how they might be customised should people want to change them.

Love all of this. The two most wanted features for me are: 1) Version history: I've multiple times screwed up a notebook and only thanks to the agent's history were able to recover it. So a built-in version history would help me a lot. 2) Notebook import: This is a big one for me. My typical workflow involves raw data processing, and some analyses that I need to perform offline with large datasets. Then I typically prepare a report offline with notebook-kit (Claude Code does a great job with it), and then to share with collaborators I then create an online version with Observable Notebooks. For this last step I've used copy-paste from the notebook-kit version, which is annoying. At one point I've asked the Observable Agent to import the notebook from a public GitHub source, which worked well enough, but ate up all my tokens 😂 so I switched back to copy-paste. A simple import would be lovely!

1) Totally agree. FWIW, there’s a workaround: go to old.observablehq.com (just put “old.” in front of notebook URL) and browse / compare / revert history there. The new site supports viewing notebooks at a given version with “@123” (e.g. https://observablehq.com/@tophtucker/classic-research-in-data-visualization@592), but we don’t expose any UI around it yet. 2) Also totally agree! This morning we were just discussing better supporting exactly that sort of agentic workflow…