Ledge: The notebook that runs code

The notebook that runs shell commands, code, SQL, and AI promptsNew subscriptions this weekStripe API notesNew subscriptions this week---profile: stripe---Monday check on last week's signups. The stripe profile holds the API key and database URL. Endpoints are in Stripe API notes. #growthshcurl -sG https://api.stripe.com/v1/subscriptions -u "$STRIPE_KEY:" \ -d limit=100 -d "created[gte]=$(date -v-7d +%s)" > subs.json jq -r '.data[].plan.nickname' subs.json | sort | uniq -c | sort -rn24 Pro, 11 Team, and 3 Business since last Monday.pythonimport json subs = json.load(open("subs.json"))["data"] mrr = sum(s["plan"]["amount"] for s in subs) / 100 print(f"{len(subs)} subscriptions, +${mrr:,.0f} MRR")38 new subscriptions, adding $2,682 in MRR.sqlselect source, count(*) as upgrades from accounts where upgraded_at >= now() - interval '7 days' group by source order by upgrades desc;The database agrees: 38 upgrades. Newsletter 17, docs 12, referrals 9.promptWrite this week's growth update from this note for #teamLedge is a Markdown notebook for developers and DevOps. Write a note, press ⌘↩ on a code block, and its output streams in beneath it. In your shell, in your project, on your machine, or on a server.Install Ledge Servercurl -fsSL https://ledge.sh/server.sh | shFree and open source · Apache-2.0 · macOS on Apple Silicon · Linux · Windows 11 with WSL · iPhone and iPad · Android (beta)Each note has its own shellShell blocks run in a persistent shell that belongs to the note. A cd, an exported variable, or an activated virtualenv carries into the next run.⌘↩ runs the block under the caret. Output streams in beneath it.⇧⌘↩ sends the block to the note's terminal drawer, a second shell you can keep typing in.A running block takes input. Answer a sudo password or a [y/N] in the output panel.cwd: and env: in the frontmatter set where the note's shells start and what they carry.norun on a fence takes the Run button away. Use it for a command you are quoting, not running.Docs: Running CodeInvoice rounding bugInvoice rounding bugTotals drift by a cent on partial refunds. Repro first. #billingshcd services/billing && source .venv/bin/activateshpytest -q --tb=no tests/test_refunds.pyTerminalKeep your notes on a serverPoint Ledge at a machine over ssh and the notes live there. The server holds the files and runs the shells. The app on your computer is the window onto it.No account, no service, and no port to open. The only thing between you and the server is ssh.Shells and running blocks belong to the server. Close the laptop and they keep going. The output is waiting when you open it again.Your computer, your phone, and a second window can all be on one server at once, each with its own tabs.Sign in with an ssh key, or with a password kept in the system keychain. Ledge pins the server's host key and refuses any other.Install with the command below. ledge backup puts an encrypted copy of the notes in an S3-compatible bucket every hour.Install Ledge Servercurl -fsSL https://ledge.sh/server.sh | shDocs: Keep Notes on a Remote Servervps-1---cwd: ~/api---Cut 2.4.2 from the server, not the laptop. The build takes a minute.shmake releaseThe same notes on your phoneLedge runs on iPhone and iPad as a window onto the same server. The phone holds no notes. It reads, edits, and runs what is on the server.Read, edit, and create notes with live preview. Search, tags, backlinks, daily notes, and wikilinks all work.Tap Run on a block and it runs on the server. Switch apps and it keeps running. The output is waiting when you come back.^C, ^D, Escape, and the arrow keys sit above the keyboard, so you can interrupt a command, quit a pager, or move around in htop.Scan the pairing code that ledge pair prints on the server. The phone signs in with a key made in the Secure Enclave that never leaves it, and that key can speak to Ledge and nothing else.Locked notes unlock with the passphrase. The phone stores none of it.Docs: Ledge on Your PhonehomelabMedia serverTwo episodes transcoding. Check before starting a third.shhtopBI[[Run blocks on other machinesAdd a host: line to the frontmatter and every run in the note happens over ssh on that host. The note itself stays where it is.Declare several hosts and Ledge asks which one on every run. Enter repeats your last pick.Mark a block confirm and Ledge shows the code, names the machine, and asks before running it.Authentication is your own ssh. Keys, agents, ~/.ssh/config, and 2FA work as they do in a terminal.The note's cwd and env travel with the run. Profiles and secrets never do.python, node, and other interpreted blocks run on the host too, with a per-machine interpreter override in Settings.Docs: Run Code on Remote Hosts---cwd: ~/Projects/apihost: staging, deploy@prod---Stale session keys after the 2.4.1 deploy. Flush staging, verify, then prod.sh confirm="Flush the session cache?"redis-cli -n 2 flushdbPut notes side by side⌘D splits the view left and right, ⇧⌘D top and bottom, and either side can split again. Each pane has its own tabs.Every note keeps its own shell, so two panes are two working environments. A run keeps streaming in the pane you left.Drag a tab to another pane. It keeps its caret, scroll position, undo history, and any output still streaming.⌃Tab cycles tabs. ⌃1 to ⌃9 jump to one by position.Each workspace saves its layout and restores it at the next launch. ⌘1 to ⌘9 switch workspaces, layout and all.One terminal drawer spans the window and follows the focused note.Docs: Panes and TabsTrial length bugcwd: ~/Projects/apiTrial length bugSome trials end a day early.shgo test ./...Secrets stay out of your notesA profile is a named file of environment variables kept outside your notes folder. A note that names it gets the variables in its shells. The note carries only the name.profile: deploy in the frontmatter reads ~/.config/ledge/profiles/deploy.env, a plain dotenv file readable only by you.Notes get synced, backed up, and read by agents. A profile value stays on the machine.Any number of notes can share one profile. An env: line overrides a value for one note.A built-in editor shows the values masked, with one toggle to reveal them.envFile: .env loads the project's own dotenv for everything that is not a secret.Docs: Profiles and Secrets---cwd: ~/Projects/apiprofile: deploy---Backup restore drill. The AWS keys come from the deploy profile.shaws s3 ls s3://ledge-api-backups/nightly/ | tail -2Built to be worked by agentsLedge ships an MCP server. claude mcp add ledge -- ledge mcp connects Claude Code, and any MCP agent can read, search, create, and edit your notes through it.Notes are addressed by title, which survives renames, so an agent's references do not go stale.A terminal opened inside a note knows which note it is in. "Add a TODO section here" needs no explanation.A prompt code block is a runnable block. ⌘↩ pipes it to the agent and the reply streams in beneath it.Agents can read your settings and the manual, so "check the Ledge docs" is a fair instruction.There is no delete tool, and locked notes refuse their bodies to every agent.Docs: Agents and LedgeRelease 2.5.0Release 2.5.0Tag after the migration bake. Checklist in Release runbook. #releaseshgit log --oneline v2.4.1..HEAD | head -3Done84 ms9f31c22 storage: chunked uploads for assets over 50 MB 41b0a07 api: rate limit per token, not per IP c2ade19 fix: retry idempotent writes on 5xxTerminaldev@mbp api % claudeLock the notes that matterLocking encrypts a note's body on disk behind a passphrase. Agents never see it, sync services carry ciphertext, and reading it requires an unlock.The title, frontmatter, and tags stay visible, so links and navigation keep working.Search and backlinks skip locked bodies and say how many notes they skipped.One passphrase covers every locked note. ⌘L relocks, and the vault relocks itself after 15 minutes idle.Images pasted into a locked note are sealed with it.A locked note is self-contained. On another machine it unlocks with the passphrase alone. There is no recovery.Docs: Note LockingComp review 2026This note is locked. Its body stays sealed on disk, away from agents and search, until you unlock.Unlock Notes…Terminaldev@mbp notes % ledge cat "Comp review 2026"Sync with anything, share with gitNotes are plain files in ordinary folders, so syncing them is syncing a folder: iCloud Drive, Dropbox, git, Syncthing, or whatever you already use. There is no database on the side.Ledge watches the folder and follows outside changes live, even in an open note.Push a workspace to a git remote and the people you work with clone it. Each clone attaches as an ordinary workspace, and a pull shows up in the sidebar with nothing to refresh.One note changed in two clones is a git conflict like any other. If a pull rewrites a note you have open, your version keeps the file and the other goes to the workspace trash.A Sync note in the workspace pulls, commits, and pushes with one ⌘↩.Profiles never enter the folder, locked notes travel as ciphertext, and the trash stays out of git.Docs: Keep Notes SyncedSyncThis workspace is a repo. One run commits and pushes every note in it.shgit add -A && git commit -m "notes $(date +%F)" || true git pull --rebase && git pushWays to use LedgeSix kinds of notes, each with the manual page that covers it.Data explorationsqlselect plan, count(*) from signups group by plan;Done41 ms plan | count ------+------- free | 1204 pro | 187pythonimport pandas as pd df = pd.read_csv("signups.csv") print(df["source"].mode()[0])Done610 msnewsletterDocs: Running CodeProject runbookcwd: ~/Projects/apienvFile: .envshdocker compose up -d db make migrateDone3.8 s ✔ Container api-db-1 Started migrated to 0043_signup_sourceDocs: Run a Project from a NoteIncident responseprofile: prod-readonlyredisINFO keyspaceDone12 ms# Keyspace db0:keys=4812339,expires=0,avg_ttl=0Docs: Profiles and SecretsLearning to coderuby%w[a b c].each_with_index do |s, i| puts "#{i}: #{s}" endDone88 ms0: a 1: b