A dark mossy hollow deep inside old-growth rainforest, mist pooling between huge trunks with faint warm light filtering from far above.

How it works

A lecture goes in. A filed markdown note comes out.

What happens in between, where the file lands, and the things this app deliberately refuses to do.

Where the notes go

You pick the vault and the two folder names. The course folder itself comes from detection, and is created if it is not there yet.

MyVault/
  00 - Courses/
    CS 314H/
      Lectures/
        2026-09-02 — Binary Search Tree Deletion.md
        2026-09-04 — Red-Black Trees.md
    M 340L/
      Lectures/
        2026-09-02 — Alternating Series Test.md
    _Unsorted/
      Lectures/
        2026-09-04 — Course Administration.md

That last one is what a lecture looks like when detection was not sure. It carries a warning at the top of the note and the guess in the frontmatter. Detection runs again at the end of the lecture, and if the answer changes the note moves itself rather than leaving a duplicate behind.

What it does not do

It is not sandboxed, and it is not on the App Store. It spawns the claude binary and writes into a vault that lives wherever you keep it, and neither of those is possible inside an App Sandbox container. That rules out the Mac App Store on its own, notarization aside.

It will spend your subscription. Three kinds of pass per lecture, and a long lecture is a lot of transcript. Settings has the knobs.

It will not guess a course. Covered above, and worth repeating, because the failure mode it avoids is the expensive one.

The notes are a study aid, not a record. They are generated from speech recognition output and they can misattribute or drop things. Check anything that matters against the lecture itself, and do not hand them in as your own work.

Check your institution's policy before you record a lecture. Plenty require explicit permission and some prohibit it outright, and consent rules differ by jurisdiction. That part is on you, not on the tool.