[maxy-shpfy]

Description

A remote environment can add, list, and read session resources over the /remote-env socket, through the same catalog path the HTTP resource routes use. An agent on one host can contribute a file, a host entry, or a memory write, and Prime or an agent on another machine can fetch it.

• Shared protocol: ack events remote:resource:add, remote:resource:list, and remote:resource:read. RemoteResourceInput reuses HostResourceInput, so a file write (bytes under uploads/, binary as base64), a host entry, and a memory write share one catalog path.
• Gateway: useResources wires the catalog, the spawn-preamble refresh, and the room notifier. Adds go through applyResourceInput. Lists scan the workspace, then return the catalog. Reads stay inside the session's uploads/ and artifacts/ trees, reject a uri that escapes that root, cap the payload at MAX_FILE_RESOURCE_BYTES, and return base64 plus a content type derived from the extension. Authorization reuses the room-read gate.
• Socket.IO maxHttpBufferSize matches MAX_JSON_BODY_BYTES, so a file at the 1 MiB cap still fits once base64 and the ack envelope are included.
• @tangent/remote-subagent: addResource, listResources, and readResource (30s ack timeout), documented in the package README.

How to test

1. pnpm --filter @tangent/server test — remoteEnvironmentGatewayResources.test.ts covers a file add/read/list round trip, a uri that escapes the session root, a session-scoped host writing another session, and an add when the catalog is not wired.
2. pnpm --filter @tangent/remote-subagent test — client ack success and rejection for add, list, and read.

Notes

Builds on #111. Next in the stack is #112; calling these methods from the local agent host is follow-up work.

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}