Macroscope’s agent researches your codebase, git history, and connected tools to answer questions and take action.
To use Macroscope’s Agent, you must configure Status. To configure Status, click on Status in the left sidebar, then complete the Product Overview and Sprint Cadence. Once your backfill has finished, you’ll be able to use the Agent.
Built-in
These tools work out of the box once your repositories are connected.
| 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 (beta) | 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
These tools become available when you connect the corresponding service. See Integrations for setup instructions.
| Tool | What it can do |
|---|
| Jira | Looks up issues, tracks project progress, creates new issues across projects. |
| Linear | Looks up issues, tracks project progress, creates new issues across teams. |
| BigQuery | Browses datasets, inspects schemas, runs read-only SQL. Includes a methodology summary with each answer so you can verify the analysis. |
| PostHog | Queries product analytics events, analyzes trends, searches session recordings, inspects feature flags, and runs HogQL queries. |
| Amplitude (beta) | Runs event segmentation queries, analyzes conversion funnels and retention, searches for users, and inspects individual user event streams. |
| LaunchDarkly | Lists projects, environments, and feature flags. Checks flag status, targeting rules, and variations across environments. |
| Sentry (beta) | Searches error issues across projects, views issue details and event history, and investigates crashes and exceptions. |
| GCP Cloud Logging | Discovers available log sources and queries log entries with filters on severity, resource type, timestamps, and payload content. |
| MCP Connectors (beta) | Connect any MCP-compatible server to extend the agent with custom tools (e.g. Datadog, PagerDuty, internal APIs). Configure in Settings → Connections (admin only). |
Where to Interact with Macroscope’s Agent
- Slack: DM Macroscope (under Apps), tag
@Macroscope in a channel, or add it to a group DM.
- GitHub: Mention @macroscope-app in any PR discussion thread, or reply to any of Macroscope’s inline code review comments.
- API: Trigger the agent programmatically via webhooks.
In Slack and GitHub, the agent reacts with 👀 to acknowledge a query and replies in-thread. You can attach images, screenshots, PDFs, and code snippets anywhere in a thread and the agent will use them as context.
Custom Instructions
Set preferred tone, domain context, output format, or person-specific rules in Settings → Workspace → Custom AMA (Ask Macroscope Anything) Instructions (e.g. “customer success teammates should get less technical responses”).
Examples
- “What did the team ship yesterday?”
- “Draft release notes for everything shipped in the past 2 weeks.”
- “How does the authentication flow work?”
- “Here’s a screenshot of a bug. What’s causing it? Open a PR to fix it and assign Eliza as a reviewer.”
- “How many signups did we get last week?” (uses BigQuery or PostHog)
- “What feature flags are enabled in production right now?” (requires LaunchDarkly)
- “Make a Jira ticket to track this bug. Assign it to Ikshita.” (requires Jira)
- “What’s the status of Linear ticket ENG-431?” (requires Linear)
