Coming soon

Three things are announced and not available yet: RTCode.ai, <ai-agent> and <fs-explorer>. This page collects what Elefunc has said about them in public, and how they relate to what you can use today. None of them can be used yet, and nothing here promises a feature or a date.

Note: Coming soon means announced and not available. Experimental means available and still changing. See Badges.

RTCode.ai

Coming soon RTCode.ai is Elefunc's upcoming AI services brand: agents that will help you in the playground and at the edge.

RTCode.ai is named as one of Elefunc's services in the scope of the company privacy policy. The playground announces it in its empty editor, with the line "✨ Need a hand? Let RTCode.ai help you out live!". No RTCode.ai feature exists in the playground today. The ✨ Agent commands belong to Agent Folder Share, which works with a coding agent that you run yourself.

RTCode.ai has its own Pins plugin, with the same capture options as pins in the playground.

<ai-agent>

Coming soon <ai-agent> is an Elefunc AI agent built as a web component, on web platform primitives.

elefunc.com lists <ai-agent>s among Elefunc's products. The Elefunc blog post File Systems Access for Web Agents says:

I am building <ai-agent> around web platform primitives, and filesystem access is one of the pieces it needs. I will cover that component and its integration in a separate post.

The element is not documented yet. <fs-explorer> is the file layer that it builds on.

<fs-explorer>

Coming soon <fs-explorer> is a file explorer web component. It gives several kinds of storage one file and directory handle interface, so a page or an agent can read and write them the same way. Its author describes it as "an early experimental component", and says that its code and examples describe the current deployed component, not a promise that every backend behaves identically.

The blog post names six sources that it can show:

SourceWhat it mounts
MemoryAn in-process tree.
OriginThe origin-private file system (OPFS).
DirectoryA folder that you pick with the browser's picker.
EdgeKVA remote store with eventual consistency.
ShareAn EdgeKV store that you see through a share grant.
ListingA read-only flat list from a hosted share URL.

The interface follows the File System Access API: the pickers showDirectoryPicker(), showOpenFilePicker() and showSaveFilePicker(), the standard handle methods, the permission methods and an observer built on FileSystemObserver. Sync access handles are not unified, and S3 and finer-grained permissions are described as future work.

<fs-explorer> is the filesystem layer for <ai-agent>. It is unrelated to Agent Folder Share, which uses the browser's native folder handles. The playground's own folder browser, opened by ✨ Agent: 📂 Explore… while a share is active, is a separate page that does not use <fs-explorer>.

How they fit in

NameWhat it isWhat you can use today
RTCode.aiElefunc's AI services: agents for the playground and the edge.Agent Folder Share, with the coding agent of your choice, and pins.
<ai-agent>An AI agent as a web component.The same: Agent Folder Share and pins.
<fs-explorer>The file layer for <ai-agent>.Agent Folder Share has its own folder browser. It does not use <fs-explorer>.

Agent Folder Share does not depend on any of the three. It works with Codex, Claude Code, or any agent that reads AGENTS.md or CLAUDE.md. Pairing with an AI agent shows how to start.

Badges

Coming soon Coming soon

Announced and not available. This page describes it only as an announcement.

Experimental Experimental

Available, documented and still changing. It may change or go away. These features carry the badge:

See also