xAgent 0.0.7.beta Is Available: File Storage, Team Sharing, and Desktop Client

xAgent 0.0.7.beta is now available. This release makes a substantial upgrade to file storage and team collaboration, introduces the first Desktop Client release at 0.0.1, and continues to improve model caching, Provider compatibility, and image recognition.

This is still a beta release. The sections below summarize the main changes and do not replace the formal installation and upgrade instructions.

File Storage: From Local Files to S3

xAgent now provides unified Local and S3 file storage Providers. Administrators can configure AWS S3 or an S3-compatible object store, including its endpoint, region, bucket, prefix, path-style addressing, and credential mode. Connectivity and read/write checks can be run before activation.

Files can be migrated between Local and S3 storage. Static S3 credentials are encrypted through KMS, while configuration revisions and migration progress are retained. If migration fails, the active storage Provider is left unchanged.

During S3 operation, xAgent uses a local read cache and validates content size and SHA-256 integrity. If the remote store becomes temporarily unavailable, xAgent can fall back to local storage, upload content created during the outage after recovery, and switch back to S3.

Unified File ACLs and Team Sharing

This release unifies file ACLs across the workspace, upload, and share virtual roots. The new instance-wide share directory lets administrators create directories and manage shared content through upload, move, rename, download, and delete operations.

Shared directories support inherited read-only R and read-write RW grants for users and groups. Session tools enforce the merged user and session ACL, so the console, Agents, and Tools use the same readable and writable boundaries.

Existing workspace access configuration and legacy shared-directory layouts are migrated during startup or first access.

Image Recognition and OCR Agent

The release adds a configurable OCR model role. Administrators can select a vision-capable model and manage OCR-specific model policy.

When text is needed from an image attachment, xAgent can create canonical Markdown containing visible text, necessary visual description, and the primary language. OCR output uses a fixed structured contract; missing models, models without vision support, and invalid responses do not produce incomplete results.

OCR in this release applies to image attachments. Scanned PDFs without a text layer remain unsupported.

Model Context and Caching

The context and selected memory at the start of a user turn are now fixed against the real user message. Runtime state from a tool loop is appended to the request tail, reducing cache invalidation caused by repeatedly rewriting stable prompt content during one turn.

Session execution context now uses the unified file ACL projection, so models and tools receive the same readable and writable boundaries. Cached-token reporting is also normalized across OpenAI, Anthropic, and Gemini, distinguishing an omitted cache field from an explicitly reported zero.

Desktop Client 0.0.1

The first xAgent Desktop Client release provides packages for macOS Apple Silicon and Windows AMD64. At startup, the Client reads the public release catalog; when a newer package is available for the current platform, an update icon with a red indicator appears in the lower-left navigation.

After confirmation, the Client downloads the matching package, verifies SHA-256, exits, replaces the installation, and restarts automatically. If replacement fails, it retains the previous installation and attempts to restart it.

Session UI and Stability

This release fixes Session Timeline handling for legacy string messages and thinking-block attention state, restoring the production build gate for WebUI and Desktop. It also adds administration UI and localized copy for shared files, storage runtime status, and S3 migration progress.

Preparing to Upgrade

Back up configuration, database, workspaces, shared files, and Connector state before upgrading. Before enabling S3, save and test the configuration, then start Provider migration; the current Provider remains active until migration succeeds.

See Start Installation and the Changelog for installation and upgrade steps.