v0.9.25
[0.9.25] - 2026-03-12
Changed
- Project scope extraction uses explicit paths only for current message: Contextual nickname matching skipped for current user message to prevent false positives from common English words. Only explicit filesystem paths (
~/foo,/foo,./foo) are extracted. - Primary project scope prefers text order over disk existence: Fixes new-project creation where a false-positive match to an existing directory would override the user's explicit path.
- Scope-lock uses only user-explicit project scope: No longer falls back to
known_project_dirinferred from tool results, preventing history context pollution. - Project dir injection no longer updates
known_project_dir: Prevents parent directory fallback from causing subsequent tool calls to latch onto unrelated projects. http_requestbudget cap raised to 15: Multi-step API workflows legitimately need more sequential calls.- CI workflows bumped to
actions/checkout@v5: Silences Node.js 20 deprecation warning.
Fixed
- New project creation scoped to wrong existing project: Common words in the prompt could match existing project directories, causing the agent to scope-lock and edit files in the wrong project.
- Budget exhaustion logging missing context: Added session/task/iteration details to warnings.
Full Changelog: v0.9.24...v0.9.25