Coming Soon

FFP is disabled

AgentOS V6.6.8 retains FFP compatibility data, but all runtime execution bypasses FFP. No activation control, consensus engine, validator voting, or proposal history is available.

Routing behavior

FFP Disabled: multi-agent activities route directly to the Unified Execution Engine.

FFP activation: unavailable. PATCH requests return Method Not Allowed.

All execution types bypass FFP in V6.6.8.

Affected execution types

Multi-agent workflows
Subagent collaboration
Multi-agent task delegation

Routes

GET/api/ffp/temp

Auth: Browser Session or Bearer

Returns the workspace FFP temp status, current route, affected execution types, and bypassed single-agent execution types.

PATCH/api/ffp/temp

Auth: Browser Session or Bearer

Returns 405 Method Not Allowed. FFP cannot be activated in V6.6.8.

Example

curl -s https://www.agentos.services/api/ffp/temp \
  -H "Authorization: Bearer $TOKEN"

curl -s https://www.agentos.services/api/ffp/temp \
  -X PATCH \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"enabled":true}'
# HTTP 405 Method Not Allowed