Every feature announcement carries the same quiet promise: this is strictly additive. More capability, no cost, nothing to lose by turning it on. It's a comfortable story, and for the person who shipped the feature it's even mostly true.
For you it usually isn't. Every feature you adopt before you need it is a tab in your attention, a habit half-formed, a thing you now feel vaguely guilty for not using "properly." A tool with thirty capabilities isn't thirty times as useful as one with two — it's two useful capabilities wrapped in twenty-eight invitations to fiddle. The skill isn't adopting everything on offer. It's knowing which features to ignore until a specific trigger flips them from distraction to leverage.
Below are seven JustJot features worth ignoring — each one steelmanned first, because none of them are bad, then handed a precise trigger. Until that trigger fires, leaving the feature alone isn't laziness. It's focus.
1. Agent runs
The pitch is the most exciting on the whole surface, and it's not hype: describe a multi-step task and an agent plans and executes a sequence of operations — search, draft, classify, summarize — with an auditable step log. When the work genuinely is multi-step and mechanical, nothing else comes close.
But that "when" is doing enormous work. Most of what you do in a notes app is a single move: capture this, find that, ask one question. Reaching for an agent to do a one-step job means you now write a careful task description, watch it plan, and review a step log — to accomplish what a single search would have. Ignore it until you catch yourself doing the same tedious chain by hand for the third time ("find every note tagged Q3, pull the open questions, draft a summary"). That repetition is the trigger. Automating a thing you do once is how you spend an hour saving a minute.
2. Natural-language custom feeds
The appeal is real: describe the feed you want in plain English and get a durable, named lens you can pin and return to. For someone drowning in a noisy follow list, one sentence buys real signal.
But a lens only helps when there's too much to look at. Building three saved feeds over a library of forty notes is curating a view of almost nothing — you spend the effort designing the filter and then watch it return the same handful of items the default already showed you. Ignore it until your home feed is genuinely too broad to skim and you've felt yourself scrolling past what you came for. Filters earn their keep against volume. Without the volume, they're just rearranged furniture.
3. Repurpose to every channel
Take one long note and emit channel-tuned variants — a thread, a LinkedIn post, a Threads version — each rewritten for the format. For something good you've already published, it multiplies reach without rewriting five times. Hard to argue with.
Except reach is a multiplier, and a multiplier on nothing is nothing. The failure mode here isn't wasted time, it's worse: it tempts you to optimize distribution before you have anything worth distributing, polishing the funnel for a piece that didn't deserve the first post. Ignore it until you've published something that actually landed — a piece people responded to. Then repurpose it. Spreading thin work across five channels doesn't five-times the work. It just exposes the same thinness to five more audiences.
4. Deep research reports
Ask a question and get back a planned, multi-section report with web search, fetched sources, and a numbered reference list — saved as an editable note. For a question bigger than a single search, it's a sourced first draft instead of ten blue links.
But most questions aren't bigger than a single search, and running the full research machine on a quick lookup is ceremony. You wait for sub-questions to plan and sources to fetch, then get a five-section essay where one verified sentence would have done. Ignore it until the question has genuinely moving parts — competing claims, several sub-questions, a need for citations you'll have to defend later. For "what's the formula for margin of safety," just ask. Save the cited report for the questions whose answers you'll be held to.
5. Flashcards and quizzes
Turn any note into derived flashcards and a quiz, pulled from your own material so they test what you captured. For something you need to retain, recall practice genuinely beats re-reading. The research on this is not subtle.
But the operative phrase is "need to retain," and most of what passes through a notes app is reference, not memory — things you want to find again, not recall on demand. Generating cards for a note you'll look up in two seconds anytime you need it is busywork dressed as studying. Ignore it until you hit material you must produce from memory without looking — for an exam, an interview, a language, a talk. For everything you can simply search later, searching later is the system. Manufacturing recall practice for facts you'll never need cold is effort spent looking productive.
6. Reactions
Lightweight emoji reactions on notes and posts. In a shared space — a team, a collaborator, an audience — they're real signal: fast, low-friction feedback about what landed without anyone writing a comment.
But signal needs a sender other than you. Reacting to your own private notes is talking to yourself with extra steps; the feature does nothing until a second person is in the room. Ignore it until you're actually sharing — collaborating on a space or publishing to people who can react back. In a solo library it's not a feature you're underusing. It's one that hasn't been switched on by the only thing that makes it work: someone else.
7. Reader mode for everything
/read wraps a long note in a focused reader — progress bar, table of contents, auto-resume where you left off. For the half-read long pieces quietly rotting in your library, the auto-resume alone removes the "where was I" tax that kills follow-through.
The word that makes it work, though, is long. Reader mode is built to defeat the friction of finishing big things; pointed at a four-line note it adds a chrome of progress bars and contents to something you'd have read in one glance. Ignore it for anything short. Reach for it when a note is long enough that you keep abandoning it partway. Matching a heavyweight reading surface to a lightweight note is solving a problem you don't have.
The two you shouldn't ignore
Here's the honest caveat, because a list that says "ignore everything" is just contrarianism for its own sake. Two capabilities are worth adopting on day one and never apply the rule above: capturing fast — the plain, boring habit of getting thoughts into the app with no friction — and asking your own sources, where you point a question at notes you've kept and get an answer cited back to the exact lines it came from. Those two are the floor. They pay off on the notes you have today, at any library size, for any use.
Everything else on this list is real, and every item flips from distraction to leverage the moment its trigger fires. The mistake isn't that these features exist. It's adopting them on the announcement instead of on the need. Master the two that always pay. Then let the rest wait until you can name the exact moment you reached for them — and keep that decision in JustJot, so the next time a shiny feature ships, you can ask your own notes which ones actually changed how you work.