DevApp Connection

Overview

When the Fenwave Agent is running, it starts a local server that the Fenwave DevApp dashboard connects to. This connection is what makes the DevApp interactive — every action you take in the dashboard (starting a container, streaming logs, opening a terminal, …) is handled by the agent on your machine.

The connection is local-only and never exposed to the internet.

How It Works

Fenwave DevApp Dashboard  ──── local connection ────►  Fenwave Agent
     (port 3003)                                          (port 3001)
                                                              │
                                                              ▼
                                                       Docker Engine

The agent must be running for the DevApp to function. If the DevApp shows a disconnected state, start the agent first.

What the DevApp Can Do Through the Agent

Once connected, the DevApp gives you a visual interface to:

Containers

List, start, stop, restart, and remove containers
Inspect container details and resource usage

Images

Browse, pull, and remove Docker images
Push images to connected registries

Volumes

Create, remove, and inspect volumes
Back up and restore volume data

Apps

Manage application blueprints from the platform
Switch between published versions

Registries

Connect to Docker registries (GHCR, Docker Hub, ECR, etc.)
Browse images from connected registries

Logs & Terminal

Stream live container logs
Open an interactive terminal session inside any container

Metrics

View real-time CPU, memory, and disk usage per container

Ports Allocation

Component	Default Port	Fallback Range
Agent server	3001	3001–3010
DevApp dashboard	3003	3003–3102

Ports are allocated automatically if the defaults are already in use. You can override the agent server port:

fenwave service start --port 3005