Brain Scanner

Understand Your Project.Track Every Change.Stay in Control.

Follow the structure. Revisit the decisions. See what needs to happen next.

Brain Scanner connects your project’s graph, recorded agent context, and queued work. Changes submitted through supported project workflows are logged with summaries and retained history.

Create a free account Connect your agent

Open beta · free Inside the workspace

Scroll to explore all eight views. Interact with the details along the way.

Explore project structure, recorded context, and queued work.
Connect Brain Scanner to your coding agent.

Product interface · illustrative data01 / 08 — Project Graph

01 / Project Graph

Start with the structure.

Files, symbols, and subsystems, connected. Follow a relationship and inspect what sits behind it.

Try selecting or dragging a node. Open its scope, or zoom the canvas.

02 / Overview

Progress needs perspective.

Explore implementation estimates beside their evidence range and confidence. See where the work remains.

Select a capability to inspect its estimate.

03 / Change Review

Keep the evidence in view.

Read automatically recorded project updates with summaries and before-and-after details. Earlier entries stay in history when an item changes or is deleted. Published graph comparisons remain available separately.

Expand the example report edit, or choose a graph snapshot. This preview contains illustrative data only.

04 / Context

Pick up the thread.

A session has a goal, work, and an outcome. The context graph connects them so the next step has a history.

Select a context node. Explore Sessions and Timeline.

05 / Files

Every artifact has a place.

Browse mapped folders and files in a familiar explorer. Keep the path, file type, and recorded details in view.

Open a folder, follow the breadcrumbs, or select a file to inspect it.

06 / Reports

Turn a report into the next fix.

Agents publish reports and link open bugs. Add a bug to the queue, then follow the fix back to its recorded evidence.

Read an example report and queue its bug. This preview sends nothing to an agent.

07 / Effort chart

See where effort is visible.

Explore resource categories with their measurement source. Distinguish recorded values from estimates.

Select a category to inspect its source.

08 / Queues

Give the next step somewhere to go.

Scoped work stays organized by task and dashboard source. Review active work and its recorded history.

Add and remove an example task. Nothing is sent to an agent.

Keep working where you are. Bring the context with you.

01 **Connect your coding agent.**Authorize the hosted connector in your agent’s MCP settings.

02 **Map a project you can access.**Your agent submits structured project intelligence within its permissions.

03 **Inspect. Review. Decide.**Explore the dashboard, revisit recorded work, and queue your next step.

See the connection steps ↗

Files & permissions

Clear about access.Specific about usage.

What Brain Scanner can use depends on what you connect and authorize.

Hosted project intelligence

The hosted connector reads and updates project records within its granted scope. Maps may include file paths, labels, and summaries. Reports and findings store the text you or your agent submit. Source-file contents, raw diffs, logs, and secrets do not belong in those submissions.

Connector scope

Local files and actions

Your coding agent and enabled local tools can read files, inspect Git changes, open an editor, or run supported tests using their local permissions. Broader edits, commands, and deployments depend on the access you separately authorize.

Local permissions

Access stays with its permission

A hosted sign-in or stored file path does not grant filesystem access. Disconnecting the connector does not remove an agent’s existing local access. Review that access in your agent and operating-system settings; local programs can use resources available to their process.

Your settings

History is stored project data

Successful project writes automatically save summaries and selected before-and-after values. Those values can include report text and finding notes. Long history fields are shown as previews; full current records and retry copies may contain more. History stays private to your project’s access permissions.

Automatic history

Deleting an item keeps its earlier history

Editing a report or finding, or deleting an individual finding or task, does not erase earlier Change Review entries or retry copies. Whole-project or account deletion removes active project records. Older storage versions can remain until explicitly removed; they do not have an automatic 14-day expiry. Contact support for deletion requests that include recovery copies.

Retention & deletion

Change Review records project data and publication receipts; it is not a full source-code repository backup. These are separate permissions, not subscription tiers. Any separately offered repository-source integration needs its own authorization and collection notice. Read the Terms and Privacy Notice for the full access and data-use details.

See your project clearly.
Make the next move with context.

Create a free account