Storyloom field notes
How to direct the work behind the outputs.
Five grounded guides drawn from Storyloom’s shipping canvas, model catalog, BYOK path, engine, and MCP server. No invented case studies and no generic AI trend posts.
5 articles
Notes from the working system.
Each article explains a real capability or trust boundary and links back to the relevant product surface or source.
Workflow
One brief, one board, a complete campaign
A practical way to turn a campaign brief into concepts, variants, and channel-ready assets without losing the visual idea that connects them.
Read the note
Models
Choose the model for the shot, not the whole project
A grounded approach to selecting image, video, audio, and 3D models inside a mixed-media workflow while keeping cost and iteration visible.
Read the note
Canvas
Keep creative versions in space, not in a dropdown
How an infinite canvas changes versioning by keeping branches, references, and selected work visible without pretending creative history is a linear list.
Read the note
Infrastructure
What bring your own key means in Storyloom
The actual credential path behind Storyloom's BYOK model, including browser storage, the server proxy, provider calls, and the trade-offs creators should know.
Read the note
Agents
Let an agent use the same actions as the studio
How Storyloom projects its typed creative action registry through MCP so an external agent can drive the same engine without a second automation stack.
Read the notePut the method on a canvas
The useful next step is a visible piece of work.
Open Storyloom without an account or a provider key. Add your own models when the direction is ready for production.