@detergent-software/conductor 3.0.0-dev.1 → 3.0.0-dev.2

package/CHANGELOG.md

@@ -2,6 +2,12 @@
 
 Releases are tagged `conductor-v<version>` and staged on npm by `atk-conductor-release` (`pipelines/release-conductor.yml`), which writes each section below. `scripts/check-changelog.mjs` fails when a tag has no section here.
 
+## [3.0.0-dev.2](https://emergentcode.visualstudio.com/Emergent%20Software/_git/Emergent.AgenticToolkit/branchCompare?baseVersion=GTconductor-v3.0.0-dev.1&targetVersion=GTconductor-v3.0.0-dev.2) (2026-10-17)
+
+### Documentation
+
+* **conductor:** say the first console asks to trust its folder (ATK-525) ([8d9e37d](https://emergentcode.visualstudio.com/Emergent%20Software/_git/Emergent.AgenticToolkit/commit/8d9e37de5b37807bfab5fb7a94903be868513d6a))
+
 ## [3.0.0-dev.1](https://emergentcode.visualstudio.com/Emergent%20Software/_git/Emergent.AgenticToolkit/branchCompare?baseVersion=GTconductor-v2.2.0-dev.3&targetVersion=GTconductor-v3.0.0-dev.1) (2026-10-17)
 
 ### ⚠ BREAKING CHANGES

package/README.md

@@ -718,7 +718,7 @@ conduct console          # a tab in Windows Terminal (window "conductor"), in ~/
 conduct console --here   # the same session in this terminal
 ```
 
-It writes the plugin copy if none exists yet (see Plugin), then runs `claude --plugin-dir <home>/plugin -n conductor --permission-mode auto -- /conductor:conductor-console` with `CONDUCTOR_CONSOLE=1`. A background session started in that new folder ran with no trust prompt (ATK-525); the first interactive one may still ask. The skill starts the daemon if it isn't running (`conduct start`, detached, so it doesn't end with the session), then handles what waits.
+It writes the plugin copy if none exists yet (see Plugin), then runs `claude --plugin-dir <home>/plugin -n conductor --permission-mode auto -- /conductor:conductor-console` with `CONDUCTOR_CONSOLE=1`. The first console in that folder asks Claude Code to trust it once, and the mod's band and the console's stream start only after you accept; background sessions there run with no prompt (ATK-525). The skill starts the daemon if it isn't running (`conduct start`, detached, so it doesn't end with the session), then handles what waits.
 
 **Escalations.** A rule's `escalate console "<ask>"` appends `console.escalated` (the default `conductor-handoff` does it for a worker's `Handoff · conductor` note). The mod wakes the model with `[conductor] escalation #<id> on <item>: <ask>`. The console does the job and reports back with `conduct escalations done <id> "<what it found or did>"`, which logs `console.handled` with the escalation as its cause, so `conduct why <that event>` leads to the rule. With `--ask`, the finding also goes in the inbox as a `console` item, pushed like any other, for something only you can do. `conduct escalations` lists those not yet handled, from the last 14 days, including the ones raised while no console was open; the console reads it when it starts.
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@detergent-software/conductor",
-	"version": "3.0.0-dev.1",
+	"version": "3.0.0-dev.2",
 	"description": "Conductor: the local daemon that runs conducted projects' work loops (conduct serve) and its conduct CLI.",
 	"type": "module",
 	"bin": {