Overseer Docs
Interfaces

Web Dashboard

Built-in web admin interface

Web Dashboard

The web dashboard is the easiest and most complete way to use Overseer.

If you only use one interface, this is the one most people should choose.

Features

  • Real-time Chat — Chat with your agent directly in the browser
  • Conversation History — Browse and search past conversations
  • Per-user Files — Each signed-in user works in their own sandboxed file area
  • Attach Files and Images — Upload files directly in chat
  • @ File Attach — Attach files from your saved Files area right from the composer
  • /skills and /<skill> commands — Discover and use skills from chat
  • Provider Management — Add, configure, and switch LLM providers
  • SOUL.md Editor — Rich Markdown editor for agent personality
  • Skills Manager — Browse, install, and configure skills
  • MCP Connections — Manage MCP server connections
  • Cron Jobs — Schedule prompts and recurring automation
  • Sub-agents — Spawn parallel workers for bigger tasks
  • Super Memory — Persistent long-term memory and memory management
  • Files Page — Upload, browse, preview, rename, and delete user sandbox files
  • Tool Browser — View all available tools and their usage stats
  • System Metrics — CPU, memory, disk, and network monitoring
  • Audit Logs — Real-time system log viewer
  • User Management — Create and manage admin accounts

Why the web dashboard matters

The web dashboard gives you the fullest Overseer experience because it combines:

  • chat
  • admin settings
  • file management
  • user management
  • provider setup
  • interface setup
  • automation and advanced features

In other words, even if you mostly use Telegram, Discord, Slack, WhatsApp, or Matrix, you will probably still come back to the web dashboard for setup and management.

Access

pnpm dev  # Development: http://localhost:3000
pnpm start  # Production: https://your-domain.com

Authentication

The dashboard uses session-based authentication with bcrypt password hashing. Default credentials are set in your .env file:

ADMIN_USERNAME=admin
ADMIN_PASSWORD=your-secure-password
Change the default credentials immediately after first login.

On this page