		@@ -18,3 +18,3 @@ /**

		Written for @clipy/cli + @clipy/mcp 0.8.5 (the two versions move in lockstep). If
		Written for @clipy/cli + @clipy/mcp 0.8.6 (the two versions move in lockstep). If
		\`clipy --version\` reports older, upgrade first: \`npm i -g @clipy/cli@latest\`.
		@@ -206,4 +206,4 @@
		those are reserved for marks Clipy itself checked, so a skim tells the two apart
		by shape before you read a word. Both
		flags are required together, and a mark carries exactly ONE provenance — combining
		by shape before you read a word. Both flags are required together, and a mark
		carries exactly ONE provenance — combining
		them with --assert-* is a usage error. Works in EVERY session type, including
		@@ -374,13 +374,2 @@ \`--source mac-screen\`.
		auto-stops at 1800s).
		- AUDIO: agent screen recordings do NOT capture the microphone. Default is system
		audio ON, mic OFF — an agent recording on someone's behalf is not the same
		consent as that person clicking Record, and nobody asked for the room (or
		whatever call they're on) to be recorded; your narration rides on marks, not
		speech. \`--mic\` opts in, \`--no-system-audio\` opts out of system audio. Both
		are mac-screen only (headless captures are silent — passing them on the web path
		is a usage error). The resolved config is printed (\`audio: system on, mic off\`)
		and returned as a sibling \`audio\` in --json. If the Clipy app is too old to
		handle audio control it will NOT echo a config back, and the CLI warns that the
		app's own defaults are in force and the mic may be recording — believe the
		warning and update the app.
		- If a human presses Stop inside the app during your session, \`session stop\` /
		@@ -391,2 +380,32 @@ \`mark\` return a \`stopped_from_app\` error — the recording was already uploaded

		### THE MICROPHONE IS OFF BY DEFAULT — KEEP IT THAT WAY UNLESS ASKED

		Agent screen recordings do NOT capture the microphone. The default is system audio
		ON, mic OFF, and that asymmetry is deliberate: system audio captures the machine,
		the mic captures the ROOM. A person clicking Record chose to be heard. You starting
		a recording on their behalf is not that same consent, and nobody asked for their
		call, their kitchen, or whoever else is nearby to be on a shareable link. Your
		narration rides on marks, not speech, so the mic buys the recording nothing by
		default.

		- \`--mic\` opts in. Only pass it when the user asked for their voice in the
		recording — treat it as an instruction to obtain, never a default you restore
		because audio "seems better".
		- \`--no-system-audio\` opts out of system audio.
		- Both are \`--source mac-screen\` ONLY. Headless web captures record no audio at
		all, so passing either on the web path is a usage error (exit 2) rather than a
		silently ignored flag.

		The resolved config is printed (\`audio: system on, mic off\`) and returned as a
		sibling \`audio\` object in \`--json\`. Read it rather than assuming your flags won:

		- If the Clipy app is too old to control audio, the CLI warns BEFORE recording
		starts that the app's own defaults are in force and the mic may be live.
		- If the app claims audio control but never confirms what it applied, you get the
		same warning after start.

		Either way the warning means the same thing: WE DO NOT KNOW that the mic is off.
		Believe it, tell the user, and update the app — do not report a recording as
		mic-free on the strength of the flag you passed.

		## Rules for recording (follow strictly)
		@@ -393,0 +412,0 @@

+1

-1

package.json

		{
		"name": "@clipy/cli",
		"version": "0.8.5",
		"version": "0.8.6",
		"description": "Command-line interface for Clipy — list, search, and read your screen recordings' transcripts, AI summaries, and key moments from the terminal.",
		@@ -5,0 +5,0 @@ "license": "MIT",

+9

-4

README.md

		@@ -365,3 +365,3 @@ # @clipy/cli
		```text
		[verification] 2 clipy-verified: 1 passed, 1 failed, 1 unverified · 3 driver-attested: 2 passed, 1 failed
		[verification] 3 clipy-verified: 1 passed, 1 failed, 1 unverified · 3 driver-attested: 2 passed, 1 failed
		```
		@@ -465,6 +465,11 @@
		passing them on the web path is a usage error. The resolved config is printed
		(`audio: system on, mic off`) and returned as a sibling `audio` field in `--json`. If your
		Clipy app predates agent audio control it won't echo a config back, and the CLI warns that
		the app's defaults are in force and your mic may be recording — update the app.
		(`audio: system on, mic off`) and returned as a sibling `audio` field in `--json`.

		Two things can go wrong, and both fail closed toward "assume the mic is live". If your Clipy
		app is too old to control audio at all, the CLI says so before recording starts — the
		timing is the point, since a warning printed after the fact is an autopsy on a mic that was
		already open. If a new-enough app never confirms what it applied, you get the same warning
		after start. Either way the message means we do not know that the mic is off: believe it
		and update the app rather than trusting the flag you passed.

		`--window` takes a window id from `clipy sources`, or an app/title substring
		@@ -471,0 +476,0 @@ (case-insensitive; ambiguous matches list the candidates instead of guessing).

dist/index.js

Sorry, the diff of this file is too big to display

@clipy/cli - npm Package Compare versions

New alerts

Fixed alerts

Improved metrics