How freelance22688-cloud/orca_ui works
ORCA Hand Console is a browser-based monitoring and control application for ORCA Hands, with an MCP interface for agents. The main workflow is browser or MCP request → backend API → hand service and connected hardware; live telemetry returns through the stream hub and WebSocket to the UI. Distinct product stages include hardware discovery, sensor/motor monitoring, motion and library playback, setup operations, and teleoperation. The graph also shows the frontend state layer and operation/teleop managers. Some subsystem links reflect README capabilities because their implementation files were not sampled.
Main entry points: service.py Hand service · server.py App server · rest.py REST API · App.tsx App shell
Components 31
Browser interface
- App shell
frontend/src/App.tsx - Product views
frontend/src/components/views - UI state
frontend/src/state/appStore.ts - Stream state
frontend/src/state/streamStore.ts
API and streaming
- REST client
frontend/src/api/rest.ts - Stream client
frontend/src/api/streamClient.ts - App server
orca_ui/server.py - REST API
orca_ui/api/rest.py - WebSocket API
orca_ui/api/ws.py - Stream hub
orca_ui/streaming/hub.py - Stream topics
orca_ui/streaming/topics.py
Hand runtime
- Hand service
orca_ui/hand/service.py - Hardware supervisor
orca_ui/hand/supervisor.py - Connection sessions
orca_ui/hand/sessions.py - Capability state
orca_ui/hand/states.py - Hardware adapter
orca_ui/core_source.py - Telemetry service
orca_ui/hand/telemetry.py
Operations and teleop
- Operation manager
orca_ui/hand/operations/manager.py - Hand operations
orca_ui/hand/operations/hand_ops.py - Pose playback
orca_ui/hand/operations/player.py - Teleop manager
orca_ui/hand/teleop/manager.py - Teleop runner
orca_ui/hand/teleop/runner.py
Agent and pose tools
- Pose library
orca_ui/library.py - MCP server
orca_ui/mcp/server.py - MCP tools
orca_ui/mcp/tools.py - Backend client
orca_ui/mcp/client.py
Other components
- Operator
- Browser
- MCP client
- ORCA hand
- Teleop process
Connections 35
- Operator → Browser: uses
- Browser → App shell: opens
- App shell → Product views: renders
frontend/src/App.tsx - App shell → REST client: initializes
frontend/src/App.tsx - App shell → Stream client: starts
frontend/src/App.tsx - Stream client → UI state: updates
frontend/src/api/streamClient.ts - Stream client → Stream state: updates
frontend/src/api/streamClient.ts - REST client → REST API: requests
- Stream client → WebSocket API: subscribes
- App server → REST API: mounts
orca_ui/server.py - App server → WebSocket API: mounts
orca_ui/server.py - App server → Stream hub: creates
orca_ui/server.py - App server → Hand service: creates
orca_ui/server.py - App server → Telemetry service: starts
orca_ui/server.py - REST API → Hand service: delegates
orca_ui/api/rest.py - WebSocket API → Stream hub: subscribes
orca_ui/api/ws.py - WebSocket API → Hand service: reads
orca_ui/api/ws.py - Stream hub → Stream topics: uses
orca_ui/streaming/hub.py - Hand service → Hardware supervisor: owns
orca_ui/hand/service.py - Hardware supervisor → Connection sessions: connects
orca_ui/hand/supervisor.py - Connection sessions → Capability state: describes
orca_ui/hand/sessions.py - Connection sessions → Hardware adapter: connects through
- ORCA hand → Connection sessions: connects
- Telemetry service → Stream hub: publishes
- Operation manager → Hand service: controls
orca_ui/hand/operations/manager.py - Operation manager → Hand operations: runs
- Pose playback → Pose library: loads assets
orca_ui/hand/operations/player.py - REST API → Pose library: reads and writes
orca_ui/api/rest.py - Teleop manager → Hand service: coordinates
orca_ui/hand/teleop/manager.py - Teleop manager → Teleop runner: launches
orca_ui/hand/teleop/manager.py - Teleop runner → Teleop process: starts
- MCP client → MCP server: connects
- MCP server → MCP tools: registers
orca_ui/mcp/server.py - MCP tools → Backend client: calls
orca_ui/mcp/tools.py - Backend client → REST API: requests