openclaw - 💡(How to fix) Fix Feature: chief-of-staff orchestration layer for multi-agent workflows [1 comments, 1 participants]

Pattern to steal

Inspired by agent-manager / chief-of-staff style projects (for example, ClawChief-style coordination UX).

Problem

OpenClaw has strong primitives for sessions, cron, memory, browser, tools, ACP runtimes, and subagents, but the user often still has to act like the human orchestration layer.

We need a first-class manager / chief-of-staff layer that can:

• hold a multi-step objective
• delegate named work to specialized lanes
• track who is doing what
• surface blocked vs completed vs waiting states clearly
• keep the user focused on outcomes, not raw agent plumbing

Proposed feature

Add an opinionated orchestration layer above raw sessions/subagents with:

• named roles / lane presets
• explicit delegation and handoff state
• lightweight “who owns what” visibility
• durable objective tracking
• better distinction between planning, execution, review, and follow-up

Why this matters

Today OpenClaw can do the work, but the ergonomics still encourage ad hoc orchestration. A manager layer would make complex, multi-agent work feel like one coherent workflow instead of a pile of sessions.

Acceptance ideas

• define the minimum chief-of-staff object model
• define how objectives, delegates, and blockers are represented
• define how this should integrate with sessions, cron, and memory
• produce a first implementable slice rather than a vague orchestration umbrella