Skip to content

Working together

Every Member of a Project opens the same editor on the same Project. What one changes, the others see as it is changed.

Any Member can invite. On the Dashboard:

  1. Click the Project’s name on its card. The Project’s page opens.
  2. Under Members, type the person’s email address under Invite someone, and click Invite.
  3. Tell them yourself: no mail is sent. They sign in at https://app.shell-engine.com with the Google account of that address.

Until they have signed in, the address is listed as “Invited, has not signed in yet”. Take back removes the invitation; you can take back one you sent, and the Owner can take back any.

The Member who made a Project is its Owner.

WhoCan
Every MemberEdit, ask the Agent, and invite. All but the Owner can Leave
The Owner onlyRemove a Member, rename the Project, and delete it

Remove and Leave ask once more before they are done: click a second time to agree.

People in the Dashboard’s menu lists everyone you share a Project with, each once, with the Projects you share.

  • An invitation nobody has taken up yet is listed apart, with Take back.
  • Where a Project is yours, Remove takes the person out of it. If you share several of your Projects with them, choose which one first.

The other Members with the Project open are in the editor’s toolbar, each as initials in a colour of their own.

  • Hover over one to read their name and where they are: “in this document”, in another Document by its path, or “with no document open”.
  • Click one who is somewhere else to open the Document they are in.
  • The first of them is you. Click it to change your name as the others see it.

The scene or prefab you have open is your Document. In a Document you share with someone, their Presence shows:

  • in the Hierarchy, their face on each entity they have selected: their picture, or their initials in their colour. A row shows three faces, then “+1” or more for the rest; hover over a face to read whose it is;
  • in the Inspector, under the name of what you inspect, their face and “Ana is here too” when they have it selected too, or any of the entities you inspect: two names, then how many more (“Ana, Sam and 2 more are here too”); hover over the line for every name;
  • in the Scene view, what they have selected, with their name above it, and their pointer. When their pointer is over their scene view but outside yours, an arrow with their name waits at the edge of yours, pointing the way; press it (or Tab to it and press Enter) to centre your view on their pointer. Your zoom stays, and nothing is undone by it.

Say something by your pointer. With the pointer over the Scene view, press / and type: the others in the Document see your words by your pointer as you type, up to 100 characters. Enter keeps the line for 5 seconds; Esc, or moving the pointer off the Scene view, takes it away at once. A finished line is read out once to screen readers. Nothing of it is saved, and the Agent does not see it. In a text field, / is just a /.

During a Run the Agent is among the Members too, as Agent.

  • Changes arrive as they are made. There is no save step, and nothing is ever unsaved.
  • Two Members who change different fields of one entity both keep their change.
  • Undo takes back your own steps and no one else’s. A step on an entity someone has since removed is skipped, and the Console says so.
  • If the connection to the Project is lost, the editor freezes under a bar that says so: nothing can be changed until it is back. It notices within about ten seconds, also where nothing ended the connection, as when a laptop loses its network. When the connection answers again the editor takes changes again where you are, and the Console says “Connected again. Nothing was lost.”; where it cannot, the page loads again by itself. The bar says “The Project is starting again” while its Sandbox starts, and “You are not connected to the internet” where your browser has no network. If you changed something, or asked the Agent, in the moment before or while it was lost, the bar says that it may not have been kept: look for it when the page is back.
  • If the Project is closed to you while you have it open (an Admin suspended it, you were removed from it, or it was deleted), the editor goes by itself to a page that says so.

A script is a file, not shared the way a Document is. Each Member writes in a copy of their own until they save, with Mod+S in the Code panel.

  • A saved system is taken up on every Member’s page at once.
  • A saved component loads every Member’s page anew. During a Run, that waits for the Run’s end.
  • When two Members have changed one script, the second to save is told, and chooses Take theirs or Keep mine.

The Gamedoc is kept as it is written, a part at a time, and every Member’s page takes a change about a second later. When two Members have text in one part at the same moment, the second is told, and chooses Take theirs or Keep mine.

The Project in a folder on your computer, kept in step, with your own agent connected to the editor. Your own nvim, VS Code or other editor works on the folder. It needs Node 20 or later, and Google Chrome for your agent’s editor.

Your own agent needs no allowance: it is paid by you where you run it, and is not counted under Usage. The Dashboard’s Agent page has these steps too.

  1. In the editor’s toolbar, beside the Members, click Work on your computer, or choose File › Work on your computer….
  2. In a terminal, run the command of step 1 where the folder should go. For a branch’s folder, pick the branch beside it first: the command, and the folder’s name, <project>@<branch>, change with it.
  3. Click Make my token, and paste it when the command asks. The command makes a folder named after the Project, brings every file into it, and keeps it in step. Each save reaches every Member’s page in about a second, and what the others change comes down to the folder.
  4. Start your agent in the folder with the line of step 3. You do not need the editor’s tab open: while the command runs, your agent has its own editor, a windowless Chrome, and the others see it as your agent. You edit beside it in your own tab, with your own selection and undo.

The folder has, beside the Project’s files:

  • .mcp.json, which Claude Code reads: your agent reaches the editor’s tools from the folder with no claude mcp add. Claude Code asks once to use it. It holds no token.
  • AGENTS.md, what an agent needs to know there. It is the folder’s own and is not sent to the Project.
  • .shell/, with the token (readable by you alone), what was last in step, a copy of the command that .mcp.json starts, so your agent connects after the editor is updated, and offline, and the profile of your agent’s Chrome. None of it is sent to the Project.

A folder for a branch is called <project>@<branch>, and works on the branch. A branch that is not there is refused: make it in the editor’s branch menu first. Your agent cannot make branches.

  • The token is shown once, and not again after the dialog closes. There is one for each Member and Project: Make a new one ends the one before. Take it back ends the token, the folder’s sync and the agent’s connection.
  • The Project’s page on the Dashboard says Connected from a computer since the day the token was made, with Take it back: for a computer that is lost, without opening the editor.
  • When a file was changed in both places, yours is kept, the Project’s is written beside it as <name>.online, and nothing is sent. Take what you want from it and remove it: yours is then sent. An earlier version of the Shell app wrote one by mistake as it started, for a file changed on one side only: one that came so, with nothing changed online, can simply be removed.
  • A Project that is asleep is said to be; a save wakes it. Run the same command in the same place to bring the folder back in step after a while away.
  • One command at a time keeps a folder in step: run a second there while the first runs, and it says so and stops. Stop the first (Ctrl-C) and run it again.
  • node_modules holds the types of the Project’s packages, for your editor, and is not sent. Nor are names that start with a dot, and vim’s swap and backup files.
  • package.json, vite.config.ts, index.html, editor.html, CLAUDE.md and the tsconfig files can be read and not changed.
  • A symbolic link in the folder is not followed. It has not been tried on Windows.
  • A scene, prefab, settings file, clip, effect or tileset the editor saves ends with fileId: leave it as it is. A file moved in the folder with your own tools is still found by a value that carries its id (a picture or a sound only with its .meta file beside it); a value without one names the old place, and is listed under missing files in the editor while no file is there (Missing and moved files).

Play on the Project’s card opens the game alone, with no editor around it. It is at /play on the Project’s address, and can be sent as a link.

The link is for Members: whoever opens it has to be signed in and a Member of the Project. To show the game to someone else, invite them, or publish it.

The Owner can publish the game for people who are not Members. On the Project’s page, under Published game, click Publish.

  • The game is built from the Project as it was at its last Checkpoint. One is made before every Run, every few minutes while Members change things, and when the Project stops. What was changed after it is not in the game.
  • Building takes a minute or two. Then the page says Live, the game’s address, such as crate-game.shll.page, the revision the game was frozen at, when that was checkpointed, and when it was published.
  • The game plays on its own for anyone with its address: no editor, no sign-in, no password, and the Project’s machine does not start for it.
  • Later changes stay private until you click Publish again, which replaces the game at once. When a build fails, the game published before stays live, and the page shows why it failed.
  • Unpublish takes the game away: its address finds nothing.