GIVE THE SCENE ROOM
Paste a passage that goes by too fast. It opens as a chapter in Muses, and what the AI adds to slow it down arrives as suggestions you accept or reject.
Three steps with a sample story: a short passage expanded in place, one moment slowed down on request, and a line of summary written out as a scene. The buttons work, so accept and reject the suggestions yourself.
Chapter to Expand
Sefa and Jun reached the gorge at dusk. The rope bridge was old, and some boards were gone.
Sefa and Jun reached the gorge at dusk, with a little light left on the far wall and none at the bottom. The rope bridge was old. Its hand ropes had worn gray and soft, and some boards were gone, so that in places there was only rope and the air under it.
Sefa went first. Halfway over, a board broke and she almost fell, but they both got across.
Sefa went first, because she was the lighter of the two. Halfway over, a board broke under her left foot.
She never heard it go. Her leg went through to the hip, and the rope burned across both palms. The river turned slowly under her, a long way down.
“Don’t look at it,” Jun said behind her. “Look at the far side.” She got her knee back onto wood. They were both across before the light went, and neither of them spoke until the fire was lit.
Expand this chapter in place, paragraph by paragraph, so I can compare. It moves too fast: slow the key moments down with detail and dialogue, and add paragraphs where a moment is skipped. Keep what happens, the names, the tense, the point of view and my voice. No need to ask first.
Chapter to Expand
Sefa and Jun reached the gorge at dusk, with a little light left on the far wall and none at the bottom. The rope bridge was old. Its hand ropes had worn gray and soft, and some boards were gone, so that in places there was only rope and the air under it.
Sefa went first, because she was the lighter of the two. Halfway over, a board broke under her left foot.
She never heard it go. Her leg went through to the hip, and the rope burned across both palms. The river turned slowly under her, a long way down.
She never heard it go. Her leg went through to the hip, and the rope burned across both palms. The river turned slowly under her, a long way down, brown and wide. A whole tree was riding it, roots and all. One of her sandals was already in the water.
“Don’t look at it,” Jun said behind her. “Look at the far side.” She got her knee back onto wood. They were both across before the light went, and neither of them spoke until the fire was lit.
Stay with her while she’s hanging there. What does she see when she looks down?
I added what’s under her: the river, a tree, her sandal.
Chapter to Expand
Sefa and Jun reached the gorge at dusk, with a little light left on the far wall and none at the bottom. The rope bridge was old. Its hand ropes had worn gray and soft, and some boards were gone, so that in places there was only rope and the air under it.
Sefa went first, because she was the lighter of the two. Halfway over, a board broke under her left foot.
She never heard it go. Her leg went through to the hip, and the rope burned across both palms. The river turned slowly under her, a long way down, brown and wide. A whole tree was riding it, roots and all. One of her sandals was already in the water.
“Don’t look at it,” Jun said behind her. “Look at the far side.” She got her knee back onto wood. They were both across before the light went, and neither of them spoke until the fire was lit.
Jun fed the fire one stick at a time, the way he did when he had something to say and no wish to say it. Sefa turned her hands over in the light. The rope had taken the skin off both palms.
“There’s no map,” he said at last. “There was. I traded it in Orrin for the dog.” She looked at the dog. The dog looked at the fire.
Next: that night Jun admits he traded their map for the dog back in Orrin. Write it out at the end of this chapter.
Two new paragraphs at the end. Jun takes his time getting to it.
This story was made up for the demo, and the screens follow the current Muses editor. Send the AI the same request twice and you’ll get different wording each time.
Whatever the AI adds, your own paragraphs stay as they are until you decide. Accept a suggestion and it becomes part of the chapter. Reject it and nothing in your chapter changes.
Say what deserves the space, as briefly as you like: “more on the fall,” “let them argue longer,” “nothing more about the weather.” What the AI adds next arrives as suggestions too. Once a round is decided, what you accepted is ordinary text in your chapter, so trim it or rework it like anything else you wrote.
The word count at the bottom of the editor counts a suggestion once you accept it. Kept too much? Once a round’s last suggestion is decided, an Undo button shows for a few seconds. Click it and the chapter is back as it was before that round. Later, Version History holds an “AI edit” for each round of suggestions you accepted, and “Show auto versions” adds the chapter’s earlier saves to the list.
Put the passage that moves too fast in the box at the top of this page, and sign in or create an account when asked. Muses starts a new story project with your passage as its chapter, and the chat next to it opens with a request to expand it: slow the key moments down with detail and dialogue, and add paragraphs where a moment is skipped. What the AI adds shows up in the chapter as suggestions. Accept or reject each one, then tell it what you’d like next.
Yes, you need a Muses account to see what the AI adds. After you submit your passage, the next screen asks you to sign in or create one. Expansions draw on a monthly AI allowance: the free plan includes one, and paid plans include a larger one. The Pricing page shows what comes with each plan.
Your story changes only where you accept a suggestion. The request that starts your chat asks the AI to add detail and dialogue while keeping what happens, the names, the tense, the point of view and your voice. Hold each addition up against your own lines, accept the ones that sound like you and reject the ones that don’t. To fence something off, say so: “don’t touch the last line,” “no new characters.”
That’s up to you. The opening request asks the AI to slow the key moments down and to fill in the moments that were skipped, and it leaves the length open. From there, tell the AI how far to go: “only a little longer,” “much more on the crossing,” “stop at the fire.” Each round arrives as suggestions, so the chapter grows only by what you accept.
Reject it, and nothing in your chapter changes. Or say what’s off, like “too much scenery” or “she wouldn’t stop to think here,” and ask the AI to try again. If an addition is close, accept it, and once you’ve decided the rest, cut it down yourself. From then on it’s your text, the same as the rest.
Yes. Ask in the chat, in whatever words come to you: “more of the kitchen before anyone speaks,” “let the argument run longer,” “what is she thinking when the board breaks?” To single out one spot, select it in the chapter first, and it goes to the AI along with your next message. What the AI adds arrives as suggestions, the same as before.
Yes. Paste a few lines of what happens. They become the chapter, and the opening request asks the AI to expand it with detail and dialogue. Or, once you’re in the chapter, say what happens next in a sentence or two and ask the AI to write it out at the end of the chapter. Added to a chapter you’ve already started, the new paragraphs arrive as suggestions, so you keep the parts that match what you had in mind.
A paragraph or two, or a few lines of summary: enough to see what the AI adds and decide whether you like it. Each line you paste becomes its own paragraph, in plain text. Once you’re signed in, paste the rest of the scene straight into the chapter. To bring in earlier chapters, go to the Muses home page, hover over the project’s card, open the three-dot menu and pick Import into This Project. It reads DOCX, TXT and Markdown files, from a folder or a ZIP archive.
You do. Under Muses’ terms, you keep ownership of the content you create, and AI-generated content belongs to you. Muses does not use your content or your conversations to train AI models. The Muses team may review conversations with the AI to improve the product. You can turn off “Allow conversation review” in your Profile at any time.
Paste it into the box at the top of the page and sign in. Your passage stays as you wrote it until you decide, and the story grows only by the suggestions you accept.
Make my story longer