A developer working beneath an apple tree as an apple drops nearby

Pre-release Context continuity for AI-assisted coding

Governed Vibes

Keep the context.
Keep your momentum.

A Codex plugin in development for builders who are tired of burning session limits re-explaining the same project.

Current focus Carry the accepted state forward without replaying the whole project.

The context tax

A new task should not mean starting the project over.

Long conversations become expensive. Fresh conversations lose the decisions that made the work coherent. Governed Vibes is being built around a smaller, durable handoff.

01

Relevant context

Restore the accepted facts and unresolved decisions a task actually needs.

02

Bounded authority

Make the role, allowed surface, tools, and stopping conditions explicit.

03

Clean handoffs

Carry evidence and the next legal action forward without another full retelling.

A compact control loop

Enough state to continue. Not another transcript dump.

Each task begins with a small, explicit capsule: what is true, what is allowed, what remains unresolved, and what should happen next.

control-state.json bounded
{
  "task": "Add inspection endpoint",
  "status": "in_progress",
  "authority": ["src/data-service/**"],
  "must_not": ["src/ui/**", "push"],
  "evidence": ["focused tests: 18/18"],
  "next": "Independent review"
}
  1. 1
    PlanChoose the bounded action.
  2. 2
    AuthorizeState the exact authority.
  3. 3
    ExecuteWork inside the boundary.
  4. 4
    ReviewInspect the delivered bytes.
  5. 5
    ReconcileAdvance accepted state.

The governing idea

Capability is not authority.

Agents can propose. Humans decide.

The current role receives only the authority needed for the current action.

Context is selected, not sprayed.

Relevant accepted state beats loading an entire conversation into every task.

Failures stop cleanly.

Missing authority, stale state, or conflicting instructions trigger a handoff.

Build path

A small useful plugin first.

The first release is intentionally narrow: make context continuity useful on its own, then let the larger governed workflow grow around proven behavior.

  1. Now

    Control state

    Model tasks, authority, evidence, review, and clean continuation.

  2. Next

    Durable context

    Store reviewed state and return only the context relevant to the next task.

  3. Then

    Open plugin client

    Bring the workflow into Codex through a focused, testable interface.

Built in public

The plugin client is planned as open source.