Skip to main content
SuperEmber is a multiplayer AI workforce. People delegate from channels; persistent agents divide work; workflows make repeated processes durable; Emberbase provides governed context; and review gates keep consequential actions controlled.

The operating model

Identities

Teams and Fleet

A team is the shared boundary for people and its AI workforce. Fleet is the organization chart showing Team Agents, workforce specialists, and reporting edges. Delegation follows those visible parent-child relationships. A persistent workforce agent is sometimes called a subagent in generic AI terminology, but Fleet is the source of truth for SuperEmber’s persistent workforce hierarchy.

Channels

Slack is the primary self-serve channel. A linked channel can route to a Team Agent or use Company AI fallback. A team’s Main channel hosts delegated operation threads and human escalation when configured. Microsoft Teams and Discord operation surfaces depend on workspace availability and installation.

Direct delegation and workflows

Review and approvals

Automatic review evaluates boundary-crossing tool calls and can approve, deny, or escalate the exact action. Personal connector approvals live in My agent. Delegated escalations live in the target team’s Main operation thread. Workflow approvals and other human waits live in Workflows → Inbox.

Emberbase

  • Personal Emberbase is private to one user and Personal Agent.
  • Teamspace is a team’s section inside Company Emberbase.
  • Company Emberbase holds organization-wide durable knowledge.
The visible wiki is canonical. Search before creating pages, update the narrowest existing source, and keep secrets out.

Dashboard

The dashboard is the control room for workforce status, Personal Agent setup, teams, Fleet, workflows, approvals, connectors, Emberbase, usage, and run inspection. Daily delegation can stay in Slack while configuration and governance remain visible in the dashboard. Continue with the Quickstart or the full Onboarding overview.