A file tree should answer “where does this scene belong?” Tabs should be classified as saved, changed, or unnecessary before they are closed. After a saved tab closes, use a stable scene ID to prove that you can return. A title such as “Confrontation” is readable but not unique; ACT2-SC-12.md is a dependable address.
This method suits a screenplay or audio drama with many short scenes, a cast sheet, and a prop list. It does not require cloud collaboration. It relies on local files whose roles can be understood from their paths.
Give every scene an address
The sample structure contains three acts and 18 scenes under chapters/. Act one uses ACT1-SC-01.md through ACT1-SC-06.md; act two ends at ACT2-SC-12.md; act three ends at ACT3-SC-18.md. Supporting material lives in refs/characters.md and refs/props.md.
This naming scheme carries three pieces of information: act, scene order, and file type. The heading inside a file can still be expressive. The filename remains stable enough to search when two scenes share the same heading.
Before leaving a scene, add a return note outside the prose, for example:
SC-12 — around line 38 — check the handoff of the key — save before closing
That note is more useful than keeping a dozen tabs open “just in case.”
Classify every tab before closing
Open only the current scene and the one or two references needed for the decision. A practical arrangement might be ACT2-SC-12.md, characters.md, and props.md. When the decision is complete, close the references and leave the scene open until its return note and save state are settled.
Use three explicit states:
| State | Evidence | Close decision | Record |
|---|---|---|---|
| Saved | The authoritative path and end marker read back correctly | May close | Scene ID and return point |
| Changed | The intended content has not been read back after saving | Do not close | Purpose and unresolved decision |
| Unnecessary | The diff was read and a reason to discard is recorded | Discard candidate only in a copy | Reason it is not needed |
“Probably saved” and “probably unnecessary” are not states. Treat uncertainty as changed and preserve a separate copy. This rule does not depend on an unobserved warning dialog.
Confirm return with the saved SC-12 tab
- Search the tree for
SC-12and openACT2-SC-12.md. - Read the authoritative path, the note near line 38, and the saved return marker; classify the tab as saved.
- Classify the cast and prop sheets the same way, and close only saved tabs.
- Search the tree for
SC-12again and reopenACT2-SC-12.md. - Pass the return check only when the scene ID, line-38 note, progress note, and saved marker agree.
The first opening proves only that the tree can reach the scene. The second opening proves that your return path works. Changed and unnecessary tabs are kept outside this saved-file test.
What the saved-file close and return established
In a dedicated local workspace, a tree containing 18 scene files plus the cast and prop sheets was listed. The cast sheet, prop sheet, and SC-12 were opened in that order, then closed as SC-12, prop sheet, and cast sheet. After the workspace itself was closed and opened, the three files were reopened in their original order. SC-12 was made active again, and one saved return marker was read back.
Rune Studio's current Mac documentation describes a file tree, tabs, unsaved indicators, confirmation before closing an unsaved tab, tab reordering, and movement between panes. It also allows the behavior of Cmd+W to be configured for closing a tab or a window. Those are documented capabilities, not observations of this article's unsaved state.
Do not make an unobserved warning a pass condition
The measured sequence used saved files. It did not observe the unsaved indicator, the close-confirmation dialog, or its save, discard, and cancel choices. Rune Studio documents those safeguards, but the saved-file close and return cannot prove how they appear in the installed interface. Visual tab colors were not inspected either.
Score the candidate in two layers. Return to saved SC-12 is an observed pass. Unsaved protection is documented but remains on hold because the indicator and decision dialog were not observed. While it is on hold, keep changed tabs open, save manually, and read back the content before moving them to saved. Do not make Cmd+W part of the safety rule because its action is configurable.
A workable script-editing routine
At the start of a session, open the scene by ID and only the references needed for it. At the end, record the next decision, settle the save state, close the tab, and make one return attempt. That habit tests the structure while the work is still fresh.
Rune Studio's saved-file return result and its documented unsaved safeguards can be evaluated separately. Product details are available on the Rune Studio website.
The useful outcome is not the maximum number of open tabs. It is a defensible state for each tab and the ability to recover saved context from SC-12, line 38, and the key handoff. This method does not claim an unobserved warning passed; it keeps changed work out of the close path until readback makes it saved.
For current details about the Mac file tree and tabs, visit the Rune Studio product page.