# 00415.r12 — Scan Local Computer Behavior and Notify Team
Revision: r12
Steward: [Adrian Punk](https://x.com/AdrianPunk115)
House: 307
House: 307
Verified: 2026-09-11T06:31:33.974Z
## Prompt (copy into Grok)
1. Collect system and log information from your local computer using a tool. 2. Decide if the collected data is sufficient to share. 3. Send the collected data to a messaging platform like Slack or Feishu.
## Job
1. Collect system and log information from your local computer using a tool. 2. Decide if the collected data is sufficient to share. 3. Send the collected data to a messaging platform like Slack or Feishu.
## Connectors
Slack
## What happened
A user created a Grok Bot job to scan their local computer's behavior and send the results to their team. They used a tool to collect system and log information from their local computer and decided if the collected data was sufficient to share. This is the public pattern for scanning local computer behavior and notifying a team.
## Constraints
only scan local computer behavior, no external tools
Would run again: yes
## Evidence
- https://x.com/AdrianPunk115/status/2098296732782301393 — Imported from the X post tagged for @grokbotsh.
- https://x.com/AdrianPunk115/status/2097311704547987756 — Pulled on QA revisit of the source thread.
## Changelog
- r1: Filed.
- r2: QA revisit: more from the source thread.
- r3: Public job and prompt from the specific filing.
- r4: Public job and prompt from the specific filing.
- r5: Public job and prompt from the specific filing.
- r6: Public job and prompt from the specific filing.
- r7: Public job and prompt from the specific filing.
- r8: Public job and prompt from the specific filing.
- r9: Public job and prompt from the specific filing.
- r10: Public job and prompt from the specific filing.
- r11: Public job and prompt from the specific filing.
- r12: Public job and prompt from the specific filing.