A second CTA card sits immediately after the existing dashed
Add application card at the end of the Applications grid
(ApplicationsPage.tsx, today ~L363). Same footprint and keyboard behaviour as its
sibling, but solid-bordered with the fuse seam on top: it is the agent-driven path, not the
manual one. The card exists only while fuzefront.apps.build-with-agent is ON.
Federated apps registered to your workspace.
World clocks for your team.
Work with FuzeAgent.
Register a federated or standalone app.
Describe it — FuzeAgent builds and deploys it for you.
World clocks for your team.
Register a federated or standalone app.
Behaviour. The card is a role="button" with tabIndex=0, activated by
click, Enter or Space — identical to the Add card. It routes to /applications/build (frame b).
In (a4) the latest non-terminal session from GET /build-sessions?limit=1 turns the card into
a resume link to /applications/build/:sessionId; that read only happens when the flag is ON.
Flag. fuzefront.apps.build-with-agent, release, default OFF, builders audience.
OFF ⇒ the component returns null. The page change is a single mount of
<BuildAppCard /> from @fuzefront/app-builder-ui after the Add card —
the card's own markup and logic live in the package.
Test hooks: [data-frame='01-build-entry'] · [data-panel='applications-grid'] ·
[data-action='add-application'] · [data-card='build-application'] ·
[data-action='build-application'] · [data-flag-state='off'] ·
[data-flag-state='loading'] · [data-action='resume-build-session'].