Usage capture follows you through the whole project
Automatic agent usage capture no longer depends on the folder where a session happens to finish. Claude Code, Codex, and Mistral Vibe can now end at the project root, inside a nested app or package, or in an isolated worktree created by Pekan, and the same project recorder is resolved safely. This fixes missing telemetry and module-not-found diagnostics after an agent changes directories during its work.
Project setup now writes a small launcher alongside the existing recorder and registers a shell-safe command that works with Windows drive paths, spaces, Unicode, PowerShell, cmd, and POSIX shells. The launcher accepts only the configured project recorder or a verified Pekan worktree shim, so an unrelated parent directory cannot substitute its own script. Resolver and import failures remain nonfatal to the agent session and report only the relevant stage and project path.
Running Repair setup replaces older relative hooks and hooks left behind after a project moves, while preserving unrelated user and plugin hooks. Turning usage capture off removes both old and current Pekan hook forms. The setup health view recognizes configurations that need this migration and gives an actionable repair message. Existing retry queues and stable run identifiers continue unchanged.
Highlights
- Usage capture works from nested project folders.
- Pekan-created isolated worktrees keep using the source recorder.
- Repair setup migrates old and moved hook configurations safely.
- Launcher failures never fail the agent session.