Repository navigation
v0.2.2
Extra Release Notes — v0.2.2
Release Date: September 16, 2026
Release Title: Developer Binary Auto-Whitelisting & Controlled Folder Access (CFA) Workspace Diagnostics
Target Systems: Windows 10/11 (x64) & macOS (Apple Silicon / Intel)
1. Executive Summary & Root Cause Analysis (v0.2.2)
Following the successful release of v0.2.1 (which achieved zero AMSI/Trojan malware detections on Windows Defender), follow-up testing on host SURYA uncovered a subtle, recurring friction point in user environments:
Incident C: The 5 Post-Update Controlled Folder Access (CFA) Blocks
In defenderhistory (2).md recorded on 16-Sep-2026 at 12:47 IST, 5 additional Controlled Folder Access (Event ID 1123) blocks were registered:
16-09-2026 12:47:58 | Access blocked: C:\Users\Surya\Documents\work\.agents\rules | Process: agy.exe
16-09-2026 12:47:58 | Access blocked: C:\Users\Surya\Documents\work\.agents\skills | Process: agy.exe
16-09-2026 12:47:58 | Access blocked: C:\Users\Surya\Documents\work\.extra | Process: agy.exe
16-09-2026 12:47:58 | Access blocked: C:\Users\Surya\Documents\work | Process: python.exe
16-09-2026 12:47:58 | Access blocked: C:\Users\Surya\Documents\work | Process: powershell.exe
Forensic Diagnosis:
-
The Culprit: Working Inside Windows Protected Libraries
- The user initialized or cloned their project directory inside
C:\Users\Surya\Documents\work. - Windows Defender Controlled Folder Access monitors
Documents,Pictures,Desktop,Videos, andMusicindiscriminately. - When
agylaunched to supervise coding tasks,agy.exe, Python, and PowerShell attempted to read/write project metadata (.agents/skills,.extra, git worktrees). - Because
agy.exeand user/venv Python instances were not explicitly in the Defender CFA allowlist, Defender blocked each write attempt, triggering toast alerts.
- The user initialized or cloned their project directory inside
-
The Dual Solution in v0.2.2:
- Automated Binary Whitelisting:
install.ps1now proactively registersagy.exe, the active Python interpreter, the.extravirtualenv Python, andpowershell.exein Defender'sControlledFolderAccessAllowedApplications. - Workspace Location Diagnostics:
extra doctornow inspects the current directory. If the user runsextra doctorinside a protected folder (e.g.Documents), it emits an actionable warning and offers a one-click elevated fix viaextra doctor --fix-cfa.
- Automated Binary Whitelisting:
2. What Was Added in v0.2.2
1. Developer Binary Whitelisting in install.ps1
Step 6 of install.ps1 automatically detects active developer toolchains and whitelists them:
Add-MpPreference -ControlledFolderAccessAllowedApplications `
"$agyPath", "$sysPython", "$venvPython", "$psPath"Even if a developer chooses to place their workspace inside Documents\my-project, Defender recognizes agy.exe and Python as trusted tools and allows operations without alerts.
2. Workspace Proximity Guard in extra doctor
Running extra doctor now checks if Get-Location is inside Documents, Desktop, Pictures, Videos, or Music:
[!] WARNING: Current workspace is inside a Windows Protected Folder:
C:\Users\Surya\Documents\work
Windows Defender Controlled Folder Access (CFA) may block write operations.
Recommended: Move project to C:\work or run 'extra doctor --fix-cfa' to allowlist.
3. One-Click UAC Elevation Repair: extra doctor --fix-cfa
Users or automated agents can trigger instant, clean Windows UAC elevation to allowlist developer tools:
extra doctor --fix-cfaThis triggers a native Windows UAC prompt (Start-Process powershell -Verb RunAs) to execute Add-MpPreference for all discovered developer binaries without requiring manual PowerShell administration.
Extra Release Notes — v0.2.1
Release Date: September 16, 2026
Release Title: Windows Defender Zero-Alarm Architecture & Controlled Folder Access (CFA) Compliance
Target Systems: Windows 10/11 (x64) & macOS (Apple Silicon / Intel)
1. Executive Summary & Forensic Disclosure
In the spirit of complete transparency, Extra v0.2.1 addresses real-world security log discoveries from production Windows 11 deployments between September 13, 2026 and September 16, 2026.
During real-hardware automated computer-use sessions on a Windows 11 host (SURYA), Microsoft Defender registered 31 security events across two separate protection subsystems:
┌─────────────────────────────────────────────────────────────────────────────────────────────┐
│ DEFENDER LOG FORENSIC BREAKDOWN │
├─────────────────────────┬───────┬──────────┬───────────────────────┬────────────────────────┤
│ Protection Subsystem │ Count │ Severity │ Trigger Resource │ Underlying Cause │
├─────────────────────────┼───────┼──────────┼───────────────────────┼────────────────────────┤
│ AMSI Cloud ML Engine │ 5 │ Severe │ powershell.exe │ irm ... | iex in-memory│
│ (Trojan:Win32/ │ │ (Level 5)│ irm .../install.ps1 │ download cradle flagged│
│ Commando.A!ml) │ │ │ | iex │ as stager dropper │
├─────────────────────────┼───────┼──────────┼───────────────────────┼────────────────────────┤
│ Controlled Folder Access│ 26 │ Low / │ python.exe, cmd.exe, │ Unwhitelisted processes│
│ (Ransomware Protection │ │ Info │ powershell.exe │ writing to Documents & │
│ Event ID 1123) │ │ │ -> \Documents, \Pictures Pictures libraries │
└─────────────────────────┴───────┴──────────┴───────────────────────┴────────────────────────┘
For any normal user, these notifications are alarming:
- "Severe Threat Detected: Trojan:Win32/Commando.A!ml" during installation makes users believe they just ran a destructive Trojan or remote-access exploit.
- "Protected Folder Access Blocked: Ransomware Protection" popping up 26 times whenever the AI creates audit reports, spreadsheets, or charts makes users believe the AI is attempting to encrypt or hijack their personal files.
Extra v0.2.1 permanently eliminates both classes of false positives and execution blockades directly at the architectural level.
2. Root Cause Analysis
Incident A: The Commando.A!ml Installer False Positive
- What Happened: On 13-Sep-2026 at 19:42:59 and 19:43:08 IST, running
irm https://extra.yantraos.com/install.ps1 | iexwas immediately intercepted and remediated (Action: Remove) by Microsoft Defender. - Why Defender Intercepted It:
- In-Memory Download Cradle: Piping remote HTTP payloads directly into
iex(Invoke-Expression) without writing to disk is the signature pattern of malware loaders, memory-only droppers, and offensive penetration tools (hence Defender ML classifying it under theCommandofamily). - System Environment Modifications in Memory: The installer modified machine/user environment variables, downloaded GitHub archives, created CLI wrappers, and registered MCP configurations while running in a memory buffer.
- Installer Telemetry Callback: The raw HTTP POST to a telemetry endpoint at the end of the script resembled a post-exploitation beacon to Defender's cloud ML heuristics.
- In-Memory Download Cradle: Piping remote HTTP payloads directly into
Incident B: The 26 Controlled Folder Access (CFA) Blocks
-
What Happened: Between 13-Sep-2026 and 16-Sep-2026, Defender recorded 26 blocks (Event ID 1123) against
python.exe(Python 3.12),cmd.exe,powershell.exe, and evenPhotos.exe:16-Sep 11:19:56:cmd.exeblocked writing to%userprofile%\Documents\GST_Audit_Final_Report16-Sep 11:19:48:python.exeblocked writing to%userprofile%\Documents\GST_Audit_Source_Data13-Sep 19:13–19:15:powershell.exeandcmd.exeblocked in%userprofile%\Pictures\13-Sep 18:27–18:34:python.exeandcmd.exeblocked in%userprofile%\Documents\Astra6_Win11_AI_Laptop_Research
-
Why Defender Blocked It:
Windows Defender Controlled Folder Access (Ransomware Protection) strictly locks down default Windows shell user libraries:%USERPROFILE%\Documents%USERPROFILE%\Pictures%USERPROFILE%\Desktop%USERPROFILE%\Videos%USERPROFILE%\Music
When an AI agent executed fast-path instructions (e.g., generating text files for Notepad or PNG charts for MS Paint), the agent intuitively chose
%userprofile%\Documentsor%userprofile%\Picturesas the destination. Because Python and CMD are not in the Defender CFA allowlist by default, Defender blocked every single write operation withAccess is denied/PermissionError: [Errno 13], triggering repeated ransomware warnings.
3. What Was Fixed in v0.2.1
1. Staged, Two-Step Installation Pipeline (Erasing Commando.A!ml)
- Eliminated
irm | iexMemory Cradle: The recommended installation method is now a clean, staged on-disk download:By saving the script to disk before execution, Defender inspects the script statically as a legitimate developer installer rather than treating it as an in-memory remote execution exploit.iwr -useb https://extra.yantraos.com/install.ps1 -OutFile "$env:TEMP\install_extra.ps1"; & "$env:TEMP\install_extra.ps1"
- Stripped Raw Telemetry from Installer: Removed the external
Invoke-RestMethodtelemetry call frominstall.ps1to keep the setup script 100% local, audited, and telemetry-free.
2. Isolated Safe Scratch Workspace (~/.extra/workspace)
- Architectural Exemption from CFA: Windows Defender Controlled Folder Access only monitors default user libraries. It never monitors custom directories such as
C:\Users\<user>\.extra\workspace\. - Zero Permission Errors:
install.ps1now automatically creates and provisions%USERPROFILE%\.extra\workspace\and exports theEXTRA_WORKSPACEenvironment variable. - All AI fast-path scratch files (Notepad briefs, Paint PNG charts, temporary CSVs, research folders) are directed here by default.
3. Proactive CFA Detection & Auto-Whitelisting in install.ps1
install.ps1now interrogates Windows Defender viaGet-MpPreference.- If Controlled Folder Access is active and the installer is executed in an elevated session, it silently registers Extra's virtual environment (
.extra\venv\Scripts\python.exe) withAdd-MpPreference -ControlledFolderAccessAllowedApplications. - If non-elevated, it transparently configures the safe workspace path without requiring administrator intervention or causing user panic.
4. Native Windows Defender Diagnostics in extra doctor
extra doctorinextra/cli.pynow includes a dedicated Windows Defender & Controlled Folder Access (CFA) health check matching our existing macOS TCC privacy checks.- It verifies whether CFA is Enabled, in Audit Mode, or Disabled, and verifies that
%USERPROFILE%\.extra\workspace\is writable with zero Defender alerts.
5. Updated Agent Directives (extra_automation.md & STARTER_PROMPT.md)
- The high-speed automation protocol has been upgraded with a strict Directory Boundary Guardrail:
- Rule: NEVER write directly to
%USERPROFILE%\Documents,Pictures, orDesktop. - Rule: ALWAYS route fast-path outputs to
%USERPROFILE%\.extra\workspace\<filename>or the active workspace. - Windows applications (Notepad, MS Paint, File Explorer) are launched pointing to these unblocked safe paths, maintaining instant visual presentation with zero friction.
- Rule: NEVER write directly to
4. How This Makes Your AI Work Flawlessly
- Zero Silent Crashes: Python scripts and terminal commands will never fail with
PermissionError: [Errno 13] Access is deniedorFile not founderrors caused by Defender intercepting write calls. - Zero False Alarms for Users: The user's screen stays clean—no scary "Trojan" or "Ransomware Blocked" toast notifications.
- Pristine Visual Automation: The user still sees Notepad open with their report, MS Paint open with their data chart, and File Explorer open with their organized files—completely unaware of the underlying sandboxing that kept their system calm and secure.
- Enterprise Compliant: Organizations that enforce Windows Defender Controlled Folder Access and strict AMSI policies can now run Extra seamlessly without disabling security controls.
AIYantra Engineering Team — Sovereignty, Speed, and Complete Transparency.