StablEdge Desktop · Public version 0.3.7.2 · Internal build 0.3.8
Core capabilities
Layered System Prompt governance: Chat, Agent, Complex and Subagent can each add their own prompt. The base comes from "enterprise AgentBackend > system default", and what you write is appended rather than replacing it, so the built-in tool discipline always applies and later updates to the enterprise template still arrive. The local security core cannot be overridden.
Plugin creation mode: One button at the top of Abilities → Plugins takes you there. The Agent creates the plugin folder and source files for you: it follows the built-in plugin authoring guide to write plugin.json and payload/, then uses the host's packaging to validate, seal the hash and sign locally, and the sources can live in any ordinary folder. You still confirm each permission on the permissions page to install. The mode adds hot preview, a development install and read/write access to installed plugins, and every grant is withdrawn when you leave it.
External Agent channels: A single Channel Gateway connects Lark, DingTalk, Telegram and WeChat, with conversation binding, pairing and allowlists, group chat policy, idempotent deduplication and graceful fallback when a platform lacks a feature.
Organization and member usage limits: Usage limits come from the server with separate organization and member policies, and usage pre-checks, server-side metering and over-limit notices work the same way for both.
Tasks inside the chat workspace: The task canvas can sit beside chat, files, the editor and plugin workspaces, while scheduling and run history stay separate, and the Agent can act only on tasks bound to the chat.
A unified node system for Tasks: Task nodes now share one model for NodeSpec, the Palette, ports, schema, timeout, cancellation, retries, artifacts and run records. Plugins cannot inject node types or editor UI.
Project memory and conversation lookup: Project memory becomes structured entries you can search, cite, update and forget, and the Agent can look up global and cross-project past conversations within its permissions, without reading system prompts, tool results or hidden threads.
A more open plugin system
Unsigned plugins officially supported: Before installing, the source, permissions and network declarations are shown, and the installing user and device are recorded.
Permissions granted per manifest: Workspaces and the top bar can declare network targets, and every request still goes through the host's controlled proxy.
Plugin identity context: A surface's ready() and the worker call context can read the current host user identifier.
Expanded runtime capabilities: User-approved trusted workers are supported, and the quotas for Bridge, top bar and worker calls are higher.
Better authoring and packaging: Plugin sources can be packaged from any folder you authorize, and the Topbar and Host Bridge guidance is complete.
Security and compatibility
The manifest schema, sealed file list, SHA-256 checks, path traversal protection and install confirmation all stay.
Signed plugins still verify publisher continuity; user attribution is not treated as cryptographic proof of origin.
Iframes still cannot reach the network directly; all network access passes the host's checks on domain, port, method, timeout and size.