Make it yours
Rooms of your own
One folder, one room.json, one page — and it sits as a tab beside your chat.
A room is a panel beside the chat — a board, a counter, a page for your own job. It is a folder holding room.json and index.html, and it appears as a tile on the workbench start page and opens as a tab like any file.
What room.json needs
{
"api": 1,
"kind": "desk-room",
"contract": 1,
"id": "board",
"name": "Work board",
"doors": ["assistant", "code"],
"entry": "index.html"
}- Required
api: 1·kind: "desk-room"·contract: 1·id(the folder name, lowercase, 2–32 characters, never starting withbuiltin-) ·name·doors(assistantorcode) ·entry- Optional
descriptionusestoolsnetworkversioniconhue- Limits
- 8 MB in total · 200 files · 2 MB a file · 24 rooms on one machine · no symlinks
Getting one in
- Put a correct folder in
%APPDATA%\Aetox\desk-rooms\<id>\— that folder is scanned every time the list is drawn - Or let an agent write into
%APPDATA%\Aetox\desk-room-drafts\<id>\and open the workbench panel once — a draft that opens is moved intodesk-roomsby itself - A
room.jsonthat does not pass shows as a dashed card with the reason and a button that hands it to an agent to fix
How far a room can reach
A room's page is locked down by CSP: no network, no localStorage. It talks to the app through the room contract and nothing else — which is what makes every room you load a page you can read, not a program calling something behind your back.
Deleting a room deletes its folder, and any tools it brought are switched off rather than removed.