Skip to content

[Epic] Coordination primitives — delegate goals, not one-shots (Coder as first consumer) #154

Description

@serge-ivo

Make agent coordination correct — as a platform primitive Coder is the first consumer of, NOT a refactor of Coder's hardcoded internals. Design: docs/coordination-primitives.md. Companion to agent-platform-strategy.md + connector-manifest.md (#143).

Problem (verified): the Overseer (drive_claude) and send_to_cli are fire-and-forget one-shots — no follow-through, no typed task/status, three overlapping drive-paths, and the console Loop is client-driven (dies when the tab closes) while the durable Pilot (CodingSessionWorkflow) overlaps it.

What stays (best practice, keep): Engine=executor / brain=decider; deterministic target routing (repo → one active session → live node); per-instance isolation; declarative consent-gated tools. This is not a rewrite — only the coordination policy on top changes.

Principle: delegate at the right abstraction, through a durable handoff. Commands → Engines; goals → autonomous workers (Pilot, later another agent) that own loop/retry/escalate; the coordinator delegates goals and tracks status.

We build ONE thing now (the fix as the primitive) and defer the generalizations until they have a proven primitive and/or a real second consumer — avoiding both "polish the hardcoded thing" and "build the framework too early."

Metadata

Metadata

Assignees

No one assigned

    Labels

    backendBackend / Worker / API workcoordinationAgent coordination / delegation primitives

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions