I can let my agent edit those files all the same + there's better integrations and knowledge readily available on these.
I can tell my agent to edit the Obsidian Markdown just like that, but I can also tell it to create a full-on notebook with backlinks and DataView queries. I can tell my agent to create logically complex .org notes with code blocks and references.
To me, Hubble just seems like a Markdown editor, based on the premise that agents are able to edit local files.
There's a few reasons I built it instead of continuing to use Obsidian (which I've used for years):
- I wanted something closer to Apple Notes or Notion for simpler editing. Hyperlinks are popups instead of in-line strings. Formatting is WYSIWYG, without *_ characters in-line. There's a / menu to discover formatting options. etc.
- I wanted an app that could display HTML pages alongside Markdown. And more interestingly, I wanted to give those HTML pages access to Markdown files in the folder, using Markdown as a mini-database to build apps on top of. This is likely possible with Obsidian plugins (everything is) but I wanted something first-class. The hubble.md homepage tries to communicate this, but I could likely do a better job :)
- More recently, I've wanted markdown -> agent handoff to be better. We've added an embedded terminal to chat with agents alongside notes directly, and we've just added a first-party commenting system similar to commenting in a Google doc (agent accessible with in-file metadata). All of these features have been community-led. I'm very grateful for our repeat contributors.
If any of that sounds interesting, give it a try! Otherwise, feel free to give feedback on the app itself or the homepage on GitHub. All of that is open-source: https://github.com/bholmesdev/hubble.md
- I wanted something closer to Apple Notes or Notion for simpler editing. Hyperlinks are popups instead of in-line strings. Formatting is WYSIWYG, without *_ characters in-line. There's a / menu to discover formatting options. etc.
- I wanted an app that could display HTML pages alongside Markdown. And more interestingly, I wanted to give those HTML pages access to Markdown files in the folder, using Markdown as a mini-database to build apps on top of. This is likely possible with Obsidian plugins (everything is) but I wanted something first-class. The hubble.md homepage tries to communicate this, but I could likely do a better job :)
- More recently, I've wanted markdown -> agent handoff to be better. We've added an embedded terminal to chat with agents alongside notes directly, and we've just added a first-party commenting system similar to commenting in a Google doc (agent accessible with in-file metadata). All of these features have been community-led. I'm very grateful for our repeat contributors.
Now, I'm having fun with tldraw.[1] With their new tldraw offline, I can continue to work in Claude Code (and others) and I can either output or interact/input from tldraw. This is more of a free-form, infinite canvas. I treat it like Excalidraw + Draw.io + Freeform Notetaker.
For text, most agents/LLM/assistants are pretty happy and smart using the same Markdown files to anywhere I have allowed them to interact.
Since this project uses such good agentic engineering practices, I was able to use Claude Code to add support for Mermaid diagram rendering and produce my very own local build on Mac, all in about 30 minutes.
Thank you! Hubble+cmux gets me close to the agentic IDE I’m working towards.
Do you mean "good code" and "good documentation"?
I really like it as I run a webdav service and can read/write and sync notes between multiple Mac desktops and Android. Encrypted while I am at it.
Markdown native.
And before you ask, the next "trend" will be as much tiring.
I feel like tables are generally underrated while the AI ecosystem is focused on .md files but I guess markdown has tables so they’re included to some extent
Can you easily share lists or pages or is it all local? (Is there a cloud element to it)
What are the most useful examples you’ve personally found when it comes to using the HYML component?
I built https://smalldocs.org for my agent’s Markdown needs. I extended it so it can render complex formats: Mermaid diagrams, charts, in-document slides and even in-document spreadsheets. It gives your agent a good selection of formats to express itself as it helps you understand whatever topic you’re looking into.
Here is a sample document: https://smalldocs.org/blogs/what-is-a-smalldoc
I publish anonymous analytics here: https://smalldocs.org/analytics
It has a rest api and a cli tool, and also the possibility to make headless deployments, and it can sync clips without a sync server. It can serve folders/tags and optionally expose a read or read/write api for JSON files on the same level. It supports lua plugins, and I have a fal.ai plugin to generate/edit images already in the repo (some other examples there).
It has a lot of features so maybe it's better if I just link to the docs: https://egeozcan.github.io/mahpastes/
Add to that the fact that it's likely entirely vibe-coded, there's really 0 value proposition here.
"Agent ready"? Eg, it uses markdown like... everything else? There is literally no information here.