arena-shell-control
Use the existing Arena Shell as the visible organizing frame.
Assimilate tab/window/open/preview behavior into unified shell controls.
/agent-arena/shell58Q Arena Shell Guide
Arena Shell Feature Flow Map
The Arena Shell should guide how every feature is reached: one command frame, clear tabs, fewer duplicate route paths, and deep experiences preserved behind cleaner entrances.
agents-first
Agents should help review, test, and implement already-created features.
Select existing agent runner/workflow/testing pieces before writing new runtime.
/agent-lablive-connection
Live connection should start as one controlled bridge candidate.
Choose one safe bridge path: provider, adapter, browser bridge, or controlled web search.
/live-connection-readinessunified-search
Internal and external search should live under one command layer.
Connect internal routes/registry first, external web second, browser tabs third.
/unified-search-browser-bridge-mapexperience-depth
Keep saturated quality but reduce duplicate pathways.
Group duplicate/circular pages as experiments until one path wins.
/visual-flow-registryLive bridge order
Highest safety and immediate utility. Lets agents find existing components.
Agents can inspect candidate pages and surface implementation tasks.
Adds live outside knowledge with source boundary and attribution.
Enables browser-like experience without full Chrome control risk.
Powerful but should wait for permission gates and testing.