Macroscope

Command your own software factory.

[Macroscope @Macroscope]

Today we are introducing Murmur, our cloud agent orchestration system.

Here's an early preview of Murmur:

[Kayvon Beykpour @kayvz]

https://t.co/66Pm2Hgqhy

[Macroscope @Macroscope]

introducing Policy Repo: write your code review config once, and every repo inherits it.

pick a Policy Repo under settings → repos → policy inheritance. macroscope then uses the ".macroscope/" config from that repo's default branch as the shared default for all your repos:

✅ "approvability​.md": your policy for which PRs macroscope can safely approve without a human
👻 "ignore​.md": the files code review should skip, so reviews stay fast and focused
🤖 "check-run-agents/": agentic PR checks you write in plain markdown
🎯 "correctness/": tune how macroscope's correctness check works with your own rules and filters

need something different in one repo? add that file to the repo's own ".macroscope/" folder and it takes priority over the inherited one.

that means no more copy-pasting config into every repo, no drift when one copy gets updated and the rest don't, and one PR to change review policy everywhere.

docs: https://t.co/ijmp2nOPKk

[Kayvon Beykpour @kayvz]

your eng team burns hours reviewing PRs an agent could have approved. macroscope fixes this. "Approvability" is our agent that auto-approves PRs that are safe to merge.

today we're launching a dashboard that shows how Approvability is performing, what it approved and why, so you can confidently make it more permissive over time and understand the impact.

[Macroscope @Macroscope]

docs: https://t.co/4CosV3xCUX

[Macroscope @Macroscope]

introducing the Approvability Dashboard: see what macroscope's approvability agent is approving, what it isn't, and how your policy changes move the numbers.

approvability works out of the box with sensible defaults. want it more permissive or tuned to your team's standards? add your own rules in "approvability​.md", then watch how those changes play out on your real PRs:

✅ approval rate: the share of PRs macroscope approved, plus a ceiling for what it would have approved
🛡️ eligibility: how often the agent judged a change safe to approve without a human
🚦 verdict mix: approved, would approve, needs human approval, skipped
📋 every PR and its verdict, searchable by repo and time range, and exportable to CSV

find it under code review → approvability in the macroscope app.

[Macroscope @Macroscope]

3/ check run agents are agentic PR checks you write in plain markdown.

they now follow the same ignore rules as code review, so they skip test files, .json, or anything else you've told Macroscope to ignore. that means faster checks, simpler configs and much more cost efficiency.

if one of your agents does need to review something you've deliberately ignored, use the "include" param in its config.

[Macroscope @Macroscope]

1/ a few upgrades to approvability and check run agents this week.

approvability is a macroscope agent that decides whether a PR is safe to merge without a human, and approves it if so. it helps make code review less of a bottleneck for your eng team.

as of this week, when you resolve the last blocking comment on a PR, approvability automatically reruns. so a fixed PR gets approved right away, instead of sitting there waiting on a new commit or a manual rerun. this means faster approvals and faster merges.

[Macroscope @Macroscope]

2/ new: onlyApprove. list paths in approvability's front matter, and it will only consider approving PRs whose diff stays inside them. touch anything outside those paths and it won't approve.

so you can turn on auto-approval for the parts of your codebase you trust it with, without handing it the keys to everything.

[Macroscope @Macroscope]

Back for day 2 of ELC! Loved all the conversations yesterday and are excited for more today.

If you’re at the conference, come say hi :)

[Macroscope @Macroscope]

Yesterday's #SFTechWeek Clickety Clack Café, in photos 📷

Thanks for stopping by! And if your PR needs another shot, check out Macroscope: https://t.co/SoxEEACzIl

[Macroscope @Macroscope]

PSA: free coffee and matcha at 500 Folsom St until 4:30pm 🍵

Grab a hot (or cold) fix before your next #SFTechWeek event. We'll be here (caffeinated).

[Macroscope @Macroscope]

Clickety Clack Café is live!☕️

Coffee & code review on Macroscope.

Register for location: https://t.co/qKYbB9LGJU

#SFTechWeek

[Lightfield @lightfld]

@Macroscope runs its go-to-market on a business world model built with Lightfield.

They ingest customer touchpoints across marketing interactions, product use, and sales into a single platform. This gives agents full context on entire customer lifecycle. Agentic workflows that used to take months to build in other systems can be designed in hours using natural language.

Read how Macroscope is building its GTM system.

https://t.co/6NlNnx6Z1I

[Macroscope @Macroscope]

Tomorrow: free coffee for everyone at #SFTechWeek.

Clickety Clack Café, 1:30 to 4:30pm. RSVP for the location.

Coffee & Code review on us.

https://t.co/qKYbB9LGJU

[Macroscope @Macroscope]

@cars24india is one of India's largest auto-tech companies: 300M+ users, $1B+ in revenue, 400 engineers.

with Macroscope, they saw up to 3x more code reaching production in 3 months. 🧵

[Macroscope @Macroscope]

🥉 GPT 6.1 Sol debuts at #3 on our code review leaderboard.

It comes below GPT 6 Sol because recall is lower, but it leaves 30% fewer comments with very high precision.
It also slightly beats workhorse Astra at a seventh of the price!

See full results: https://t.co/czIcV77GGF

[Macroscope @Macroscope]

@cars24india not more tokens, more shipped code.

full case study: https://t.co/X4jgY7OvPg

[Macroscope @Macroscope]

@cars24india is one of India's largest auto-tech companies: 300M+ users, $1B+ in revenue, 400 engineers.

with Macroscope, they saw up to 3x more code reaching production in 3 months. 🧵

[Macroscope @Macroscope]

@cars24india since december 2025, Macroscope has been their source of truth for engineering output: code that actually lands in production.

code review catches bugs before an engineer sees the PR. approvability flags what's safe to merge and what needs human judgment.

[Macroscope @Macroscope]

@cars24india Jayesh Gupta (AI & innovation at cars24) put the problem simply:

"how do you measure productivity when token usage no longer tells you what work is actually getting done?"

[Macroscope @Macroscope]

We're opening a coffee cart for #SFTechWeek ☕
Free coffee and matcha for everyone shipping code

Tue Oct 6, 1:30 to 4:30pm, downtown SF. RSVP for location drop.

https://t.co/qKYbB9LGJU