Skip to main content
Macroscope can stream real-time code activity summaries into Slack channels via /macroscope commands. Subscribe channels to specific repositories or activity types so each team sees only what’s relevant.
To add Macroscope to a channel, type @Macroscope and click Add Them. Use /macroscope help for the full command list, or /macroscope subscriptions to see a channel’s current subscriptions.

​
Commands

  • /macroscope subscribe <repo>: all activity from a repo
  • /macroscope subscribe-commits <repo>: commit summaries only
  • /macroscope subscribe-prs <repo>: PR activity only
  • /macroscope subscribe-build-failures <repo>: build failures only
PR notifications include status emojis: ✅ approved, 💬 commented, 🚀 merged.

​
Path-Based Filters

Add --paths= to any subscribe command to filter to specific parts of a repo. Useful for monorepos.
  • /macroscope subscribe-commits your-repo --paths=/api
  • /macroscope subscribe-prs your-repo --paths=/frontend
  • /macroscope subscribe-prs your-repo --paths=/api,/services (multiple paths)
If a file path has spaces or commas, wrap it in quotes: --paths="/my folder/api" Without --paths=, all activity from the repo is streamed.

​
Screenshots and Recordings

When a commit’s pull request has screenshots or screen recordings attached, Macroscope uploads them into that commit’s summary thread, so reviewers can see the change without leaving Slack. Recordings play inline in Slack.
  • Screenshots come from the pull request description.
  • Recordings come from the pull request description and its comments, in .webm, .mp4, or .mov format. Up to five recordings are attached per commit.
Attach files to the pull request through GitHub — drag them into the description or a comment — so they’re hosted on GitHub. Links pointing to other hosts aren’t attached.
Files larger than about 50 MB are skipped. Macroscope also needs permission to upload files to a channel; channels where it doesn’t have that permission still get the summary, just without the attachments.
Recordings are attached in Slack only — the Commits feed in the web app shows screenshots.

​
Linked Issues

Commit summaries display linked Jira and Linear tickets with direct URLs, so you can trace commits back to the work they address.