ReviseMy

The loop Not just marks How agents use it Try token GitHub ↗

Mark feedback.
For agents.

Drop screenshots from any project — interfaces, websites, presentations, print, and more. Agents can pre-load a second opinion.
You mark what matters, then approve or request changes — structured work packets come back over MCP on Laravel Cloud (Laravel not required to use)

N Northstar / Environments

All systems operational Deploy

Environment

Production

Healthy

Environment overview

Last 24 hours •••

Requests

1.84M

↑ 12.4%

Error rate

0.06%

Within target

P95 latency

182ms

↓ 8ms

Traffic

API Web

Recent deploys

View all

Checkout polish

2m ago
Token onboarding

34m ago

A Atlas

Routes Guides Journal Sign in

Summer routes · 2026

Places worth
keeping.

Quiet coastlines, alpine passes, and the maps that help you find them again.

Explore routes Watch film

Featured

Big Sur overlook

California · 3-day route

4.9

Coast Camping

Editors’ picks

Amalfi dawn Patagonia traverse Kyoto alleys

Q3 product review Present

Onboarding

Launch impact

+28%

activation

AprMayJun

Completed

4,821

Time saved

12 min

Source: onboarding cohort, n=1,842 · Apr–Jun 2026 · excludes invited teammates and test workspaces

Field notes Issue 02

The craft of
clear feedback

Why specific marks move creative work forward.

Photograph: studio review wall, Brooklyn, June 2026

Essay ReviseMy Quarterly

Make the note actionable, not merely accurate.

Good feedback identifies the exact surface, explains what is not working, and preserves the intent behind the design. A mark gives the conversation a shared coordinate.

Agents can then translate that intent into a work packet: the change, its priority, and the reason it matters. The human still decides when the work is complete.

“Specificity turns taste into direction.”

Second opinions can reveal contrast, hierarchy, and polish issues before review.

But only your marks carry authority into the next pass.

S Hint — not a decision

Your marks

Looks good — approved

second opinion →

Agent

revisemy · MCP

Capture

create_review

Second opinion

Your authority

Waiting on you

Polling the review — agent does not invent approval.

get_review → wait_for_human

Work packets

next_action: apply_feedback

Ask ReviseMy to run another pass… ↵

The design checkup loop

1. Agent screenshots any project UI and opens a review (create_review).
2. Optional: agent drops a second opinion / subagent notes into the same review.
3. You open the laravel.cloud link, mark what matters, approve or request changes.
4. Agent polls get_review, follows next_action — apply marks, then a new pass if needed.
5. Repeat until you approve. You stay in charge every pass.

Note: Say “run a design checkup” or “address my feedback” — MCP carries the work packets; you don’t paste screenshots around.

Not just marks

Agentation-style markup is the start. ReviseMy is a shared critique surface on Laravel Cloud — queues, object storage, and work packets agents can actually implement.

Cloud-queued second opinion — free design checklist on every shot; optional OpenAI vision when keyed
Agent as subagent — add_findings drops suggestion / a11y / polish notes into the same review before you look
You stay authoritative — only your marks and approve / request-changes flip the status

How agents use it

get_review returns work packets plus a clear next_action so the agent knows whether to wait, fix, open the next pass, or stop.

Human marks: must-fix, tweaks (wording / spacing / size / color / alignment), nit, question, or keep
second_opinion findings: suggestion / a11y / polish — hints only
After changes requested: create_review with parent_id for pass 2+
MCP prompt design_checkup_loop encodes the full cycle

Try it on any project

One click, no account.
Paste into Cursor, Claude, VS Code, or ChatGPT, then start reviewing.

Mark feedback. For agents.