Relevant context
Restore the accepted facts and unresolved decisions a task actually needs.
Pre-release Context continuity for AI-assisted coding
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.
The context tax
Long conversations become expensive. Fresh conversations lose the decisions that made the work coherent. Governed Vibes is being built around a smaller, durable handoff.
Restore the accepted facts and unresolved decisions a task actually needs.
Make the role, allowed surface, tools, and stopping conditions explicit.
Carry evidence and the next legal action forward without another full retelling.
A compact control loop
Each task begins with a small, explicit capsule: what is true, what is allowed, what remains unresolved, and what should happen next.
{
"task": "Add inspection endpoint",
"status": "in_progress",
"authority": ["src/data-service/**"],
"must_not": ["src/ui/**", "push"],
"evidence": ["focused tests: 18/18"],
"next": "Independent review"
}
The governing idea
The current role receives only the authority needed for the current action.
Relevant accepted state beats loading an entire conversation into every task.
Missing authority, stale state, or conflicting instructions trigger a handoff.
Build path
The first release is intentionally narrow: make context continuity useful on its own, then let the larger governed workflow grow around proven behavior.
Model tasks, authority, evidence, review, and clean continuation.
Store reviewed state and return only the context relevant to the next task.
Bring the workflow into Codex through a focused, testable interface.
Built in public