If you play music — gigging, recording, teaching, or just on a serious personal craft path — your notes situation is probably a familiar mess. Voice memos in three different apps. A practice notebook you fill once a year. Setlists in the Notes app, then printed out and lost backstage. Lyric drafts in Drive, in notebooks, on hotel stationery. Rehearsal recordings on a band member's phone you'll never get a copy of.
This guide is about putting the parts that matter — the practice log, the setlists, the lyrics, the rehearsal audio, the gig notes — into a single vault where you can actually find them later, and where an agent can do the boring middle work for you.
The actual job of a musician's notes
Notes for a musician aren't just records. They're the connective tissue between sessions. You learn a passage, you struggle with a section, you try a new tempo, you decide a setlist works one way and not another — and unless you write some of it down, you re-learn the same lessons next week.
The pattern that holds up over time has four pieces:
- A practice log that captures what you worked on and what you noticed, even briefly.
- A song archive with lyrics, chord charts, arrangement notes, and demos.
- Setlists per gig, with notes after the gig about what landed and what didn't.
- Recordings — practice takes, rehearsals, demos, gigs — that are searchable, not just stored.
Most apps do one of these well. A vault that does all four together, where the agent reads everything, is what makes the system pay off over months. The audio-heavy setup overlaps a lot with what we describe in AI notes for podcasters — same transcription pipeline, different artifact at the end.
Practice logs that don't feel like homework
The hard part about a practice log isn't writing one. It's writing it consistently. Every musician has tried to keep a notebook and watched it die after a week. The trick is making the entry small.
Open a "Practice" page in your vault. After a session — even a short one — type three lines: what you worked on, what you noticed, what you'd do next time. That's it. No metrics, no dashboard, no streaks. Just a dated entry.
Over a month, those entries become a real picture of your work. Ask the agent: "Read my last four weeks of practice logs. What patterns do you see in what I'm focusing on, and what have I been avoiding?" You'll find out you've been working on the same two passages for three weeks and never touched the third one you said you would. That's useful intelligence.
For specific pieces you're working up, a sub-page per piece with its own log works. "Bach C Major Prelude — practice notes" lives under "Pieces in progress" and accumulates over weeks. When you decide to revisit that piece next year, the page already has your annotations from this year.
Lyrics, chord charts, and the long-running song archive
Songs are the long-lived asset. A song you wrote in 2022 might come back into a setlist in 2027. A lyric you abandoned might become the bridge of something new. The archive needs to last.
Plain markdown is the right shape here. One page per song, with the lyrics, the chord chart, arrangement notes, and any demo audio embedded inline. No proprietary file format. No app you'll outgrow. The text is just text.
For lyric work, the agent helps with the kind of pass that's tedious to do by hand. "Pull every lyric I've written that mentions winter or cold weather." "Find every chorus across my song catalog that uses the word 'home.'" These are the questions that surface unintentional patterns — the recurring image, the overused metaphor, the angle you didn't realize you kept circling. Sometimes the find tells you to lean in. Sometimes it tells you to stop.
For chord charts, the formatting is whatever convention you use — Nashville numbers, lead-sheet style, chord-over-lyrics. Plain text means it renders the same way everywhere and the agent can read it. The plain-markdown shape is the same trade we make against block-based tools — see our Notion comparison for the reasoning if you're considering switching from a block editor.
Setlists: built fast, retired with notes
Setlist building is mostly assembly. You have a song catalog. You have a venue, an audience, a length, and a vibe in mind. You pick fifteen songs in an order that flows.
A setlist page in your vault is just a list of song titles, optionally with capo, key, and tempo annotations. The flow is the important part. After the gig, add a few lines at the bottom: what landed, what dragged, where you lost the room, where you got it back. Tag the page with the venue and date.
A few months later when you're prepping for a similar gig, ask the agent: "Pull every setlist from a coffeehouse-style gig in the last year. Show me which songs got positive notes and which ones I marked as flat." You build the next setlist informed by the actual record, not by guessing what worked.
For longer-term planning, an inline database of all your setlists works well. Embedded directly in a markdown page via the :::database::: directive. Columns for date, venue, length, and a status (logged / pending / cancelled). The whole gig history sits in one place you can query.
Rehearsal recordings and the agent that can read them
The single biggest win for a working musician with a notes vault is what happens when rehearsal audio becomes searchable.
Drop the rehearsal recording into a page. It transcribes with speaker labels — useful for a band practice where you want to remember who suggested which arrangement change. The transcript lives next to the audio, on the same page, in your vault.
Now next week when someone asks "what did we decide about the bridge?", you don't have to scrub through forty-five minutes of audio. You ask the agent: "Find every time we talked about the bridge in last week's rehearsal. Pull the relevant exchanges." You get the moments back, in plain text, with who said what.
Same pattern works for demo recording sessions. You play three takes of a song, the engineer suggests a phrasing change, you commit to trying it, and then six months later you have no memory of which take was the good one. With the audio in your vault and a few notes after each take, the take you wanted is findable.
Songwriting collaborators and the version question
Co-writing is a great way to lose track of who suggested what. Everyone shares files differently, drafts get emailed back and forth, and three weeks later the version everyone is referring to as "the latest" is actually different on each person's laptop.
A workable pattern when you're the keeper of the song: one page per song, with a "Versions" sub-page underneath. Each version is its own dated page with the lyric, chord chart, and notes about what changed and who suggested it. The agent can compare versions on demand: "What's different between Version 3 and Version 5 of 'Glass Hour'? Pull the lyric changes line by line." That's hard to answer fast in a folder of Word docs.
If your collaborator sends you a voice memo with a new bridge idea, drop the audio into the song's page. It transcribes, and the spoken bridge becomes searchable text alongside the rest of the song's history.
Teaching: keeping students straight
Music teachers face the same context-management problem as anyone with many small relationships. Twenty students, each with a different piece they're working on, a different practice issue you noticed last week, and a parent or partner who occasionally needs an update.
A "Students" sub-vault with a page per student is the same shape that works for classroom teachers — see AI notes for teachers for the parent guide. After each lesson, three lines: what you covered, what they're stuck on, what's next. Over a semester, the page is a real record of progress, and pulling it up before the next lesson takes ten seconds.
For studio policies, scales charts, exercises, and PDFs of repertoire — drop them in. Uploaded PDFs auto-convert to markdown via docstrange so the agent can search and quote from them. The Hanon book that's living as a PDF on your laptop becomes something you can ask: "Find me the exercise that builds independence between the third and fourth fingers."
A vault you stay in
A small habit that keeps the system useful: a five-minute prep before a gig and a five-minute debrief after. Before, open the setlist page, skim notes from past gigs at the same kind of venue, pull up lyric pages for the two songs you're least confident about. After, type three lines about how it went — what landed, what didn't, what you want to remember. Over a year, those debriefs become the most useful document in the vault. They're the only place where you've honestly recorded what actually works in front of an audience versus what you assumed would.
Music notes have a tendency to colonize every app you own and then become useless because they're scattered. The shape that works is one place — your vault — where the practice log, the songs, the setlists, the recordings, and the teaching notes all live together. Plain markdown so the agent is fast. Audio that becomes searchable text. Inline databases for the things that benefit from being tabular.
The agent doesn't replace the practice or the writing or the playing. It does the chores around them — finding the past take, pulling the recurring pattern, comparing the versions, drafting from the record. The kind of work you'd do on a quiet Sunday if you had one, except you don't, because Sunday is band practice.
Try Docapybara free — sign up, drop in your current setlist, the last rehearsal recording, and one piece you're learning, and ask the agent what it sees.