Agent 📂 Share™

The root folder

On the first share, the browser's folder picker opens. Choose the folder that should hold all your work folders, for example RTCode in your home folder. You pick it once: the browser remembers the root for every playground tab in the same browser profile.

• If the browser cannot remember it, the toast Root link is session-only in this tab. appears, and the root lasts only for that tab.
• Each share asks the browser for read and write access to the root. If the browser does not grant it, the share ends with the warning Root folder permission was not granted. The root stays linked.
• When the page loads, the playground checks the stored root. If the browser cannot validate it, the playground forgets it and says Stored root expired. Pick it again. If the browser cannot read the stored root at all, the message is Could not restore the cached root. A root that was deleted or moved can also make the next share fail, with a warning toast.
• To forget the root yourself, use Unlink Root.

The work folder

The work folder is named after the first route of the playground, Code.D[0] (see Code), or Unrouted when the playground has no route. It is created inside the root. Holding Alt while you share adds a random suffix.

• A route path that contains / creates nested folders. The work folder of a parent route therefore contains the work folders of the routes below it: with the routes example.com and example.com/docs, the second folder sits inside the first.
• All unrouted playgrounds use the same Unrouted folder. A second unrouted tab that shares at the same time meets the another-window prompt. Share it with Alt to give it its own folder.
• The name is fixed for the whole session. Editing the routes during a share does not move the folder, and a retry after a conflict reuses the same name, suffix included.
• The Share and Unshare tooltips show the tree, Root and ← Work. Before a root is stored they read ← (pick once) Root. While Alt is held, the Share tooltip shows the suffix.

Ways to start

The Agent section of the Code menu has up to four items: Pins (Ctrl+P / ⌘+P), Explore, Share and Unshare. Share shows only while no folder is shared. The other three show only while one is. The Code menu is the logo button at the far left; its tooltip reads File, and Alt+F opens it. Open the command palette with F1.

The keys also work outside the editor, but not while the output has focus: the output does not forward Alt+A or Ctrl+Alt+A. A key that runs a command still obeys its conditions, so Share does nothing while a folder is shared. Some palette labels contain characters that you cannot see or type easily: the labels of Share, Pins and Pins Stop end with an invisible filler character, and the two Share ← Folder labels spell Share with a Cyrillic а, so typing share does not find them. Type folder, enable or disable instead.

Modifier keys on the Share item

Click the Share item, or focus it and press Enter, with these modifiers. They combine.

Empty deletes files and folders recursively. Everything goes: AGENTS.md, CLAUDE.md, .agents/, .claude/, your own notes and nested route folders. A warning toast with a recycle icon says so. With File Sync on, the folder then counts as empty, so no Files differ dialog appears and the editor wins.

Capture opens the dialog of Capture: Window…, whose cancel button reads Skip. Skipping continues the share without a screenshot. Cancelling the browser's own picker does the same, after a danger toast with the browser's message. Without Region Capture there is no chooser: the browser's picker asks for a window directly. When a capture starts, the share writes 📸.png, and Unshare stops a capture that the share started.

On macOS the Capture and Delete modifier is the Control key (⌃), not ⌘. The keyboard path works: focus the item and press Ctrl+Enter.

What a share does

While it starts, a toast titled Agent 📂 Share™ · patent-pending · by Elefunc, Inc. lists what the share will maintain. It stays until startup ends. A share runs these steps:

1. It asks the browser for access to the stored root, or shows the folder picker.
2. With File Sync on, it compares existing files with the editor. The Files differ dialog appears here if they differ; see File Sync conflicts.
3. It creates or opens the work folder, and checks whether another window is sharing it.
4. It deletes stale swap files (*.crswap) at the top level of the work folder, and empties the folder when you used Shift.
5. It downloads the current agent guide and the Pin Use skill, and installs the skill under .agents/ and .claude/.
6. It restores the pins.
7. It writes the initial files in parallel: AGENTS.md and CLAUDE.md; 📄.html and the exported files; 📄.sel; an empty 📜.json; the pin files. It also deletes io.eval.js and io.eval.json.
8. It opens the console writer, starts or removes the screenshot, and starts watching the folder.

The files that the toast lists, grouped as the toast groups them:

Two files are not deleted at share start: o.eval.js and o.eval.json. A leftover o.eval.json from an earlier session can therefore be stale.

When startup ends, a success toast shows the Root → Work tree. If startup fails:

• Cancelling the folder picker shows Aborted.
• Cancel in the Files differ dialog ends the share silently.
• A File Sync error ends the share with a warning toast that shows its message. The root stays linked.
• Any other error, such as a failed download of the agent guide, shows a warning toast with the message. The root link may be forgotten as well, in which case the next share asks for the folder again.

Another window is already sharing

While a share is active, the work folder contains 📜.json.crswap. If that file exists when a share starts, another window, or a session that crashed, holds the console writer. The share then asks Another window is already sharing this route. Unshare it and try again? with two buttons:

Unshare & Retry

Asks the other playground windows in the same browser profile to unshare, waits 200 ms and retries. If the swap file is still there, it deletes it once and retries again. If that fails too, the toast Another window is sharing ends the attempt. This also clears a swap file that a crashed session left behind.

Cancel (focused by default)

Stops the share and shows the same toast.

Share with a screenshot

Share + 🔴 Output… shares and starts an Output capture in one step. It runs only while no folder is shared. There is no chooser, but the browser's own screen-share prompt still appears. An active Output capture is reused. If a different kind of capture is active, a toast says Capture is already active. Stop it before switching to Output capture. and the share continues without a screenshot. Where screen capture is missing, the message is Screen capture is not available in this browser.

To add an Output capture to a share that already runs, use 🔴 🖥️ Capture (output) (Ctrl+Alt+Shift+C / ⌘+⌥+⇧+C) or Pins + 🔴 Output…. Share + Output does nothing while a folder is shared.

Pins + 🔴 Output… is available while no Output capture runs. Without a share it shares with an Output capture. With a share it makes sure an Output capture runs. Then it starts picking pins. Pins shares first when needed, without a capture, and the same key stops pins. See Screen capture and Pins and comments.

Resume from what is on disk

1. Open the command palette with F1, type folder and choose ✨ Agent: 📂 Shаre ← Folder: Enable.
2. Press Alt+A / ⌥+A. The disk 📄.html, its exports and ⚙️.js (File Sync on) and the disk pins are loaded into the playground. No Files differ dialog appears, and Shift is ignored.
3. The flag resets on reload.

Unshare

Unshare (the menu item, or ✨ Agent: 🗂️ Unshare) ends the share and leaves its files in the folder. The item also takes modifiers:

With Ctrl+Shift, the folder is emptied first and then deleted. Delete removes the work folder recursively, child route folders included. It then walks up the route's parent folders: in each it removes operating-system junk files such as .DS_Store, Thumbs.db and Desktop.ini, and removes the folder if it is now empty.

An Unshare does this, in order:

1. Stops File Sync, eval processing and screenshot refreshes.
2. Restores the normal sync direction and stops watching the folder.
3. Stops the screen capture, only if this share started it. Stopping a capture also deletes the pin images, 📍.<N>.png.
4. Closes the console writer, which commits 📜.json.
5. Applies Empty or Delete, if you asked for it.
6. Removes the folder badge and tells the explorer that the share ended.
7. Closes Pins and clears the pins from memory. The 📍.<N>.json files stay in the folder unless you emptied or deleted it.
8. Lets the address bar update again.
9. Shows a neutral toast, Root ← Work, and focuses the editor.

Unlink Root

✨ Agent: 🗂️ Unlink Root is a palette command that shows while a root is stored. It unshares first if a share is active, and then deletes the stored root. A success toast, ← (unlinked) Root, shows the old root name struck through. The next share asks for a folder.

If the browser cannot forget the root, the toast says Could not forget the cached root. This tab still drops its root, but the stored root may come back when you reload. Other open tabs keep their in-memory root until they reload.

Indicators

Folder badge

An amber folder badge appears on the Playground menu button (Alt+J). Its tooltip shows Folder, the root's name and, below it, the work folder's name.

Tab icon

While you share, capture or pin, the tab icon shows a three-character code. The first character is the share, the second the capture, the third the pins. An example is AO3: sharing, Output capture, three pins.

Transfer toasts

While a share is active, every write or read of a shared file shows a toast with the file's name, except 📄.sel and the 📍 files. Writes to the folder are red with a down arrow. Reads into the playground are green with an up arrow. Writes during startup are silent.

When none of the three is active, the normal icon shows.

Sync direction

While a folder is shared, the playground pins the sync direction to Input → Output, and Input → Output sync is unaffected. Changes that the live output makes on its own are held back instead of being written into the input at once. The F6 badge shows on the logo button, and F6 still pulls the output into the source on demand. Held-back changes are retried after Unshare. See Live sync and reloads.