DEVELOPMENT / SERVER INSPECTOR

See the server flow behind main.dowe

Use the backend dashboard during dowe dev to move from an endpoint or WebSocket to its compiled flow, source span, entities, resources, jobs, and bounded local runtime state.

The sidebar follows Dowe's ghost navigation style: destinations sit directly on the page surface, while the active area uses one compact filled row.

Endpoint rows keep selection separate from compact source and Try it icons. Try it opens the request form in a modal so the route catalog stays visible and uncluttered.

1 / OPEN THE DASHBOARD

Use the server target

The dashboard uses the same backend listener as your authored routes; it does not create a second port or a production endpoint.

When web and server targets run together, the web inspector shows a server icon beside its view routes and opens this dashboard in a new tab.

View-only HMR rebuilds keep the backend inspector manifest and URL available while the web output updates.

dowe
dowe dev --target server
open http://127.0.0.1:8080/_dowe/dev/server/
The URL uses server.port from main.dowe. Replace 8080 when the project declares another port.

2 / DASHBOARD AREAS

A compact map of the backend

Area
What it provides

No data

There are no records to display

3 / AGENT HANDOFF

Copy an endpoint or source node

Select an endpoint, WebSocket, handler, entity, or resource, copy its request or channel context, and give the agent the project-relative path plus inclusive lines. Source access is resolved from an opaque node ID and is capped to a small snippet.

dowe
POST /api/orders
Body: { name:string, total:number }
Try it: headers · search · body · response
Source: server/routes/orders.dowe:18-42
Flow: endpoint → createOrder → database:orders

4 / TRY THE SERVER

Test requests without leaving Dowe

Endpoints expose compiler-derived path, search, header, middleware, and body metadata. Use Try it to execute the selected method through the shared development runtime and inspect a bounded status, response headers, and response body. WebSockets provide a same-origin client for connect, send, received messages, close events, and errors.

5 / DEVELOPMENT BOUNDARY

Read-only and dev-only by contract

Target
Behavior

No data

There are no records to display

The Data studio browses local Database tables and entities, Cache keys, Queue messages, and Vector metadata with bounded results. It is read-only, masks credentials and sensitive fields, and truncates large values.