Skip to content

Dashboard

The dashboard is the primary user interface for JARVIS. It is served directly by the daemon and updates in real time over WebSocket.

By default, it lives at:

http://localhost:3142

If the daemon is running somewhere else, use that machine’s host and port instead.

The dashboard is where you:

  • Chat with JARVIS
  • Watch tasks and delegated agent activity
  • Inspect memory and knowledge
  • Approve or deny governed actions
  • Monitor awareness events and suggestions
  • Build and run workflows
  • Track goals
  • Manage sidecars, channels, and integrations

The current dashboard navigation is organized into three groups plus settings.

  • Dashboard
  • Chat
  • Goals
  • Workflows
  • Sites
  • Agents
  • Tasks
  • Authority
  • Memory
  • Pipeline
  • Calendar
  • Knowledge
  • Command
  • Awareness

Settings currently includes these sections:

  • General
  • LLM
  • Channels
  • Integrations
  • Sidecar

The high-level home view. Use it to get a quick sense of whether the system is healthy and what JARVIS has been doing recently.

This is the main conversational surface. Messages stream live, tool work can appear mid-turn, and voice input/output is integrated into the same session.

Use Chat when you want:

  • A direct request answered
  • A tool-driven task performed
  • A delegated research or coding task run
  • A workflow or goal created from natural language

The goals area is where JARVIS tracks longer-running objectives, milestones, and day-to-day accountability.

This is the automation builder and execution monitor. It is where you create event-driven flows and inspect what they did.

Sites is the web-project workspace built into JARVIS. It lets you open projects, run dev servers, inspect files, and work on site code through the dashboard experience.

The Agents page shows delegated activity and gives visibility into specialist work handled by the multi-agent system.

Tasks reflect commitments and active work items. If JARVIS auto-creates or updates work, this is one of the first places to look.

Authority is where you inspect approvals, rules, and audit-trail-adjacent behavior. If JARVIS is asking for permission or being blocked, start here.

Memory lets you inspect the raw vault layer: what JARVIS has stored and what it may later retrieve.

The content pipeline page is used for multi-step content creation and review flows.

Calendar surfaces calendar-related information and integrations exposed by the daemon.

Knowledge is the graph-style view into remembered entities, facts, and relationships.

Command is useful when you want operational visibility into system behavior and recent execution flow.

Awareness shows live context, suggestions, and activity history generated by the awareness system.

The dashboard sidebar shows whether the WebSocket connection to the daemon is currently online or disconnected.

If the dashboard says disconnected:

  • Check that jarvis status shows the daemon as running
  • Confirm you are opening the correct host and port
  • If you are reverse-proxying the dashboard, make sure WebSocket upgrades are forwarded correctly
  • See Troubleshooting

If you serve the dashboard behind Nginx, Caddy, Cloudflare, or another reverse proxy:

  • Forward normal HTTP traffic to the daemon port
  • Forward /ws with WebSocket upgrade headers intact
  • Use a stable external hostname for the dashboard
  • If auth is enabled, make sure cookies and headers are preserved properly

Video tutorial placeholder: dashboard tour and navigation walkthrough.

Add your future video link here.