REQ-FUN-099

Non-MCP fallback control channel via send-text and poll-output endpoints

ID: REQ-FUN-099
Category: Functional Requirements
Status: approved
Priority: P0
Created: 2026-05-10T18:38:20.746Z
Approved: 2026-05-10T18:38:56.432Z
Updated: 2026-05-10T18:38:56.432Z

What

System SHALL provide a non-MCP fallback control channel via POST /v1/agent-sessions/{id}/send-text and GET /v1/agent-sessions/{id}/poll-output?since={cursor}.

Why

Inspired by AoE; supports agents that don't speak MCP (Codex CLI, Gemini CLI, generic shell agents). See arch_decision_nonmcp_fallback memory.

How

Both endpoints share the PASETO v4 auth model; capability scopes agent_session:read and agent_session:write distinct from board:* etc.; rate-limited per token; long-poll supported on poll-output; submission_id idempotency on send-text.

Done when

A non-MCP agent can claim, work on, and complete a board item using only these endpoints plus the standard structured board endpoints.

Out of scope

Server-side natural-language parsing of send-text body; structured tool emulation in plain text.

established project management guidelines Mapping

Primary Knowledge Area: Communications Management
Secondary KA: Integration Management
Primary Process Group: Executing
established project management guidelines Deliverable: Project Management Plan

Non-MCP fallback channel keeps agents reachable when the primary surface is unavailable - comms continuity.