(MOT-3898) feat: create new files in the current folder by default#445
(MOT-3898) feat: create new files in the current folder by default#445ytallo wants to merge 1 commit into
Conversation
Point every model-facing instruction at the session working directory: the system-prompt working-directory aid now tells the agent to create new files there, the harness and provider prompts say where new files belong, coder::*/shell::exec contract docs describe scoped relative-path anchoring instead of the primary-root-only wording, and coder::info reports the effective session root.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (28)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
skill-check — worker0 verified, 38 skipped (no docs/).
Four for four. Nicely done. |
New files created without an explicit folder now land in the session's working directory. The path resolution already anchored scoped relative paths there — but every model-facing instruction still pointed at the primary jail root, so agents kept writing files into the worker install path. This fixes the instructions and contract text end to end.
Harness
prompts/default.txtandprompts/cli.txt: the coder routing paragraph gains the same where-new-files-go sentence.Provider prompts
Shell
coder::*function descriptions and the create/move/delete path field docs said "relative to the primary allowed root" — wrong for scoped sessions, where relatives anchor at the session root. Reworded across create/read/search/list-folder/tree/update/move/delete plus theshell::execcwddoc (omitted cwd runs in the session working directory when scoped).coder::infois now session-aware: it accepts the harness-stamped scope (schema-hidden like its siblings) and reportssession_root, so "where may I write?" answers with the session anchor rather than only the jail root.fs_scoperemains absent from every published schema.Tests
session_root_reflects_scope(scoped → canonical echo, unscoped → none, outside-roots → none).Fixes MOT-3898
Refs MOT-3897