Skip to content

consult 0.16.0: per-project worker fences

Choose a tag to compare

@NoCritics NoCritics released this 03 Nov 22:59
· 8 commits to main since this release

Added

  • A fence per worker, per project. In the Delegated tab's settings ("Fences (this project)"): Codex fenced or full access; agy and the local worker stay in folder or anywhere. Lifting one shows a warning before Save. Nothing else can set a fence: no tool, and not consult.local.md.
  • Markers where it matters. The band leads a running task's row with unfenced when its fence is lifted; the tab's task notes read full access, anywhere or not fenced; the settings line shows e.g. codex full access.
  • Start and result notes. The start reply says the fence is lifted, and an unfenced worker is asked to list the files it changed outside the folder, which the result tells Claude to name.

Changed

  • A task keeps the fence it started with. Every run (first, resume, follow-up) uses the stricter of that and the project's current setting.
  • Codex at full access runs write tasks with danger-full-access; read tasks stay read-only. agy and the local worker at anywhere are no longer asked to stay in the folder.

Install

Claude Code:

/plugin marketplace add NoCritics/consult-plugin
/plugin install consult@nocritics

Claude Desktop: download consult-0.16.0.mcpb below, then Settings → Extensions → Advanced → Install extension.

Full history in CHANGELOG.md.