Ask Macroscope - Macroscope

Macroscope’s agent can search connected repositories and git history, query integrated tools, and make changes. It works as soon as Slack is connected. Questions about commit history and productivity need the initial Status backfill to finish. Usage is billed in Agent credits.

Where to use it

Surface	Invocation
Slack	DM Macroscope, add it to a group DM, or mention `@Macroscope` in a channel.
GitHub	Mention `@macroscope-app` in a PR discussion or reply to its review comment.
Webhooks	POST a query and poll or specify a delivery destination.
Macros	Run instructions on a schedule or repository event.

The agent acknowledges Slack and GitHub queries with 👀 and replies in-thread. Images, PDFs, screenshots, and code snippets in the thread can supply context.

Built-in tools

Tool	What it can do
Code search	Finds relevant code, patterns, and implementations across all connected repos.
Git history	Traces what changed, when, and why across commits, branches, and contributors.
Pull requests	Searches PRs by status, date range, reviewer, or label. Views PR metadata, summaries, and review activity.
GitHub API	Makes read-only queries for issues, check runs, deployments, commit statuses, and releases.
Code changes	Creates branches, writes code, opens pull requests, updates existing branches, and adds reviewers.
Contributor metrics	Queries engineering output and productivity metrics for individuals or teams over time.
Sprint reports	Retrieves precomputed sprint summaries covering what the team shipped, organized by project and area.
Image generation	Generates AI images from text descriptions, including diagrams, flowcharts, and illustrations.
Web search	Searches the web for context beyond your codebase.
Docs search	Searches Macroscope’s own docs.

Connected services add issue tracking, analytics, feature flags, logs, and any MCP tools you want to connect.

Custom instructions

Set workspace context and response conventions under Settings → Workspace → Custom AMA Instructions. For instructions used by correctness review, use repository instruction files instead.

Example requests

“Trace the authentication flow for API requests and link the relevant handlers.”
“Summarize the changes shipped to payments since the last release tag.”
“Investigate this Sentry error and open a PR with a fix.”
“Break ENG-431 into sub-issues, one per migration step.” (requires Linear)