openJiuwen Releases RSI-Native AgentOS: Enabling Agents to Add Features to Themselves via Layered Extension Points
openJiuwen has released an RSI-native AgentOS, shifting AI applications from "developer-friendly" to "RSI-friendly." The system provides extension entry points across three layers—Web client, Gateway, and Agent execution. Agents generate extension packages based on user descriptions, which are loaded into the event bus to take effect. This supports hot-swapping, version management, and fault rollback without modifying the application's original code.
When using WorkSwarm to handle tasks, can you simply tell the Agent about a new feature you want, letting it build and install it for a test? openJiuwen’s answer is yes, and this mechanism is called RSI-Native AgentOS. It provides a runtime environment for Recursive Self-Improvement (RSI), advancing the extension mechanism from "conveniently allowing developers to integrate new capabilities" to "enabling Agents to proactively improve themselves based on task feedback."
Architecturally, openJiuwen divides the system into three layers: the Web client handles the interface display and receives user operations; the Gateway handles request access and forwarding; and the Agent layer consists of the AgentServer managing sessions and the Harness organizing task execution and tool calls. Each of these three layers retains extension entry points. Following this architecture, extension capabilities are divided into five segments—the Client can add buttons, panels, and settings items; the Gateway can integrate authentication or adjust request routing; the AgentServer can handle sessions, messages, and server-side commands; Swarm can customize multi-Agent collaboration rules; and the Agent can adjust prompts, integrate tools, or sub-Agents.
These modifications are delivered via extension packages. The manifest.json within the package specifies the package ID, version, dependencies, and code entry point; when involving interfaces, it can also declare where components should be displayed, such as in the input area, sidebar, or settings page. During installation, the system reads and verifies the manifest, saving the extension package by its ID and version. During loading, the Gateway and AgentServer respectively select packages running under their own control, determine the versions and order, and register the processing functions from the extension code into their respective event buses. When a user clicks an interface button, the gateway receives a request, or the Agent begins assembling a prompt, the corresponding component emits an event, the event bus finds the matching processing function, and invokes it.