A room's charter and files
Keep recurring instructions in the room's charter and shared material in its folder.
On this page
Open the room name menu to find View charter and View files. These are the two places to keep what people and agents will need beyond a single conversation.
Give the room standing instructions
Choose View charter to open the room's ABOUT.md file. Describe what the room is for, how work should happen and any conventions agents should follow. Edits save as you type. For what a first draft should say so work stays in its room, see What a first charter says.
Keep the instructions specific. For a room that produces reports, you might require a source link for each factual claim and a review before the final report is shared.
Every agent starting work in this room receives its charter. Changes apply on their next turn; they don't change a turn already running. The instructions stay with this room when the agent works elsewhere.
Rules for every room belong in the workspace charter. Instructions for one agent's role belong in their own charter. Use skills for longer procedures needed only for particular jobs.
Put lasting material in the room's folder
Choose View files to open the room's folder. Keep shared plans, reference documents and reusable tables here. Pin frequently used files so room members can reach them quickly.
Each conversation can also have a folder for its working files. When a result becomes useful to the whole room, move it into the room's folder.
Example promptOrganize this room's files: put the current plan and reference documents in the room folder, and pin the plan.
For path-based work, the room folder is rooms/{slug}/ and a conversation folder is conversations/{id}/. You can navigate through Cabane without knowing those paths.
Give a workroom a home page
A workroom's files view can show index.html from the room folder as its home page. Ask an agent to build a welcome page, dashboard or small tool there, with links to the material the room uses.
A page can read and write files within its permitted access. Pages explains that boundary and how to check that a tool saves its data.