Show HN: Ledge.sh – Runnable Markdown Notes
Ledge.sh is an open-source markdown note-taking app that executes interactive shell, database, and programming blocks locally or over SSH.
summary is enough The features and architecture are clearly outlined on the landing page, making a deep read unnecessary unless you plan to adopt the tool.
summary
Ledge.sh introduces a Markdown-based notebook where code blocks execute interactively in persistent shells, local environments, or remote servers via SSH. It supports mobile access, environment profiles, and a Model Context Protocol server for AI agent integration while keeping notes as plain files on disk. The creator designed it to bridge the gap between static documentation and command execution without requiring proprietary databases. Commenters praised the utility while drawing historical parallels to tools like org-babel and Jupyter.
key points
- Notes are plain Markdown files stored locally or on an SSH-accessible server, making them fully compatible with Git and standard file sync tools.
- Code blocks run in persistent interactive shells where variables, virtual environments, and working directories carry over between executions.
- A built-in MCP server lets AI assistants like Claude read, search, and execute commands within your workspace.
who should read it
Software engineers and DevOps practitioners who maintain command-heavy runbooks and technical notes.
discussion warm
consensus
Commenters are enthusiastic about the concept, comparing it favorably to Jupyter and Emacs org-babel while praising its focus on plain Markdown and interactive shells.
pushback
A former developer of a similar discontinued project pointed out that executable runbooks struggle to scale because users rarely keep documentation up to date.
(hi! I worked a lot on atuin desktop)
we saw a bunch of issues with desktop, in no particular order
1. authoring runbooks is difficult, most people barely document their work let alone make it executable
2. keeping runbooks up to date is difficult, they are error-prone across systems
3. agents are now pretty good at a number of the tasks these ideas solve for, and are good at working around issues caused by docs becoming out of date/etc
all these tools are great for your own notes, but are very difficult to scale
It offers pragmatic, first-hand insight into why executable documentation tools historically fail to achieve mainstream adoption.
Generated by an LLM from the article and thread. Check the sources before relying on it.