If you've been working on a screenplay, a memoir, or some other long creative thing on the side of a real job, the hardest part isn't the writing. It's that the project lives in fifteen places. A folder of voice memos. A Google Doc with the latest scene draft. A Notes.app dump from when you were on a walk. A printed PDF of someone else's script you were studying. Maybe a Scrivener file you opened twice in 2024.
The work you actually want to do — the writing — keeps getting interrupted by reassembly. You spend the first twenty minutes of every session just remembering where things were. This guide is about putting an end to that.
What a creative-project workspace actually needs
Forget software-feature lists for a minute. A creative project that runs for months or years needs four things from its workspace, and most apps deliver one or two:
- Somewhere everything lives. Not "everything important" — everything. The throwaway voice memo with the phrase that became Act 2's whole spine. The article you read in line at the coffee place. The half-finished scene you wrote on your phone. If a thought has to be promoted into the system to count, half the thoughts won't make it.
- An easy way to ask "where did I write that thing about…" without browsing. Folders are fine; a search that understands what you meant is better.
- A way to act on the material, not just read it. "Pull the three strongest one-liners from my current memoir draft." "List every scene in my screenplay where the antagonist appears." That kind of pass is the boring middle-distance work that drains a session.
- A shape that doesn't punish revision. Creative work gets restructured constantly. Tools that lock you into outlines, indexes, or rigid block trees fight you the day you decide Chapter 4 was actually three different essays.
We built Docapybara around the same shape: one vault, plain markdown notes, an agent that reads everything in it, no plugin assembly. The rest of this guide walks through how that maps to the specific shape of a screenplay, a memoir, or a long side project. If you came in from the Obsidian comparison, this is the integrated-agent answer to the plugin-assembly problem on a creative vault.
Screenplays: scenes, beats, and the version that got worse
Screenplays have a unique problem. You write a draft. You give it to a friend. You write a second draft incorporating their notes. Halfway through, you realize the second draft is worse. Now you have two versions, three pages of friend notes, your own marginalia from the rewrite, and a vague sense that something good in the first draft got cut.
A workspace built around plain text helps here because every draft sits next to the last, and the agent can compare them on demand. Drop both versions into pages. Drop the friend's notes in. Ask: "What did Draft 1 do in the diner scene that Draft 2 doesn't? Pull the lines that disappeared." You get back a side-by-side of the cuts, and you decide which to put back.
For the structural side — beat sheets, scene breakdowns, character arcs — an inline database inside a markdown page works well. One row per scene, columns for location, characters present, beat type, page number, status. The database lives inside the same page as your prose, not in a separate tool you have to remember to open. When something changes — a scene moves, a character gets cut — you update one row instead of three documents.
The big agent move on a screenplay-in-progress: "Read every scene where the antagonist appears. List what they want in each scene, in one sentence." That kind of pattern-finding is what turns a messy draft into a tighter one, and it's also the kind of pass nobody actually does on their own time because it's tedious. The agent doesn't mind tedious.
Memoir and personal essays: the part where you forgot what you already wrote
Memoir has the opposite problem from screenplay. You don't have too many drafts; you have too many fragments. A diary from 2019. A long email you sent your sister that turned out to be the heart of an essay. A Notes.app entry from a flight where you finally figured out the chapter about your dad. A folder of half-finished things you can't remember the title of.
Drop all of it into your vault. The agent doesn't care whether it was written as an email, a note, a journal entry, or a draft. It reads markdown. Once it's all in, you can ask the questions you couldn't ask before: "What have I already written about that summer?" "Pull every passage where I mention my grandmother." "Find the three pieces I've started that mention the move."
For uploaded PDFs — old letters scanned in, a printed program from a funeral, a clipping from a magazine — they get auto-converted to markdown via docstrange when you upload, so the agent can read them as text instead of treating them as opaque files. The thing your aunt wrote about the family farm in 2003 is now part of the same searchable pool as your modern fragments.
The work that feels precious — the actual writing — stays yours. The work that feels like archaeology — finding what you already have — stops being yours.
Side projects: the half-built album, the unfinished game, the would-be book
Side projects fail at the seam between thinking and shipping. You have great ideas. You have research. You have plans. What you don't have is a reliable way to surface what you committed to last month when you sit down on a Saturday and try to remember what the next thing to do was. The "current state" page habit overlaps with the cadence we describe in how to build a content calendar from your notes.
A practical setup for any long side project, in three pieces:
- A "current state" page that you update once a week. What's done, what's blocked, what's next. The agent can write a draft of this for you by reading your other notes — "Read everything I've written about the album in the last month, give me a status summary." You edit, save, done.
- An inline database for the specific units of the project — songs, levels, chapters, episodes. Status, last-touched date, blockers, file links. Lives inside a page so it's one click away from your notes, not in a separate tool.
- A loose page per work session — what you did, what you noticed, what you'd want to revisit. These are the breadcrumbs you'll thank yourself for when you come back after three weeks away and have no idea where the thread was.
Unlimited page nesting matters here because creative side projects branch in ways you can't predict. The album might want one section per song, with sub-pages for each lyric draft, demo recording, and feedback note. The book might want a folder per chapter, then a sub-folder for research, then sub-pages for each interview. There's no depth limit to fight against.
When your audio matters: voice memos, demos, and the agent that can read them
Creative work picks up a lot of audio. Voice memos with ideas you'll forget by Tuesday. Recorded conversations with collaborators. A first pass at a song demo. Interview recordings for a memoir or article.
The pattern that works: drop the audio into a page. It transcribes with speaker labels — useful for a co-writer call where you need to remember who suggested which change, or an interview where you'll want quotes. The transcript lives next to whatever else is on that page, so when you later ask the agent "what did I think about the bridge in that demo session?" it reads the transcript along with your notes. If your project leans heavily on audio — songwriting, podcasting, demos — see AI notes for musicians and AI notes for podcasters for the shape that holds when audio is the medium.
Audio stops being a separate, never-revisited folder. It becomes part of the same searchable pool as your written work.
Letting the agent do the boring 70%
The thing nobody warns you about with creative side projects: most of the work isn't creative. It's continuity-checking, restructuring, indexing, and reading-your-own-notes. That's what the agent is for. A few requests that work well on a long project:
- "Read my last three writing sessions. Give me a one-paragraph summary of where the story is and what's open."
- "List every character introduced so far, with one line on what we know about them and the page they first appear."
- "Find every scene that mentions weather. I think I'm overusing it."
- "I changed the protagonist's name from Mara to Annika in Chapter 3. Update the rest of the manuscript."
The agent doesn't replace the writing. It does the chores around the writing — the kind of pass you'd do on a productive Sunday afternoon if you had one, but you don't, because Sunday is the only day you can actually write.
The shape that quietly works
The reason a single vault outperforms a stack of tools, for creative work specifically, is that creative thinking is associative. The thing that unlocks Chapter 7 is often a fragment you wrote two years ago about something that seemed unrelated. If those fragments are scattered across four apps, the connection never happens. If they're in one searchable place where you can ask the agent "what have I written that touches on memory and place?", the connection finds you.
That's the whole pitch. One vault. Plain markdown so the agent is fast. Audio and PDFs both readable as text. Inline databases for the structural pieces. No plugin store to assemble.
Try Docapybara free — sign up and drop in the most recent draft, last month's voice memos, and one PDF you've been meaning to read. Ask the agent what it sees.