jif
6d083e3bc4
## What changed Add `codex-agent-message-board-client` with a `RemoteAgentMessageBoard` implementation of the existing `AgentMessageBoard` interface over a versioned HTTP API. Use the shared HTTP client for authenticated board creation, deletion, member registration, and board operations. Validate endpoints and credentials, bound request and response sizes, and support a caller-supplied clock. Allow post retries without a fresh timestamp so the service can replay an already committed result. Provide live SSE receivers that wait for readiness and reject notifications for another agent or turn, as well as previews exceeding 150 characters. ## Testing Add a mock HTTP integration test covering endpoint and returned-credential validation, bearer authentication, post retries when the clock is unavailable, Unicode post reads, SSE readiness and notification validation, and service error handling. GitOrigin-RevId: 844f63ee14dc216a9d61767115892c4783fe9d44
1.2 KiB
Remote agent message board
RemoteAgentMessageBoard implements the existing board contract over an HTTP API.
Supply a configured API endpoint, existing SessionId, session credential, and Codex's shared
HTTP client. Construction validates the HTTP(S) endpoint, including optional path prefixes;
credentials are validated both at construction and when returned by the service. The backend can be deployed independently of Codex.
Each board belongs to one agent tree, exactly like the local backend. The launcher
creates it using that tree's SessionId and registers its agents. Calls use the
existing request and result types: callers are ThreadIds, while authors and
subscription targets remain AgentPaths.
Live SSE notifications are bound to the receiving turn. Open a receiver before
posting work that needs live updates and drop it when the turn ends. Reconnecting
opens a new live receiver; persisted posts can be recovered with search_posts
and after_message_id. The host must atomically validate the turn before injecting
a preview and must never wake a finalized agent to deliver one.
See protocol.rs for the v1 requests. The service owns storage, membership,
idempotency, subscriptions, and notification fanout. This crate contains no server.