xAgent 0.0.9.beta Is Available: Separate Administration, a Unified Session Workspace, and Session Prompts
xAgent 0.0.9.beta is now available. This release addresses a boundary that becomes increasingly important as a deployment grows: administering the system and using it for daily work should not share the same entry point and navigation.
The administration console now lives under /admin, while /app focuses on personal sessions, files, settings, and usage. Web and desktop also share one two-column session layout, and per-session prompts can be edited directly and applied from the next model turn.
Use /admin to Govern the System and /app to Work
Previously, an administrator signing into the user interface could see system governance and personal work in the same navigation. The capabilities were available, but the boundary made bookmarks, reverse proxies, and permission troubleshooting harder to reason about.
0.0.9.beta assigns a clear responsibility to each entry point:
/admin/loginand/adminhandle models, users, Agents, approval policies, Connectors, organization-wide statistics, and upgrades;/apphandles personal sessions, Workspace files, personal settings, and personal usage;- administrators opening
/appreceive the same personal workspace experience as regular users, without administration menus; - release notices and upgrade actions appear only in the administration console.
The interfaces do not link to each other. This does not remove administrator permissions; it keeps personal work and organization governance inside their own boundaries. Existing account roles and business data are unchanged.
One Session Workspace for Web and Desktop
The session page now has a consistent two-column structure. The left side contains xAgent branding, the main session, search, and recently active sub-sessions. The right side contains the active conversation.
The main session stays pinned above search instead of moving with search results or scroll position. Conversation content scales with the available space and remains centered, using the same reading baseline on standard and ultrawide displays. Empty-session guidance, messages, and the composer now align to the same content axis.
The toolbar no longer exposes the internal Session identifier. Advanced settings use an icon entry, while the file entry and Tool-call visibility control remain available. The sidebar footer shows the current user and opens personal settings and sign-out.
Per-Session Prompts Are Directly Editable
The prompt editor is visible even when the current session has no prompt yet. It opens by default, provides at least ten rows, and expands into the remaining drawer height. Long prompts scroll inside the editor instead of pushing the actual configuration out of view.
A saved prompt applies from the next model turn. Main sessions, Connector sessions, and regular sub-sessions retain their existing role and apply the session-level override on top of that baseline. The change affects only the current session; it does not rewrite the system Agent or other sessions.
Configuration drawers also stay open after an accidental backdrop click, reducing loss of unsaved work. Read-only information drawers may still close from the backdrop.
Personal Usage Stays Personal
The former user dashboard is now Usage Statistics. It shows only the current user's Token, model-call, and Tool-call data, with model details visible by default.
Global and per-user reports remain in the administration console. The same boundary applies throughout the release: users see the state of their own work, while administrators govern organization-wide operation and cost.
What to Update Before Upgrading
Reverse-proxy rules, browser bookmarks, and operational scripts that still use /app/admin/... must move to /admin/...; the administration login page is /admin/login. /app now opens the user session workspace directly, and personal usage statistics are available at /app/dashboard.
The upgrade does not change existing account roles or business data. Before upgrading, back up xAgent configuration, the database, user workspaces, Memory, Skills, Tool packages, and Connector state.
See Start Installation for installation and upgrade steps, and the Changelog for the release summary.