Search team activity in Screenpipe Enterprise and review records by device and time. Preview, deploy, and schedule managed Pipes, which are AI automations, with explicit targets and checks before changes.
Use the native Screenpipe CLI to query Enterprise team activity or safely preview, deploy, and schedule managed team Pipes. Injected only by the Enterprise app for active admins.
Review the instructions the agent will receive before you install.
Use screenpipe team; it reads the admin token and API base from Screenpipe's
Enterprise settings. Never print tokens or read enterprise.json into context.
# Identify a device before searching for one teammate.
screenpipe team devices --raw
# Search first; default to 24h and at most 20 results.
screenpipe team search "TOPIC" --since 24h -n 20 --raw > /tmp/sp-team.jsonl
# Fetch a short chronology only after the device and window are known.
screenpipe team records --device-id DEVICE --since 4h --kind all -n 50 --raw > /tmp/sp-team.jsonl
# Fetch at most 2-3 cited frames, then open the JPEG with your image tool.
sp_team_frame_dir="$(mktemp -d)"
screenpipe team frame --device-id DEVICE --frame-id FRAME_ID --output "$sp_team_frame_dir/frame.jpg"
Only describe pixels after the frame command succeeds and your image tool opens the JPEG. An unavailable frame is not evidence about what was on screen.
Keep context small: check wc -c /tmp/sp-team.jsonl; if it exceeds 5 KB,
filter with jq or narrow the query/window instead of printing the whole file.
Reference results by timestamp and device, quote only short snippets, respect
anonymous user_* labels, and do not volunteer unrelated employee data.
For the user's own machine, use screenpipe-api, not this skill.
screenpipe team pipes list
screenpipe team pipes preview ./my-pipe/pipe.md
screenpipe team pipes deploy ./my-pipe/pipe.md
screenpipe team pipes schedule my-pipe "every day at 9am"
Before any mutation, show the exact preview and target. New deployments default
to Cloud Runner; use --device, --member, or --all-runtimes only when the
user explicitly chooses that scope. Use --yes for automation only after the
same preview is accepted. Version conflicts fail closed; re-list and re-preview
rather than overwriting a teammate's change. Use --json for structured
receipts.
The CLI explains missing-token and scope errors. Team reads require the relevant
read:devices, read:search, or read:records scope; Pipe management requires
write:pipes. Direct the user to https://screenpi.pe/enterprise?tab=tokens to
mint or rotate a token, then Settings → Privacy → Admin Team API Token.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Develop and test Windows-specific Screenpipe changes on a disposable Azure virtual machine. The workflow verifies native behavior, preserves logs and desktop video, and handles branch and pull request delivery when authorized.
Prepare screenpipe component releases by updating versions and dependency lock files, running required build checks, and triggering GitHub Actions. Verify build results and release artifacts, then hand public app publication over to a person.
Create charts, dashboards, scorecards, and styled summaries as standalone HTML reports for the screenpipe viewer. Keep styles, scripts, and images inside the file so the report renders in a sandbox with no network access.
Use Screenpipe’s local REST API, an interface for programmatic requests, to search screen and meeting history, review app activity and active time, retrieve synced-device records, export recordings, and rerun audio transcription.
Search Screenpipe recordings, screen text, audio transcripts, and synced-device history through its local API. Use the evidence to review activity, find meeting details, and inspect saved workflows, including recorded steps that can inform automation.
Turn a recorded software failure into a draft bug report with timestamps, reproduction steps, expected and actual behavior, and relevant evidence. Separate visible symptoms from possible causes and remove sensitive details from shareable evidence.