agentenv-framework-protocol 0.1.374__tar.gz → 0.1.376__tar.gz

{agentenv_framework_protocol-0.1.374 → agentenv_framework_protocol-0.1.376}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: agentenv-framework-protocol
-Version: 0.1.374
+Version: 0.1.376
 Summary: Open data-plane protocol and server SDK for agent environments.
 Project-URL: Homepage, https://www.agentenvframework.com
 Project-URL: Documentation, https://www.agentenvframework.com/docs
@@ -34,10 +34,15 @@ Requires-Dist: mcp<2,>=1.25; extra == 'agent'
 Requires-Dist: python-multipart>=0.0.13; extra == 'agent'
 Requires-Dist: regex>=2023.12.25; extra == 'agent'
 Requires-Dist: uvicorn>=0.30; extra == 'agent'
+Provides-Extra: computer
+Requires-Dist: mcp<2,>=1.25; extra == 'computer'
+Requires-Dist: pillow>=10.4; extra == 'computer'
+Requires-Dist: uvicorn>=0.30; extra == 'computer'
 Provides-Extra: dev
 Requires-Dist: a2a-sdk[http-server]<0.4,>=0.3.26; extra == 'dev'
 Requires-Dist: fastmcp<4,>=3.4; extra == 'dev'
 Requires-Dist: mcp<2,>=1.25; extra == 'dev'
+Requires-Dist: pillow>=10.4; extra == 'dev'
 Requires-Dist: pytest-asyncio>=0.23.0; extra == 'dev'
 Requires-Dist: pytest>=9.0; extra == 'dev'
 Requires-Dist: python-multipart>=0.0.13; extra == 'dev'
@@ -136,10 +141,34 @@ step names it. Steps that name it show and hide it as they do any tool. Steps fo
 that role's earlier named steps, and a full reset (`role: "*", tools: "*"`) clears all of them, so
 grant a hidden tool after such steps. Trigger tool actions call it as usual.
 
+`@tool(..., annotations={"readOnlyHint": True}, structured_output=True, meta={...})` lists the tool
+with MCP `ToolAnnotations`, an output schema and `_meta`, on mcp's FastMCP and on fastmcp alike.
+`structured_output` follows mcp's FastMCP (None derives an output schema from the return annotation
+where it can, False lists none); a tool returning `Annotated[CallToolResult, Model]` sends its
+result as is, image blocks included, and is listed with `Model`'s schema. An environment chooses
+at mount which of its `@tool` methods it serves, and with which descriptions, by overriding
+`served_tools(tools)`. After the mount, `env.mounted_card()` is the card the application serves, and
+`await env.update_tool(name, description=...)` changes a served tool's description on it and in
+`tools/list` alike, on both FastMCPs.
+
 `AgentEnvStarletteApplication` mounts the same handler onto a Starlette/FastAPI app instead of
 FastMCP; since those apps have no MCP tool registry, constructing one with `@tool` methods
 raises.
 
+### Errors
+
+Raise `AgentEnvError(code, message, *, retryable=False, applied="no", hint=None, status=400)` to
+answer a caller with a code rather than a crash. From an `@extension` method it answers with
+`status` and the body `{"ok": false, "error": {code, message, retryable, applied, hint?}}`; from a
+`@tool` it answers `isError` with `"<code>: <message>"` as the text and the same fields as the
+structured content. `applied` says whether the call's effect happened (`yes`, `no`, or `unknown`
+when it may have been delivered before something failed), and callers retry on their own only when
+`retryable` is true and `applied` is `no`. Any other exception in an extension still answers
+`extension_failed` with status 500, now with `applied: "unknown"`. On the client side,
+`invoke_extension` raises `ExtensionCallError`, an `httpx.HTTPStatusError` carrying `code`,
+`detail`, `retryable`, `applied` and `hint`; a body without those fields, such as a proxy's error
+page, leaves `code` None and `applied` `unknown`.
+
 ### Who is calling
 
 A tool that needs the caller declares a parameter annotated `ToolContext` (any name) and receives
@@ -226,6 +255,40 @@ extension's, and `client.invoke_extension(base_url, card, uri, params, method=..
 its HTTP verb. Without `method`, `invoke_extension` calls the first method listed; an extension
 with several methods, such as a gateway's `urn:agentenv:clock/v1`, should always be called by name.
 
+An extension with several methods is served by giving each handler an `op`. Handlers sharing a URI
+merge into one card entry, each method under `params.methods.<op>` with its own verb and endpoint,
+by default `/agentenv/ext/<extension>/<op>`, where `<extension>` is the URN's name without
+`urn:agentenv:` and the version. Extension-level params, such as features and limits, come from the
+environment's `extension_params(uri)`, merged beside `methods`. A declaration-only extension, a
+promise with params and no handler like `intake/v1`, is returned from `declared_extensions()`.
+Two handlers for one method, or a handler without `op` on a URI another handler also serves, are
+refused at mount.
+
+An environment chooses at mount which of its `@extension` handlers it serves by overriding
+`served_extensions(extensions)`: an extension it leaves out is not served, and of one served with
+`op`, only the methods its returned descriptor still lists under `params.methods`.
+`served_operations(operations)` chooses the data-plane methods (`data/add` and the others it
+marks) the same way. Either hook returning something with no handler is refused at mount.
+
+```python
+@extension("urn:agentenv:computer-display/v1", op="get", method="GET")
+async def display_get(self) -> dict: ...
+
+@extension("urn:agentenv:computer-display/v1", op="set")
+async def display_set(self, width: int, height: int) -> dict: ...
+```
+
+### Tool access without a gateway
+
+An environment agents reach directly, with no gateway in front, can enforce per-role tool access
+itself: set `tool_access = True` on the class. It then filters `tools/list` and refuses `tools/call`
+(`permission_denied`) by the caller's role, read from `AgentEnv-Role` or a gateway-stamped `_meta`
+role, and serves `urn:agentenv:disable-tool/v1` and `urn:agentenv:enable-tool/v1` at the gateway's
+paths (`POST /tools/disable`, `POST /tools/enable`) with its bodies (`{role, tools: [...] | "*"}` to
+`{role, disabled, allowed}`) and its rules, hidden-by-default tools included. So agent-env's
+`modify_env_tool_access` step works on such an env unchanged. A call with no role is `default`, as
+at the gateway.
+
 Where the binding lives depends on the app. On mcp's own FastMCP it wraps the tool manager's dispatch; on the standalone `fastmcp` package it joins the app's middleware chain as the outermost layer, so a handler's own middleware runs under it too. An app with neither seam mounts unbound, with a warning, unless a tool declares a `ToolContext` parameter or the handler defines `on_tool_call`: then the mount is refused rather than serving an empty caller.
 
 ### Uploading an export through a grant
@@ -300,6 +363,116 @@ async with ToolSession(mcp_url=mcp_url, role="alice@example.com") as session:
 - **Tools:** `list_tools()` returns the tools the role may use as `EnvironmentTool`, the type a card's
   `capabilities.tools` holds. Each `inputSchema` is the JSON Schema a model API takes as the tool's parameters.
 
+## Computer drivers
+
+A computer driver is what runs inside a computer an agent uses through screenshots and input. Write
+one as a `ComputerDriverEnvironment` subclass from `agentenv_protocol.computer`, which needs the
+`computer` extra (`pip install 'agentenv-framework-protocol[computer]'`: mcp, uvicorn and Pillow).
+The driver marks the methods that capture the screen and send input; the base class serves the
+computer contract from them, so the tools, results and errors can't drift from it. A complete
+driver for an X11 desktop, with an image to run it in, is in
+[`examples/computer_x11/`](https://github.com/scaleapi/agentenv-framework/tree/main/packages/agentenv-protocol/examples/computer_x11).
+
+```python
+from agentenv_protocol.computer import (
+    ComputerDriverEnvironment, Display, computer_driver,
+    capture, click, display, drag, press, scroll, type_text,
+)
+
+
+@computer_driver(name="my-driver", supports=[{"os": {"type": "linux", "display": ["x11"]}, "arch": ["amd64"]}])
+class MyDriver(ComputerDriverEnvironment):
+    buttons = ("left", "right")       # features, on the card
+    max_click_count = 2
+
+    @display
+    async def size(self) -> Display: ...                    # width, height, scale
+    @capture(display="x11")
+    async def grab(self): ...                               # the whole display, native resolution
+    @click
+    async def click_at(self, x, y, button, count, modifiers): ...
+    @drag
+    async def drag_along(self, path, button, duration_ms, modifiers): ...
+    @scroll
+    async def scroll_at(self, x, y, direction, amount, modifiers): ...
+    @type_text
+    async def type_in(self, text): ...
+    @press
+    async def press_keys(self, keys): ...
+
+
+if __name__ == "__main__":
+    MyDriver().serve()
+```
+
+**Operations.** Operations get points in screen pixels, after the base class has mapped, checked
+and queued the call, and may be sync or async. `@capture` returns a Pillow image or an
+`Image(width, height, data, mode)` (PNG or JPEG bytes, or raw `RGB`, `RGBA`, `BGRA` or `BGRX`
+pixels), at the display's size times its scale. Input operations may return an `Effect`.
+
+| Decorator | Required | Gives |
+|---|---|---|
+| `@display`, `@capture`, `@click`, `@drag`, `@scroll`, `@type_text`, `@press` | yes | the seven `computer_*` tools and `computer/v1` |
+| `@set_display` | no, with `display_modes` | `computer-display/v1` `set` (`get` is always served) |
+| `@pointer_move`, `@pointer_down`, `@pointer_up`, `@pointer_position` | all or none | `computer-pointer/v1` and its five tools; click and scroll at the pointer |
+| `@key_down`, `@key_up` | both or none | `computer-keyboard/v1` and its two tools |
+| `@run_in_session` | no; a Linux default | `computer-exec/v1` |
+| `@write_files` | no; a Linux default | `data/add` |
+
+The class is checked when it is defined: a missing required operation, half a group, two methods
+for one operation that some platform could both match, or features that don't match the
+decorators raise `TypeError`. Predicates (`os`, `distribution`, `version`, `arch`, `display`)
+choose a method per platform, read from `/etc/os-release`, the machine and `XDG_SESSION_TYPE` or
+`DISPLAY`: `@capture(display="x11")` and `@capture(display="wayland")` can sit side by side. A
+driver's own `@run_in_session` or `@write_files` replaces the base class's Linux default, which runs
+as the driver's user inside the desktop session. The base class keeps its state in `self._computer`
+and names its own members `_computer_*` and `computer_*`; a driver that redefines one of them, or
+another private member of the base class, is refused when it is defined, so a helper of the
+driver's can't silently replace one. What the optional operations give is served only when the
+driver has them, through the `served_tools`, `served_extensions` and `served_operations` hooks.
+
+**What the base class serves:**
+
+- **Tools.** `computer_screenshot` (a frame: `frame_id`, image size, display resolution and scale;
+  `region` crops a frame at native resolution), `computer_click`, `computer_drag`,
+  `computer_scroll`, `computer_type`, `computer_key` (W3C key names) and `computer_wait`, plus the
+  group tools. Every result is structured, with a one-line summary as its text block; input results
+  carry `applied`, `delivery` and `others_since_frame`, and `screenshot: true` returns a fresh frame
+  after acting. Click and scroll leave out `x` and `y` to act at the pointer on a computer with
+  `computer-pointer/v1`; elsewhere a call without them is refused `invalid_argument`.
+- **Frames and spaces.** Points are pixels of a named frame (your latest by default), or a
+  0..`norm_scale` grid over it with `space: "norm"`. A point outside the frame or the range is
+  refused (`out_of_bounds`), never clamped. The last 64 frames are kept, and a frame goes stale
+  (`stale_frame`) when the display geometry it was captured at changes.
+- **The input queue.** Input calls run one at a time in arrival order; one that waits past
+  `queue_wait_s` is refused `input_busy`. Screenshots and waits never queue.
+- **Framework extensions.** `computer-ready/v1` (`status`: real checks of the display and a
+  capture, plus the driver's own `ready_checks()`; tools refuse `device_unavailable` until they
+  pass once), `computer-display/v1`, `computer-spaces/v1` (the default space, written into the tool
+  descriptions), `computer-keyboard/v1` and `computer-exec/v1` (`run {argv, cwd?, env?, timeout_s?,
+  request_id}`: output capped per stream, a repeated `request_id` answered with the first result).
+- **The data plane.** `data/add` takes file parts that name their path, relative to the session
+  user's home, under the `data-objects/v1` marker (`{"path": ...}`), as inline bytes, an https URL,
+  or a `transfers.ReadObject` read grant under the marker's `read`, and writes them atomically.
+  `data/get` returns the files under the settings' `data_paths`, inline or uploaded under a
+  `write_namespace` grant.
+- **The card** (the name from `ENVIRONMENT_NAME`, then `@computer_driver`'s), and per-role tool
+  access (`tool_access` is on).
+
+**Errors.** A driver raises the errors table's exceptions, all `AgentEnvError`s:
+`InvalidArgument`, `OutOfBounds`, `StaleFrame`, `InputBusy`, `PermissionDenied`, `Unsupported`,
+`BackgroundUnavailable`, `TargetUnavailable`, `DeviceUnavailable` and `LimitExceeded` mean nothing
+was sent (`applied: "no"`); `Timeout`, `DeliveryFailed` and `Internal` mean it may have been. Any
+other exception from an input operation is reported `delivery_failed` with `applied: "unknown"`.
+
+**Settings** reach the driver as one JSON value in `AGENTENV_COMPUTER_SETTINGS`
+(`ComputerSettings`): `data_paths`, `default_space`, `default_norm_scale`, `queue_wait_s`,
+`tap_hold_ms`, `type_delay_ms`, `max_hold_ms`, `layout`, `drag_duration_ms`, `exec_output_bytes`
+and `exec_timeout_s`. A driver reads them as `self.settings`, for example its tap hold in `@press`.
+
+Every caller is `default` until agents carry an identity of their own; `caller_identity(context)`
+names the caller whose latest frame and others' input a call uses.
+
 ## A2A agent framework
 
 The distribution exposes two unrelated decorators named `extension`:

{agentenv_framework_protocol-0.1.374 → agentenv_framework_protocol-0.1.376}/README.md

@@ -90,10 +90,34 @@ step names it. Steps that name it show and hide it as they do any tool. Steps fo
 that role's earlier named steps, and a full reset (`role: "*", tools: "*"`) clears all of them, so
 grant a hidden tool after such steps. Trigger tool actions call it as usual.
 
+`@tool(..., annotations={"readOnlyHint": True}, structured_output=True, meta={...})` lists the tool
+with MCP `ToolAnnotations`, an output schema and `_meta`, on mcp's FastMCP and on fastmcp alike.
+`structured_output` follows mcp's FastMCP (None derives an output schema from the return annotation
+where it can, False lists none); a tool returning `Annotated[CallToolResult, Model]` sends its
+result as is, image blocks included, and is listed with `Model`'s schema. An environment chooses
+at mount which of its `@tool` methods it serves, and with which descriptions, by overriding
+`served_tools(tools)`. After the mount, `env.mounted_card()` is the card the application serves, and
+`await env.update_tool(name, description=...)` changes a served tool's description on it and in
+`tools/list` alike, on both FastMCPs.
+
 `AgentEnvStarletteApplication` mounts the same handler onto a Starlette/FastAPI app instead of
 FastMCP; since those apps have no MCP tool registry, constructing one with `@tool` methods
 raises.
 
+### Errors
+
+Raise `AgentEnvError(code, message, *, retryable=False, applied="no", hint=None, status=400)` to
+answer a caller with a code rather than a crash. From an `@extension` method it answers with
+`status` and the body `{"ok": false, "error": {code, message, retryable, applied, hint?}}`; from a
+`@tool` it answers `isError` with `"<code>: <message>"` as the text and the same fields as the
+structured content. `applied` says whether the call's effect happened (`yes`, `no`, or `unknown`
+when it may have been delivered before something failed), and callers retry on their own only when
+`retryable` is true and `applied` is `no`. Any other exception in an extension still answers
+`extension_failed` with status 500, now with `applied: "unknown"`. On the client side,
+`invoke_extension` raises `ExtensionCallError`, an `httpx.HTTPStatusError` carrying `code`,
+`detail`, `retryable`, `applied` and `hint`; a body without those fields, such as a proxy's error
+page, leaves `code` None and `applied` `unknown`.
+
 ### Who is calling
 
 A tool that needs the caller declares a parameter annotated `ToolContext` (any name) and receives
@@ -180,6 +204,40 @@ extension's, and `client.invoke_extension(base_url, card, uri, params, method=..
 its HTTP verb. Without `method`, `invoke_extension` calls the first method listed; an extension
 with several methods, such as a gateway's `urn:agentenv:clock/v1`, should always be called by name.
 
+An extension with several methods is served by giving each handler an `op`. Handlers sharing a URI
+merge into one card entry, each method under `params.methods.<op>` with its own verb and endpoint,
+by default `/agentenv/ext/<extension>/<op>`, where `<extension>` is the URN's name without
+`urn:agentenv:` and the version. Extension-level params, such as features and limits, come from the
+environment's `extension_params(uri)`, merged beside `methods`. A declaration-only extension, a
+promise with params and no handler like `intake/v1`, is returned from `declared_extensions()`.
+Two handlers for one method, or a handler without `op` on a URI another handler also serves, are
+refused at mount.
+
+An environment chooses at mount which of its `@extension` handlers it serves by overriding
+`served_extensions(extensions)`: an extension it leaves out is not served, and of one served with
+`op`, only the methods its returned descriptor still lists under `params.methods`.
+`served_operations(operations)` chooses the data-plane methods (`data/add` and the others it
+marks) the same way. Either hook returning something with no handler is refused at mount.
+
+```python
+@extension("urn:agentenv:computer-display/v1", op="get", method="GET")
+async def display_get(self) -> dict: ...
+
+@extension("urn:agentenv:computer-display/v1", op="set")
+async def display_set(self, width: int, height: int) -> dict: ...
+```
+
+### Tool access without a gateway
+
+An environment agents reach directly, with no gateway in front, can enforce per-role tool access
+itself: set `tool_access = True` on the class. It then filters `tools/list` and refuses `tools/call`
+(`permission_denied`) by the caller's role, read from `AgentEnv-Role` or a gateway-stamped `_meta`
+role, and serves `urn:agentenv:disable-tool/v1` and `urn:agentenv:enable-tool/v1` at the gateway's
+paths (`POST /tools/disable`, `POST /tools/enable`) with its bodies (`{role, tools: [...] | "*"}` to
+`{role, disabled, allowed}`) and its rules, hidden-by-default tools included. So agent-env's
+`modify_env_tool_access` step works on such an env unchanged. A call with no role is `default`, as
+at the gateway.
+
 Where the binding lives depends on the app. On mcp's own FastMCP it wraps the tool manager's dispatch; on the standalone `fastmcp` package it joins the app's middleware chain as the outermost layer, so a handler's own middleware runs under it too. An app with neither seam mounts unbound, with a warning, unless a tool declares a `ToolContext` parameter or the handler defines `on_tool_call`: then the mount is refused rather than serving an empty caller.
 
 ### Uploading an export through a grant
@@ -254,6 +312,116 @@ async with ToolSession(mcp_url=mcp_url, role="alice@example.com") as session:
 - **Tools:** `list_tools()` returns the tools the role may use as `EnvironmentTool`, the type a card's
   `capabilities.tools` holds. Each `inputSchema` is the JSON Schema a model API takes as the tool's parameters.
 
+## Computer drivers
+
+A computer driver is what runs inside a computer an agent uses through screenshots and input. Write
+one as a `ComputerDriverEnvironment` subclass from `agentenv_protocol.computer`, which needs the
+`computer` extra (`pip install 'agentenv-framework-protocol[computer]'`: mcp, uvicorn and Pillow).
+The driver marks the methods that capture the screen and send input; the base class serves the
+computer contract from them, so the tools, results and errors can't drift from it. A complete
+driver for an X11 desktop, with an image to run it in, is in
+[`examples/computer_x11/`](https://github.com/scaleapi/agentenv-framework/tree/main/packages/agentenv-protocol/examples/computer_x11).
+
+```python
+from agentenv_protocol.computer import (
+    ComputerDriverEnvironment, Display, computer_driver,
+    capture, click, display, drag, press, scroll, type_text,
+)
+
+
+@computer_driver(name="my-driver", supports=[{"os": {"type": "linux", "display": ["x11"]}, "arch": ["amd64"]}])
+class MyDriver(ComputerDriverEnvironment):
+    buttons = ("left", "right")       # features, on the card
+    max_click_count = 2
+
+    @display
+    async def size(self) -> Display: ...                    # width, height, scale
+    @capture(display="x11")
+    async def grab(self): ...                               # the whole display, native resolution
+    @click
+    async def click_at(self, x, y, button, count, modifiers): ...
+    @drag
+    async def drag_along(self, path, button, duration_ms, modifiers): ...
+    @scroll
+    async def scroll_at(self, x, y, direction, amount, modifiers): ...
+    @type_text
+    async def type_in(self, text): ...
+    @press
+    async def press_keys(self, keys): ...
+
+
+if __name__ == "__main__":
+    MyDriver().serve()
+```
+
+**Operations.** Operations get points in screen pixels, after the base class has mapped, checked
+and queued the call, and may be sync or async. `@capture` returns a Pillow image or an
+`Image(width, height, data, mode)` (PNG or JPEG bytes, or raw `RGB`, `RGBA`, `BGRA` or `BGRX`
+pixels), at the display's size times its scale. Input operations may return an `Effect`.
+
+| Decorator | Required | Gives |
+|---|---|---|
+| `@display`, `@capture`, `@click`, `@drag`, `@scroll`, `@type_text`, `@press` | yes | the seven `computer_*` tools and `computer/v1` |
+| `@set_display` | no, with `display_modes` | `computer-display/v1` `set` (`get` is always served) |
+| `@pointer_move`, `@pointer_down`, `@pointer_up`, `@pointer_position` | all or none | `computer-pointer/v1` and its five tools; click and scroll at the pointer |
+| `@key_down`, `@key_up` | both or none | `computer-keyboard/v1` and its two tools |
+| `@run_in_session` | no; a Linux default | `computer-exec/v1` |
+| `@write_files` | no; a Linux default | `data/add` |
+
+The class is checked when it is defined: a missing required operation, half a group, two methods
+for one operation that some platform could both match, or features that don't match the
+decorators raise `TypeError`. Predicates (`os`, `distribution`, `version`, `arch`, `display`)
+choose a method per platform, read from `/etc/os-release`, the machine and `XDG_SESSION_TYPE` or
+`DISPLAY`: `@capture(display="x11")` and `@capture(display="wayland")` can sit side by side. A
+driver's own `@run_in_session` or `@write_files` replaces the base class's Linux default, which runs
+as the driver's user inside the desktop session. The base class keeps its state in `self._computer`
+and names its own members `_computer_*` and `computer_*`; a driver that redefines one of them, or
+another private member of the base class, is refused when it is defined, so a helper of the
+driver's can't silently replace one. What the optional operations give is served only when the
+driver has them, through the `served_tools`, `served_extensions` and `served_operations` hooks.
+
+**What the base class serves:**
+
+- **Tools.** `computer_screenshot` (a frame: `frame_id`, image size, display resolution and scale;
+  `region` crops a frame at native resolution), `computer_click`, `computer_drag`,
+  `computer_scroll`, `computer_type`, `computer_key` (W3C key names) and `computer_wait`, plus the
+  group tools. Every result is structured, with a one-line summary as its text block; input results
+  carry `applied`, `delivery` and `others_since_frame`, and `screenshot: true` returns a fresh frame
+  after acting. Click and scroll leave out `x` and `y` to act at the pointer on a computer with
+  `computer-pointer/v1`; elsewhere a call without them is refused `invalid_argument`.
+- **Frames and spaces.** Points are pixels of a named frame (your latest by default), or a
+  0..`norm_scale` grid over it with `space: "norm"`. A point outside the frame or the range is
+  refused (`out_of_bounds`), never clamped. The last 64 frames are kept, and a frame goes stale
+  (`stale_frame`) when the display geometry it was captured at changes.
+- **The input queue.** Input calls run one at a time in arrival order; one that waits past
+  `queue_wait_s` is refused `input_busy`. Screenshots and waits never queue.
+- **Framework extensions.** `computer-ready/v1` (`status`: real checks of the display and a
+  capture, plus the driver's own `ready_checks()`; tools refuse `device_unavailable` until they
+  pass once), `computer-display/v1`, `computer-spaces/v1` (the default space, written into the tool
+  descriptions), `computer-keyboard/v1` and `computer-exec/v1` (`run {argv, cwd?, env?, timeout_s?,
+  request_id}`: output capped per stream, a repeated `request_id` answered with the first result).
+- **The data plane.** `data/add` takes file parts that name their path, relative to the session
+  user's home, under the `data-objects/v1` marker (`{"path": ...}`), as inline bytes, an https URL,
+  or a `transfers.ReadObject` read grant under the marker's `read`, and writes them atomically.
+  `data/get` returns the files under the settings' `data_paths`, inline or uploaded under a
+  `write_namespace` grant.
+- **The card** (the name from `ENVIRONMENT_NAME`, then `@computer_driver`'s), and per-role tool
+  access (`tool_access` is on).
+
+**Errors.** A driver raises the errors table's exceptions, all `AgentEnvError`s:
+`InvalidArgument`, `OutOfBounds`, `StaleFrame`, `InputBusy`, `PermissionDenied`, `Unsupported`,
+`BackgroundUnavailable`, `TargetUnavailable`, `DeviceUnavailable` and `LimitExceeded` mean nothing
+was sent (`applied: "no"`); `Timeout`, `DeliveryFailed` and `Internal` mean it may have been. Any
+other exception from an input operation is reported `delivery_failed` with `applied: "unknown"`.
+
+**Settings** reach the driver as one JSON value in `AGENTENV_COMPUTER_SETTINGS`
+(`ComputerSettings`): `data_paths`, `default_space`, `default_norm_scale`, `queue_wait_s`,
+`tap_hold_ms`, `type_delay_ms`, `max_hold_ms`, `layout`, `drag_duration_ms`, `exec_output_bytes`
+and `exec_timeout_s`. A driver reads them as `self.settings`, for example its tap hold in `@press`.
+
+Every caller is `default` until agents carry an identity of their own; `caller_identity(context)`
+names the caller whose latest frame and others' input a call uses.
+
 ## A2A agent framework
 
 The distribution exposes two unrelated decorators named `extension`:

agentenv_framework_protocol-0.1.376/examples/computer_x11/Dockerfile

@@ -0,0 +1,19 @@
+# Built from packages/agentenv-protocol, so the driver runs on this checkout's SDK:
+#   docker build -f examples/computer_x11/Dockerfile -t x11-desktop .
+FROM public.ecr.aws/docker/library/ubuntu:24.04
+ENV DEBIAN_FRONTEND=noninteractive
+RUN apt-get update && apt-get install -y --no-install-recommends \
+        python3 python3-venv python3-tk xvfb x11-utils fonts-dejavu-core procps \
+        libxcb1 libxcb-render0 libxcb-shm0 libxcb-randr0 libxcb-xfixes0 libxcb-xinerama0 \
+    && rm -rf /var/lib/apt/lists/*
+COPY pyproject.toml README.md LICENSE NOTICE THIRD_PARTY_NOTICES.md /opt/protocol/
+COPY src /opt/protocol/src
+RUN python3 -m venv /opt/driver \
+    && /opt/driver/bin/pip install --no-cache-dir "/opt/protocol[computer]" "mss>=9,<11" "python-xlib>=0.33,<0.34"
+RUN useradd --create-home --uid 10001 user
+COPY examples/computer_x11/start.sh examples/computer_x11/driver.py examples/computer_x11/fixture.py /opt/desktop/
+USER user
+WORKDIR /home/user
+ENV DISPLAY=:99 XDG_SESSION_TYPE=x11
+EXPOSE 18765
+CMD ["/bin/sh", "/opt/desktop/start.sh"]

agentenv_framework_protocol-0.1.376/examples/computer_x11/README.md

@@ -0,0 +1,60 @@
+# An X11 computer driver
+
+[`driver.py`](driver.py) is a complete computer driver for an X11 desktop, written on
+`ComputerDriverEnvironment` from `agentenv_protocol.computer`: `mss` captures the screen and XTEST,
+through `python-xlib`, sends the input. It implements the seven required operations and the pointer
+and keyboard groups, declares five buttons, triple clicks and 50-point drags, and adds a ready check
+of its own for XTEST. The base class serves everything else from those: the `computer_*` tools,
+frames and coordinate spaces, the input queue, the framework extensions and the card, and its Linux
+defaults give the driver `computer-exec/v1` and `data/add`.
+
+The image runs the driver on Xvfb beside [`fixture.py`](fixture.py), the Fixture Desk: a Tk window
+with a name field, a checkbox, a 100-item list, a grid of cells, a drawing pad and a Save button. It
+records whatever reaches it in `~/fixture/state.json`, so what an agent did can be read back from
+the app rather than from the driver's answers, and shows the text of `~/inbox/message.txt`, which
+`data/add` can write. [`start.sh`](start.sh) restarts Xvfb and the app if either dies.
+
+## Run it
+
+```bash
+cd packages/agentenv-protocol
+docker build -f examples/computer_x11/Dockerfile -t x11-desktop .
+docker run --rm -p 18765:18765 x11-desktop
+```
+
+The card is at `http://localhost:18765/.well-known/agent-env.json`, readiness at
+`/agentenv/ext/computer-ready/status`, and the tools at the MCP endpoint `/mcp`:
+
+```python
+import asyncio
+
+from mcp import ClientSession
+from mcp.client.streamable_http import streamablehttp_client
+
+
+async def main() -> None:
+    async with streamablehttp_client("http://localhost:18765/mcp") as (read, write, _):
+        async with ClientSession(read, write) as session:
+            await session.initialize()
+            shot = await session.call_tool("computer_screenshot", {})
+            print(shot.structuredContent["summary"])
+            await session.call_tool("computer_click", {"x": 300, "y": 52})
+            typed = await session.call_tool("computer_type", {"text": "Ada Lovelace", "screenshot": True})
+            print(typed.structuredContent["summary"])
+
+
+asyncio.run(main())
+```
+
+`AGENTENV_COMPUTER_SETTINGS` takes the driver's settings as one JSON value, for example
+`-e AGENTENV_COMPUTER_SETTINGS='{"default_space": "norm", "data_paths": ["fixture"]}'`.
+
+## In agent-env
+
+As a bundle env (`envs/<name>/Dockerfile`), the image is built from the env's own folder, so copy
+the three files there and install `agentenv-framework-protocol[computer]` in place of this checkout.
+Name the env with `environment_name` in its `env.toml`. A task then deploys it with `deploy_env`
+and gives it to an agent with `deploy_agent`, as for any MCP env.
+
+`tests/test_computer_x11_example.py` runs the driver against fake `mss` and `Xlib` modules, so it
+keeps up with the SDK without an X server.