StackieAlpha Preview

Dashboard

The Stackie dashboard is a browser-based interface for monitoring and controlling your sandboxes.

Opening the Dashboard

The dashboard is opened by clicking View Dashboard in the System Tray.

Stack Designer

Open a stack and use the Definition view to move between three related concepts:

  1. The project is the local folder that bounds dashboard file writes.
  2. The stack YAML is the runtime definition that stackie up parses.
  3. The design canvas is the dashboard editing surface for that YAML.

File-backed stacks can be saved in place when their active YAML path is inside the project root. Built-in catalog stacks are read-only until you create an editable copy; the default copy destination is the project root. Validate checks the current editor buffer without writing it, Save writes a writable file with an optimistic content hash, and Create Copy writes a new project-local YAML file before continuing from that file.

The topology designer lets you drag blocks from the grouped catalog, connect named ports visually, edit stack/block/edge properties, and delete selected nodes or relationships. Runtime structure changes update the stack YAML. Manual canvas positions are design-only metadata saved in .stackie/stack-designer-project.json, so arranging the graph does not change what Stackie runs. The canvas still reads legacy YAML designer positions as a fallback for older files.

The editor distinguishes source state from runtime state. Unsaved means the YAML buffer differs from the last saved source. Layout unsaved means only design metadata is waiting for confirmation. If a saved source differs from a running stack, restart or rerun the stack so runtime state catches up.

S
Stackie v1.2.0
Docs 9
  1. 1

    All your stacks in one place. A stack groups related blocks (services) together — click into any running stack to inspect its blocks, stream logs, and view live resource usage.

  2. 2

    Individual blocks across all stacks — the services that actually run (postgres, redis, node, etc.). Filter by running or stopped to focus on what matters.

  3. 3

    Browse installed packages per block with disk usage. Useful for auditing what's on disk and identifying packages left behind by stopped blocks.

  4. 4

    View the package sources Stackie resolves blocks from — Homebrew, Scoop, npm, pip, and others — along with their resolver status and configured paths.

  5. 5

    Live health check status for every block and daemon subsystem. The first place to look when a block is degraded or failing its readiness probe.

  6. 6

    Configure Stackie preferences: daemon port, update channel, log retention, and other per-machine options.

  7. 7

    MCP server management — active sessions, connected AI agents, registered tools, and authentication tokens for granting remote access to your sandboxes.

  8. 8

    Track download counts and bandwidth against your plan limits. Upgrade or manage your subscription directly from this view.

  9. 9

    Inline documentation browser — explore the block catalog, CLI reference, and stack format without leaving the dashboard.