mirror of
https://github.com/bytedance/deer-flow.git
synced 2026-07-28 00:48:07 +00:00
21b3510226
* feat(gateway): add GET /api/features for frontend feature gating (#3757) * feat(agents): add useAgentsApiEnabled feature-flag hook (#3757) * feat(agents): gate /workspace/agents segment on agents_api flag (#3757) * feat(sidebar): grey out Agents button with tooltip when agents_api disabled (#3757) * fix(sidebar): show disabled Agents tooltip on hover, harden a11y + e2e (#3757) - Wrap the disabled Agents button in a hoverable tooltip trigger so the 'feature not enabled' hint shows in the expanded sidebar, not only when collapsed (the SidebarMenuButton tooltip prop is hidden unless collapsed). - Add tabIndex={-1} and drop the redundant onClick preventDefault. - Add e2e coverage for the disabled state + a default /api/features mock. * style(sidebar): move cursor-not-allowed to the hoverable span (#3757) * test(agents): anchor e2e agents-API request filter with a path regex (#3757) * fix(agents): don't expose backend config in disabled message; tell user to contact admin (#3757) The disabled panel previously said 'Set agents_api.enabled: true in config.yaml', leaking backend configuration to end users. Replace with a generic 'not enabled on this server, contact your administrator' message (matching the existing nameStepApiDisabledError copy). e2e now asserts the contact-admin message and that no config.yaml/agents_api text is rendered. * make format * fix(agents): keep agents_api flag sticky during /api/features outage (#3757) Failing open re-mounted the agents UI and re-triggered the 403 storm when agents_api was genuinely disabled and /api/features was down. Persist the last definitive answer and fall back to it (sticky) before failing open, only failing open when nothing has ever been observed. Read the cached value after mount so the first client render matches the server (no hydration mismatch on the non-loading-gated sidebar). * fix(sidebar): make disabled Agents entry keyboard/SR accessible (#3757) The disabled-state explanation was hover-only: tabIndex={-1} removed the entry from the tab order and the reason lived only in a pointer-triggered tooltip. Keep it in the tab order and wire aria-describedby to a visually-hidden reason so keyboard and screen-reader users learn why it is disabled. --------- Co-authored-by: Willem Jiang <willem.jiang@gmail.com>
41 lines
1.4 KiB
Python
41 lines
1.4 KiB
Python
"""Read-only feature-flag endpoint for the frontend bootstrap.
|
|
|
|
Reports which optional, config-gated features are exposed over HTTP so the
|
|
frontend can gate UI and avoid firing requests that the backend would reject
|
|
with 403. Reads through ``get_config`` so edits to ``config.yaml`` take effect
|
|
on the next request without a restart (config hot-reload boundary).
|
|
"""
|
|
|
|
from fastapi import APIRouter, Depends
|
|
from pydantic import BaseModel, Field
|
|
|
|
from app.gateway.deps import get_config
|
|
from deerflow.config.app_config import AppConfig
|
|
|
|
router = APIRouter(prefix="/api", tags=["features"])
|
|
|
|
|
|
class AgentsApiFeature(BaseModel):
|
|
"""Availability of the custom-agent management API."""
|
|
|
|
enabled: bool = Field(..., description="Whether the agents_api routes are exposed over HTTP")
|
|
|
|
|
|
class FeaturesResponse(BaseModel):
|
|
"""Frontend-facing feature availability flags."""
|
|
|
|
agents_api: AgentsApiFeature
|
|
|
|
|
|
@router.get(
|
|
"/features",
|
|
response_model=FeaturesResponse,
|
|
summary="List Feature Flags",
|
|
description="Report which optional config-gated features are enabled, so the frontend can gate UI before issuing requests.",
|
|
)
|
|
async def list_features(config: AppConfig = Depends(get_config)) -> FeaturesResponse:
|
|
"""Return availability of optional, config-gated frontend features."""
|
|
return FeaturesResponse(
|
|
agents_api=AgentsApiFeature(enabled=config.agents_api.enabled),
|
|
)
|