Granular "feeling safe" control#5045
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces a granular 'feeling safe' mechanism to allow enabling unsafe behaviors selectively. To improve the architecture, avoid using global state for tracking allowed functionalities. Make the DangerousFunctionality class and formatting functions context-aware by passing the Common object (or self) to retrieve options directly. Remove unused global variables, imports, and helper functions like allow_functionalities. Additionally, fix a typo in the TODO path for the local provision plugin and import Common directly under TYPE_CHECKING to avoid re-exports.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
ed3d98f to
30c7fcc
Compare
Instead of one big all-or-nothing switch, finer control over various dangerous action is needed. Users can still allow everything, with `--feeling-safe[=all]`, or allow individual dangerous functionalities.
35b7784 to
79d239e
Compare
79d239e to
482ae37
Compare
|
Caution Review failedAn error occurred during the review process. Please try again later. ✨ 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 |
1 participant
Instead of one big all-or-nothing switch, finer control over various dangerous action is needed. Users can still allow everything, with
--feeling-safe[=all], or allow individual dangerous functionalities.Pull Request Checklist