Do you need to use all of Operon?

No. Operon has many surfaces, ways to make tasks, ways to see them, and ways to control and automate them, but none of them is required. Operon never forces you to use a feature. You can pick the small slice that fits how you work and leave the rest untouched, and it keeps working exactly as well.

This page is here to say that plainly, because the number of surfaces can look like a list of things you are supposed to do. It is not. It is a menu, not a checklist.

Operon does not push you into anything

Every part of Operon is opt-in. If you never open the Calendar, you never plan by date. If you never make a file task, every task stays a single line. If you never set a priority, tasks simply have no priority. Nothing nags you to fill a field or visit a view. The system map lays out everything that exists precisely so you can choose what to reach for, not so you feel you must reach for all of it.

The smallest useful Operon is one inline task and one Filter View. Many people never need much more than that.

Unused features add nothing to your notes

This is the quiet reassurance worth stating out loud: a feature you do not use writes nothing into your notes. Your tasks are plain Markdown, and they only carry the data you actually give them. Extra data appears when you use the things that add it, mainly when you set properties on a task or wire up parent and sub-task relationships. Skip those, and your task lines stay as short as you wrote them.

So using a small part of Operon keeps your notes small. There is no hidden bookkeeping accumulating in the background because a feature exists; the feature is simply idle until you choose it. And if you remove a field later, the values already in your files stay put rather than being scrubbed, so trying something is safe.

The defaults assume an average user, and you can dial them down

Out of the box, Operon is tuned for a fairly typical user: someone who uses both inline and file tasks and who tracks time. You can see this in what a task shows by default, where the metadata chips for priority, due date, assignees, duration, estimate, and tags are turned on. That is a sensible middle, but it is not a requirement, and it is not the only way Operon can look.

If that feels like too much, simplify what you see through the chip settings. The chips are display only, so turning them off changes nothing about your tasks; it only quiets the row. Switch off the duration and estimate chips and the time-tracking look disappears. Switch off more and a task narrows toward a plain line with just its words. You decide how much each task wears on its sleeve. See Task chips.

The same is true of the contextual menu, the action menu that appears on a task. Its actions are individually switchable, so you can pare it down to just the few you use, and if you turn them all off the menu simply stops appearing. Like the chips, this is a display choice; hiding an action does not remove the ability, only the button.

A few ways people use Operon

There is no single correct setup. Some real, valid shapes:

  • Just a to-do list. Inline tasks in your notes and one Filter View to gather them. No Calendar, no Kanban, no file tasks. Most chips off for a clean look.
  • Project notes only. Each project is a file task note with its own page, and you rarely write inline tasks at all.
  • A planner. You lean on the Calendar to place work on dates, and skip the Kanban entirely.
  • A board. You live in the Kanban, moving cards through stages, and never open the Calendar.
  • The full kit. Inline and file tasks, dates, recurrence, and time tracking, all on. This is what the defaults lean toward, and it is just as valid as the minimal end.

Any of these is a complete way to use Operon. You can also start at the minimal end and grow only when the work asks for it.

If you want Operon plain and quiet

A short recipe for the lightest setup:

  1. Use inline tasks and ignore file tasks until you want a task to have its own note.
  2. Build one Filter View for "what should I do," and leave the Calendar and Kanban closed.
  3. In chip settings, turn off the chips you do not care about, including duration and estimate if you do not track time.
  4. In contextual menu settings, keep only the actions you use, or turn them all off to hide the menu entirely.
  5. Set a property on a task only when you actually need it.

That is a real, fully working Operon, and it stays out of your way.

FAQ

Do I have to use the Calendar, Kanban, or time tracking? No. They are there if you want them and invisible if you do not.

Will unused features clutter my notes? No. A task only carries the data you give it. Features you skip write nothing.

Operon shows a lot on each task. Can I make it plainer? Yes. The chips are display only; turn them off in chip settings to strip a task back toward a plain line.

Can I start minimal and add more later? Yes, and that is the recommended path. Add a surface the day the work calls for it, not before.