·
5 min read
Everything You Can Do Here
Everything You Can Do Here
Fresh Jots has two note formats. You can use both, switch between them whenever, and they share the same 10-note free cap.
- **Rich text notes** — bold, italic, links, exported as PDF. Best for diaries, long-form writing, anything you want to *read* later. Browser-only — there's no API for rich notes.
- **Plain text notes** — simple, searchable, smaller. Browser *and* API. This is the format that everything in §3 and §4 below is built on.
You pick a default mode at signup ("Everyday" for rich, "Software development" for plain), but you can switch any time from Settings. The first time you pick Software development, you get a **14-day trial API key** so you can try the developer features without paying.
Sign up → 10 free notes
Write rich text notes (Everyday mode)
Write rich text notes (Everyday mode)
The daily diary, the half-finished essay, the recipe you'll come back to in six months. Bold, italic, links, hyperlinks, PDF export. Organize with folders and tags. Search across the whole account by full word or partial word — useful when you remember a phrase but not the title.
Every note is private by default. Flip the **Make public** toggle and the note gets a stable URL anyone can read; flip it back and the URL stops working. You stay in control.
Pin notes you reach for often. Auto-save runs every five seconds while you write, so nothing gets lost if your laptop dies or the tab crashes.
Quick-capture from the browser (extension, Free + Trial + Paid)
Quick-capture from the browser (extension, Free + Trial + Paid)
When an idea hits while you're scrolling, on a call, or watching a video, you don't want to open the app, navigate, click "New note." The Fresh Jots browser extension gives you one-click append from anywhere — Chrome, Firefox, Edge. The keyboard shortcut drops your text straight into a note.
Works on all tiers because your free trial API token unlocks it for the first 14 days.
Goodies for developers (API key required)
Goodies for developers (API key required)
If you are an IT developer that has a Fresh Jots API key, you can consume such work niceties as writing a Fresh Jots note:
- From any project you have, in any IT language, from any method;
- From your terminal;
- From a cron job;
- From inside your Claude Code session, to write or append a note to:
- Store everything you did before you did /clear, /compact, or closed the session;
- Store session summary;
- Store a work log;
- Store the description for your new PR;
- Store a to-do or a hint;
- Ask Claude Code to write anything to a new Fresh Jots note.
If you have a Fresh Jots API token, every plain-text note becomes a write endpoint you can hit from anywhere. One curl call:
curl -X POST https://freshjots.com/api/v1/notes/my-log/append \
-H "Authorization: Bearer $FJOTS_TOKEN" \
-d '{"text":"deploy ok — sha=abc123"}'
What you do with that is what makes Fresh Jots stick. Concrete uses developers have built:
- **Replace a third-party heartbeat service.** A scraper, a home server, a VPS, a backup script — append every few minutes from cron, set a dead-man deadline (§4), and you have Healthchecks.io / Cronitor for free.
- **CI failure log.** GitHub Actions / GitLab CI on-failure step curls the build summary into a per-repo note. Tag by repo. You have a searchable failure history with no log-aggregator subscription and no retention limit.
- **Deploy receipts.** After every green deploy, append the commit SHA, build duration, and actor. When you're bisecting a regression three weeks later, the timeline is right there.
- **Append-only audit log for unrelated scripts.** Backup, image-converter, batch job, scraper, scheduled cleanup — five different scripts, one note, one timeline. `grep ERROR my-log` replaces five dashboards.
- **Personal incident journal.** While debugging a prod issue, append timestamped lines from the terminal. Becomes the skeleton of the post-mortem; you don't reconstruct the timeline after the fact.
- **AI-agent persistent memory.** Claude Code, Cursor, Aider, your own scripts — read and write a note as cross-session context that survives `/clear`, lives outside any single workstation, and is reachable from any machine.
- **Read-only public status page.** Make a note public, append "OK / 200 / 134 ms" every minute from a check script. Free minimal status page at a known URL.
- **Code-snippet drawer.** A plain note titled `snippets`. Append from anywhere; pipe to fzf on the terminal to find that one-liner you wrote two months ago.
- **Daily-standup pre-writer.** Three bullets typed from your terminal into a dated note before the meeting. Searchable history of what you did, week over week.
- **Universal webhook sink.** Plenty of services emit webhooks but offer no "save this somewhere I can search later" destination. A token scoped to one note makes Fresh Jots that destination.
The pattern across all of these: **plain-text note + append endpoint + your existing scripts.** No new infrastructure.
Dead-man alerts (Pro + Team)
Dead-man alerts (Pro + Team)
You have a backup job that dumps your database at 3:55 AM. You don't check on it every day. You have a scraper. You have a side project with its own scheduled tasks. Each appends a line to a Fresh Jots note when it runs.
Instead of checking those notes every day for failures, set a **dead-man deadline**. Pick an interval — 1 hour, 6 hours, whatever fits the job's cadence. If the note doesn't receive an append within that window, you get an email. Once. The next successful append re-arms it automatically.
You only look when something needs attention. Everything else is silent.
The setup: open the note's **Settings** page, set "Hours without an append," save. That's it.
Get started
Get started
