Yes or No
"Yes or No?" Watch on YouTube →
"Yes or No?" Watch on X →
Yes or No Setting: Permission Before Action
MCPs are powerful. They let Aquin open URLs, launch apps, access your clipboard, manage files, search browser history, and automate Google services.
But power should require permission.
Before Aquin uses any MCP, it asks you: Yes or No?
- You: "Open the budget spreadsheet from my Drive"
- Aquin: "This requires Google Drive access. Allow?"
- You: "Yes"
- Aquin: Accesses Drive and opens file
Every MCP action becomes a conscious choice of yours.
MCPs:
- URL Opener
- App Launcher
- Clipboard
- File System
- Browser History
- Google Drive
- Google Meet
- Google Calendar
- Gmail
Why?
-
Prevent Accidents: No more accidental file deletions or unintended emails.
-
Stay Aware: Know exactly when AI accesses sensitive data.
-
Build Trust: Conscious control over every privileged action.
-
Learn Patterns: Understand which MCPs you actually use.
Yes/No Enabled
Every MCP action requires explicit permission. Maximum control, maximum awareness.
Yes/No Disabled
MCPs work automatically when enabled. Maximum speed, trusted environment.
Toggle it through settings window anytime.
Scenarios:
Sensitive Work: Enable Yes/No when working with confidential files, client data, or personal information.
Trusted Sessions: Disable Yes/No during routine work when you trust the AI's actions.
Learning Phase: Keep Yes/No on while learning what each MCP does.
Presentation Mode: Enable Yes/No before screen sharing to prevent unexpected actions.
The Philosophy
AI should be powerful but never presumptuous. Yes or No Setting ensures Aquin never takes action without your explicit consent.
Ask permission. Respect the answer. Repeat.
Permission-based AI. The way it should be.

