/cd now re-points transcript, settings, hooks and skills in one pass and reports anything left behind.
What's wrong with this entry?
Changing a session's directory, via /cd or through the SDK, now runs a single routine that re-points the transcript, background session state, settings watcher, hooks, skills and the skill watcher. Each step is wrapped individually, so one failure logs and the move continues rather than aborting halfway.
- A failed step reads like
directory move: re-targeting the skill watcher failed (continuing with the previous watch). - The move returns a notice to the model saying the environment block is now stale and that project settings, MCP servers and skills come from the new directory, along with the list of additional directories left behind.
- If the new directory is trusted only through a parent directory's grant, the notice states its project permission rules and additionalDirectories are NOT applied. Explicitly trusting the directory swaps in the trusted wording instead.
- Reported under the existing
tengu_cd_commandtelemetry event.
The user trusted this directory explicitly: its project permission rules and additional directories are now applied.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
A crashing slash command now tells you it crashed
Both mention slash command
-
v2.1.234
A command can decide from its arguments whether it counts as sensitive
Both mention slash command
-
v2.1.234
A slash-command grouping for a command that does not exist
Both mention slash command