screenpipe-cli

Run doctor, then service install, then status using the screenpipe CLI. The service install command defaults to recorder mode with screen and audio capture launched at login, and doctor reports any macOS permission issues to resolve first.

Use the search command with flags like --start, --content-type, --app, and --json for structured output. For repeated or SQL reads, use the MCP query_recordings tool or the daemon's read-only raw_sql endpoint instead of touching the database directly.

Yes, the CLI works on macOS, Linux, and Windows. It always runs under bash, using the bundled git-portable bash on Windows, and mktemp is available on all three platforms.

Some agents like Codex block shell network access, so bun x cannot fetch the package and calls to localhost:3030 fail. In that case, use the screenpipe MCP tools instead of the CLI.

No, never access live db.sqlite, db.sqlite-wal, or db.sqlite-shm files directly. Use the search command, the MCP query_recordings tool, or the authenticated raw_sql endpoint on the local API instead.

Create a pipe.md with an 'at <RFC3339 timestamp>' schedule in its YAML frontmatter. The pipe fires once at that time, then auto-disables itself while remaining on disk as history.