The pull request inbox that remembers

Review the code.
Skip the ceremony.

PRamatic finds the pull requests that need you, runs a read-only AI review, and keeps every comment a draft until you decide.

Get the macOS preview ↗ See the workflow

Read-only GitHub Local reports Copy-only drafts

Inbox

OPEN3

craft/monorepo

Make retries boring again

#428 · Review requested

2 findings

craft/monorepo

Move billing jobs to the queue

#421 · Authored by you

Clean

studio/web

Tighten session boundaries

#98 · Previously involved

Head moved

craft/monorepo#428

Make retries boring again

PRamatic summary

Found 2 actionable issues across 14 changed files.

100%

Findings 2ConversationDiffChat

Stop retrying after the terminal attempt

jobs/retryPayment.ts:42–48

The 429 branch re-enqueues forever. A provider incident can quietly turn into an immortal queue.

Local draft commentCan we apply the configured attempt cap here?

P1 actionable

head verified

Scroll to inspect

01 / 05

Your queue,
already triaged.

Review requests, your own PRs, stale reports, and conversations that need attention land in one calm queue. A refresh archives what is merged or already approved.

Suggested review list with search and filters
Head-change detection and force re-review
Automatic merge and approval archiving

Open 5Needs attention 2My PRsArchived

craft/monorepo · #428Make retries boring again

Your review requested · head moved 4m ago

Re-review

studio/web · #98Tighten session boundaries

Approved by you · auto-archiving

Approved

mobile/ios · #71Unify push-notification receipts

Merged · moving out of your way

Archived

One refresh, less archaeology.Merged and approved PRs leave the open queue automatically.

jobs/retryPayment.ts

+3-1

@@ -39,4 +39,7 @@ async function retryPayment

3939 const delay = retryAfter(response)

40+const terminal = attempt >= maxAttempts

4041 if (response.status === 429) {

42+ if (terminal) return markFailed(job)

4143- return enqueue(job, delay)

44+ return enqueue(job, withJitter(delay))

4245 }

P1Terminal attempts still re-enqueue

This path needs the configured attempt cap before it schedules more work.

02 / 05

The finding lives
where the code does.

Read a GitHub-style diff, jump from a finding to the exact line, and open that location on GitHub when you are ready to comment yourself.

Rendered file-by-file diff
Finding-to-line navigation
One-click handoff to GitHub

03 / 05

Every thread you’re in.
None you’ve escaped.

A holistic conversation view follows your mentions, replies, change requests, and review threads across repositories—without revisiting every PR by hand.

Open and resolved review threads
Mentions and conversations involving you
Hide, collapse, or archive the quiet ones

craft/monorepo #428 · line 42“Should this use the existing backoff helper?”

@you were mentioned · 2 new replies

studio/api #216 · generalChanges requested on your PR

Unresolved · updated 18m ago

Needs you

mobile/ios #71 · line 88Receipt format is settled

Resolved · collapses quietly

Resolved

3 conversations need you

Retry behaviorcraft/monorepo #428 · finding context

SHA 8d31c5a

You

Is this still a bug if the queue lease expires first?

PRamatic

Yes. The lease controls who owns the current attempt; it does not cap future attempts. The 429 branch schedules a new job before the lease matters.

retryPayment.ts:42

Ask about this PR or finding…

04 / 05

Ask the PR.
Keep the context.

Open multiple chats for a pull request or a specific finding. Each answer is grounded in the exact reviewed head, with a direct route back to the diff.

PR- and finding-scoped chats
Multiple named conversations per PR
SHA-bound context that rejects stale heads

05 / 05

Local-first.
Not local-fiction.

Reports and drafts stay on your Mac. Review context is sent to the AI provider you explicitly choose. The distinction is visible before the first review.

GitHub is read-only

No posting, approval, merge, push, or repository mutation action exists in the app.

Fixed read operations

Reports stay local

Findings, drafts, receipts, preferences, and caches live on your Mac and can be exported or deleted.

Telemetry off

AI flow is explicit

Selected metadata, diffs, source excerpts, policies, and chat context go only to the provider you select.

Consent required

Secrets stay native

Provider keys and GitHub App credentials use macOS Keychain and never enter report requests or diagnostics.

Keychain protected

GitHub readSanitized workspaceChosen AI providerLocal report

Signed macOS preview

A second reviewer.
Zero posting privileges.

The universal macOS preview is Developer ID signed, accepted by Apple’s notarization service, and ready to install.

Read the release disclosures

PRamatic for macOSVersion 0.1.0 · Apple silicon + Intel

Read-only review inbox
Codex or Claude Agent
Local reports and drafts

Download for macOSUniversal installer · macOS 13+ · signed, notarized, and stapled.

The un-dramatic
fine print.

Plain-language disclosures, available before download and inside the desktop app.

Privacy policyWhat stays local and what reaches your AI provider Terms of usePreview software, responsibilities, and AI limits Third-party noticesOpen-source licenses and provider marks

PRamatic legal

Privacy policy

Effective August 26, 2026. PRamatic reads GitHub account identity, repositories, pull-request metadata, diffs, selected source content, comments, reviews, and threads only after the user connects GitHub and places repositories in scope.

AI processing

When a user starts a review or chat, selected PR metadata, diffs, source excerpts, review policy, relevant conversation or chat context, and user guidance are sent to the selected provider—OpenAI for Codex or Anthropic for Claude Agent—under the user’s provider account and provider terms. Explicit consent is required before the first review.

Local storage

Reports, drafts, receipts, preferences, caches, mirrors, and sanitized workspaces are stored on the Mac. Provider keys and GitHub App credentials use macOS Keychain. Product analytics and advertising telemetry are off.

Retention and control

Users can select archived-report retention, export local app data, and permanently delete local reports, caches, mirrors, preferences, and application credentials. Local deletion does not delete data held by GitHub or the selected AI provider.

Remote actions and security

PRamatic provides no posting, approval, merge, push, or repository mutation action. The renderer has no generic shell, filesystem, database, or Keychain access. Diagnostic exports exclude source, report content, and credentials.

Production contact

The public release must identify the legal operator, address, and monitored privacy contact before distribution. This preview policy is not the final operator-specific notice.

PRamatic legal

Terms of use

Effective August 26, 2026. PRamatic is preview software provided without warranties that it will be uninterrupted, error-free, secure, or fit for a particular purpose, to the extent permitted by law.

Your responsibilities

Users must have permission to access and send selected repository content to GitHub and the chosen AI provider. Users are responsible for provider charges, account terms, company policy, export controls, and every copied or posted comment.

Automated output

AI findings may be incomplete or incorrect. They are not security certification, legal advice, or a substitute for human review, tests, and repository controls.

Third-party services

GitHub, OpenAI, and Anthropic are independent services with their own terms and privacy practices. PRamatic is not affiliated with, endorsed by, or sponsored by them.

Release status

Operator identity, jurisdiction, mandatory consumer rights, liability terms, and dispute provisions require counsel review before public distribution.

PRamatic legal

Third-party notices

PRamatic uses open-source software under its respective licenses, including React, Vite, Tauri, Rust crates, Lucide, the MIT-licensed dotLottie React player, React Markdown, Zod, SQLite, the OpenAI Codex SDK, and the Anthropic Claude Agent SDK. The small motion illustrations on this page are original PRamatic assets.

Provider marks

GitHub, OpenAI, Codex, Anthropic, and Claude are trademarks of their respective owners. Names identify compatible services only. Neutral interface symbols are used instead of provider logos; no endorsement is implied.

Release inventory

Every signed release must include a lockfile-specific, transitive dependency inventory and every notice or license text required by those dependencies. The repository contains the regeneration commands.

Review the code.Skip the ceremony.

Make retries boring again

Move billing jobs to the queue

Tighten session boundaries

Make retries boring again

Stop retrying after the terminal attempt

Your queue,already triaged.

The finding liveswhere the code does.

Every thread you’re in.None you’ve escaped.

Ask the PR.Keep the context.

Local-first.Not local-fiction.

A second reviewer.Zero posting privileges.

The un-dramaticfine print.

AI processing

Local storage

Retention and control

Remote actions and security

Production contact

Your responsibilities

Automated output

Third-party services

Release status

Provider marks

Release inventory

Review the code.
Skip the ceremony.

Your queue,
already triaged.

The finding lives
where the code does.

Every thread you’re in.
None you’ve escaped.

Ask the PR.
Keep the context.

Local-first.
Not local-fiction.

A second reviewer.
Zero posting privileges.

The un-dramatic
fine print.