GitHub Radar

Reads what you shipped.Writes the briefs.

GitHub only, read only. Radar reads the pull requests you merged, drops the bug fixes, and comes back with the stories worth a demo, each as a brief under 90 seconds.

Start free

fieldstone/app · last 7 days5 changes · 2 briefs

Team invitations #974

Role selection #978

Report filters #981

Upgrade test runner #976

Refactor billing service #979

Invite teammates with the right access

0:45

For Workspace admins

1Open team settings
2Invite a teammate, pick Editor
3Send, see the pending invite

based on #974 · #978

Find the report you need

0:38

For Analysts

1Open Reports
2Filter by channel and date

based on #981

The test runner and the billing refactor stay out. Customers would not see them.

Illustrative repository · five merges in, two briefs out

GitHub · Read only

It starts where the work ends: the merge.

Team invitations and roles #974

Mergeddana merged 3 commits into main

Add invite dialog with role picker

Send invitation email

Members list shows pending invites

DemoBites bot · just now

This change shipped something customers will see. Radar can write the briefs.

Analyze PR

Settings › Integrations

GitHub

fieldstone/app

CONNECTED

Source: GitHub
Base branch: main
Access: Read only

Radar reads merges into the branch you chose. It writes nothing to your repository.

Connect once in Settings › Integrations

Or point your agent at a pull request

Each brief is a shot list, under 90 seconds.

Invite teammates with the right access5 beats · 0:44

1
Team settings, the members list
“Here is everyone in the workspace.”
2
Invite a teammate
“Invite a colleague by email.”
3
Pick a role: Editor
“Choose what they can do before they join.”
4
Send invitePointed at, not pressed
“One click sends it.”
5
Pending invite in the list
“They show up as pending until they accept.”

Before the camera

Create a test member so the list is not empty.

After the cut

Remove the test member and the pending invite.

Brief 1 of 3 · key radar-7kq2Approve

What Radar reads

The pull requestChanged filesCommit messagesReview comments

Intent, not code. No diff reaches a brief.

What it drops

Upgrade test runner #976No demo

Refactor billing service #979No demo

Bug fixes and refactors stay out. Customers would not see them.

Edit, combine or split a brief · approve the batch once

Zero briefs is a valid answer

Two ways out.

Invite teammates with the right access0:45

1Open team settings
2Invite a teammate, pick Editor
3Send, see the pending invite

Rec

Record them yourself

The brief is your shot list. Capture it with the Chrome extension or the macOS app, and the Demo agent does the rest.

The ways a take arrives

$ npx demobite record radar-7kq2

›3 briefs · filming 2 at a time, behind the scenes

Invite teammates0:44
Find the report you need0:37
Schedule a weekly digest0:50

Minutes later, in your demo grid

Hand them to the Agentic Recorder

One line with the brief key. It films every brief behind the scenes, on your machine, and the demos land in your grid.

The Agentic Recorder

Radar writes the briefs. It never films.

Claude Code · Codex · Cursor

What comes next.

Agentic Recorder films the demo from one sentence

Record a demo of Funnels

Filming acme.app/funnels · 0:31

✓ Take done · 1:12

Raw take · 1:12

Demo agent turns one take into a finished feature demo

Recording stopped · 1:12

Script written. Narrated. Zoomed on the invite button.

✓ Done before you open it · 0:48

app.demobites.com/editor/funnels

Product Hub puts every release on a page people and AI can find

1,180 views · this release

updates.northstar.example/en/

Make your next merge worth watching.

GitHub · Read only · Briefs under 90 seconds

Start free