Skip to content
Supen Docs

Runtime Overview

Supen is designed so the product surfaces do not fragment the work. The platform, CLI, and channels all talk to the same runtime instead of maintaining separate states.

The model in one sentence

Section titled “The model in one sentence”

One runtime, many interfaces.

What sits behind the product

Section titled “What sits behind the product”
  • The daemon provides the runtime
  • The platform provides visibility and management
  • The CLI provides terminal-native access
  • Channels provide external reach for follow-up and collaboration

Why this matters to users

Section titled “Why this matters to users”

You can:

  • start work in the CLI
  • inspect it later in the platform
  • keep watching it through a channel

without recreating the task in three separate tools.

What the runtime owns

Section titled “What the runtime owns”
  • Maintain agent and session state
  • Stream task output
  • Load skills and MCP-backed tools
  • Execute scheduled automations

What the gateway adds

Section titled “What the gateway adds”

When you work with multiple spaces or provisioned environments, the gateway is the layer that helps Supen list, launch, and route between them.

Design intent

Section titled “Design intent”

Supen is built as an operator-facing product first. The API is there to complete the system, but the main experience is still the platform, CLI, and channels.