docs(agents): fail fast on EROFS - #9
Conversation
- 📝 prevent runaway cleanup retries when sandboxed Trash writes fail
Bugbot couldn't run - usage limit reachedBugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit. A user or team admin can review and increase usage limits in the Cursor dashboard. (requestId: serverGenReqId_fe2e1141-1982-4140-bedb-409b2adec920) |
There was a problem hiding this comment.
Pull request overview
Update the agent documentation so that any cleanup using
trashfails immediately onEROFSand reports the error, rather than retrying indefinitely and potentially burning CPU in sandboxed environments.
This PR updates the agent development guidelines to clarify expected behavior when trash encounters a read-only filesystem (EROFS) during cleanup.
Changes:
- Document “fail fast on
EROFS” behavior fortrash-based cleanup operations. - Explicitly forbid indefinite retry loops in sandboxed cleanup scenarios.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
| Filename | Overview |
|---|---|
| agents/AGENTS.md | The documentation-only change clearly establishes fail-fast behavior for read-only filesystem errors without introducing a concrete defect. |
Reviews (1): Last reviewed commit: "📝 docs(agents): fail fast on `EROFS`" | Re-trigger Greptile
Summary
trashcleanup to fail immediately onEROFSValidation
git diff --checkmise exec github:huacnlee/autocorrect -- autocorrect --lint agents/AGENTS.mdNote
Low Risk
Documentation-only agent guideline; no runtime, security, or data-handling code changes.
Overview
Updates agent CLI guidance so
trashcleanup fails immediately onEROFSand reports the error instead of retrying forever (which can spin CPU in a sandbox).Reviewed by Cursor Bugbot for commit 96035a2. Bugbot is set up for automated code reviews on this repo. Configure here.