AWR 0.3.3

0.3.3 adds a shared MCP service and persistent work-session continuity. One native awr-mcp process can serve multiple projects and clients through a single Streamable HTTP endpoint. The existing local stdio command remains supported.

npm install -g @originoneai/agent-work-runtime@0.3.3
# or, in a Python virtual environment
python -m pip install agent-work-runtime==0.3.3
awr --version
awr-mcp --version

Changes

• An operator-owned registry maps project keys to initialized project roots and identities. Each project keeps its authoritative sources and runtime database; clients share one service URL and select an authorized project on each call.
• Client credentials have explicit read/write project grants. Requests are authenticated, project identities are checked, and writes are coordinated per project with revision and source-fingerprint conflict detection.
• MCP tools now start, inspect, claim, checkpoint, end and resume work sessions. Persistent bindings distinguish project, authenticated client and host conversation. Network disconnects and service restarts do not end work sessions.
• Waiting for a user saves a checkpoint and a durable question. Replies and cancellations remain available for later continuation. Hosts retain control of user interaction, model execution, notifications and wakeup scheduling.
• Shared HTTP writes require stable request IDs. Repeated matching requests return recorded outcomes. Clients can inspect uncertain operations and recover a proven committed outcome without re-executing the original operation.
• Source reindexing is an explicit MCP operation; ordinary reads stay read-only. Stdio exposes 20 tools, and HTTP adds authorized project discovery for 21 tools.
• Package installation and assembly checks validate the complete stdio tool catalog, including missing or duplicate tool rejection.

Configure a shared service with the MCP service guide:

awr-mcp --registry /etc/awr/service.toml --listen 127.0.0.1:8080

Project files must be accessible on the server. The registry defines client bearer credentials through environment variables; remote deployments need HTTPS and an appropriate access boundary. The built-in authentication is static bearer access. Enterprise identity-provider integration and browser CORS preflight belong to the deployment gateway. AWR does not automatically install a system service.

Compatibility and upgrade

npm launchers require Node 22.14+; Python launchers require Python 3.9+. Keep npm optional dependencies enabled. Native executables run without either launcher runtime. Archives contain source identity, binary hashes, Apache-2.0 and dependency notices; the release manifest and SHA256SUMS bind the package files.

Database schema remains 4; upgrading from 0.3.2 needs no schema migration. Retain the original project root, authoritative sources, runtime history and previous executables. Stop active writers and keep a matching backup before switching a pinned program, following the upgrade and rollback procedure. The previous version does not expose the new MCP lifecycle and shared-service tools, even though the schema number is unchanged.

MCP request recovery covers recorded AWR operations; it does not make unrelated host tools or third-party calls exactly-once. Native platform regression, installation checks and project self-use are separate from enterprise-client integration and full business acceptance.