Read-only free-disk-space verb (ungated) for recorders and long runs

by adom

Adom Bridge unleashes your AI onto your full PC: full power, full safety. The AI breaks out of the container it runs in and onto your real machine, managing and running your entire laptop as you: launch apps, move files, drive any window, control KiCad, Fusion 360 or your real signed-in browser. Works with any AI, cloud or local (Claude Desktop, Claude Code, Codex), no Hydrogen required. Bridge and its bridges are an operating system for AI, with managed Node and Python runtimes, and a human-onl

Overview Files Skills Discover Packages Releases Dependencies Issues20 Breadcrumbs Pull Requests1 Activity

Closed feature request

John Lauer · 1mo ago ·closed by John Lauer

adom-aiflow starts a window recording per step of a board run and wants to refuse a clip when the recording drive is nearly full, so a run never fills the box's disk. Today the only way to read free space through ab is shell_execute (Tier 2, human permission plus a reason each call), which cannot sit inside an automated step. Ask: a read-only, ungated verb such as desktop_disk_free {path?} returning {drive, freeBytes, totalBytes} for the drive holding the recordings folder (and any given path), like desktop_record_status is ungated. Until then aiflow checks the run drive locally and treats the box's free space as unknown.

2 Replies

John Lauer · 1mo ago

Ack: desktop_disk_free {path?} lands in 2.1.127 (building now). Read-only, ungated; default path is the native recorder's output folder; returns {drive, freeBytes, availableBytes (quota-aware, what this user can still write), totalBytes, freePercent, recordingsDir}. Any path works, existing or not (nearest existing ancestor's volume). Live output follows with the ship.

John Lauer · 1mo ago

Shipped in 2.1.127 (insiders): desktop_disk_free {path?}, read-only and ungated. Live on arav-rog: {drive:"C:", freeBytes:1803451748352, availableBytes:1803451748352, totalBytes:2018737721344, freePercent:89.3, recordingsDir:"C:\Users\arav\AppData\Local\Temp\adom-bridge-recordings"}. availableBytes is the quota-aware figure for the current user; the default path is the native recorder's output folder; a path that does not exist yet resolves to its nearest existing ancestor's volume, and a drive that does not exist answers a plain error (D: on arav-rog: 'The system cannot find the path specified'). Also in the CLI help map and the adom-bridge-recording skill.

John Lauer closed this · 1mo ago