bootspring_dashboard

Get dashboard status, start the dashboard server, or get the URL.

Overview

The bootspring_dashboard tool manages the Bootspring real-time dashboard. The dashboard provides a visual interface for monitoring project status, viewing todo lists, tracking workflows, and more.

Parameters

ParameterTypeRequiredDescription
actionstringNoAction to perform (default: status)

Actions

ActionDescription
statusCheck if dashboard is running
urlGet the dashboard URL
startStart the dashboard server
stopStop the dashboard server

Usage Examples

Check Status

Use the bootspring_dashboard tool with: - action: "status"

Response (running):

Loading code block...

Response (stopped):

Loading code block...

Get URL

Use the bootspring_dashboard tool with: - action: "url"

Response:

http://localhost:3456

Start Dashboard

Use the bootspring_dashboard tool with: - action: "start"

Response (success):

Loading code block...

Response (already running):

Loading code block...

Response (failed):

Loading code block...

Stop Dashboard

Use the bootspring_dashboard tool with: - action: "stop"

Response (success):

Loading code block...

Response (not running):

Loading code block...

Configuration

Configure the dashboard port in bootspring.config.js:

Loading code block...

Dashboard Features

The real-time dashboard provides:

Project Overview

  • Project health status
  • Current development phase
  • Open issues count

Todo Management

  • View pending and completed todos
  • Mark items complete
  • Add new tasks

Workflow Tracking

  • Active workflow progress
  • Step-by-step guidance
  • Checkpoint status

Agent Activity

  • Recent agent invocations
  • Suggested agents
  • Agent response history

Quality Metrics

  • Lint status
  • Test coverage
  • Type errors

CLI Integration

The dashboard can also be started via CLI:

Loading code block...

Technical Details

Process Management

  • Dashboard runs as a detached process
  • Survives terminal closure
  • Uses unref() for independent lifecycle

Port Detection

  • Checks if port is already in use
  • HTTP health check for status detection
  • 1 second timeout for port checks

Startup Sequence

  1. Check if already running
  2. Spawn Node.js process
  3. Wait 1 second for startup
  4. Verify server is responding

Error Handling

Port in Use

If the port is already in use by another application:

Loading code block...

Solution: Change the port in configuration or stop the conflicting process.

Permission Denied

If the port requires elevated permissions (ports < 1024):

Loading code block...

Solution: Use a port above 1024 or run with elevated permissions.

Best Practices

Keep Dashboard Running

Start the dashboard at the beginning of your development session for real-time monitoring.

Use Status Checks

Before starting, check status to avoid duplicate processes.

Configure Port

If port 3456 conflicts with other services, configure a different port.