chieflab_status

Active

declared in 0.3.0

SESSION-RECOVERY · FIRST CALL when a session starts and the user mentions launch / users / growth / customers / metrics / revenue / marketing / what next / shipping. Returns a command-center bootCard with `headline`, `priority`, `cards[]` (each carries kind + label + literal user command + runHandle), and `next` (the one-line prompt). Aggregates: pending approvals + ripe measurements + new engagement + queued prospects + recent launches + manual-publish-pending actions. ChiefLab is stateful and re-summonable — even if the conversation was lost, the IDE was switched, or the runId was forgotten, this call recovers the workspace business state. If the user asked to launch the CURRENT repo, compare boot cards to currentRepoContext/projectName; if the open loop is unrelated, start a fresh launch instead of resuming stale work.

Parameters schema

{
  "type": "object",
  "properties": {
    "projectName": {
      "type": "string",
      "description": "Optional current project/repo name."
    },
    "workspaceId": {
      "type": "string",
      "description": "Optional workspace id."
    },
    "currentRepoContext": {
      "type": "object",
      "description": "Optional current repo/project context. Helps agents compare recovered loops against the project the user is asking about."
    }
  }
}

What this tool wraps· 0 endpoints

min confidence0.70 0.50

No endpoints wrapped at confidence ≥ 0.50.

Parent server

ChiefLab

https://github.com/bdentech/chiefmo-agent

1/7 registries

View full server →