Share your localhost,
get real comments

No more screenshots, Slack threads, or "which button?" confusion. Create a shareable link to your localhost, get contextual feedback, and fix issues right in your IDE.

Terminal
$npm install checkpoint@latest
$checkpoint start -p 3000 -n "My Feature"
✓ Tunnel created
▶ https://app.checkpoint.build/share/es2v
Share this link to collect feedback.
Watching localhost:3000...

Let stakeholders comment directly on localhost

One command creates a secure tunnel to your local development. Stakeholders comment right on your live localhost, and their feedback appears back in your IDE where you can fix it.

https://app.checkpoint.build/share/es2vcsqr
1
JakeJake
@Sarah The spacing between these cards feels tight on mobile, can we stack them vertically below 768px?
2
JakeJake
@Sarah The spacing between these cards feels tight on mobile, can we stack them vertically below 768px?
SarahSarah
@Jake Good call, will update!
3
MMia
This section feels empty, maybe add a subtle illustration or an empty-state message so it doesn't look broken.
JakeJake
@Mia Agreed, I'll add an empty-state component here.
SarahSarah
+Add Comment
Comments3

Comments appear right where you work

Stakeholder comments show up in your IDE, pinned to the exact code they're talking about. No more switching between browser and editor - feedback finds you at your workstation.

Tunnels
New Login Page Design (Active)
Dashboard Navigation Redesign (Closed)
Admin Panel Permissions (Stale)
Mobile Checkout Flow (Stale)
Comments
/dashboard
Stack cards vertically below 768px
src/pages/Dashboard.tsx
1import React from 'react';
2import {StatsCard} from './components/StatsCard';
3
4export default function Dashboard() {
5return (
6<div className="dashboard">
7<h1>Dashboard</h1>
8<section className="cards">
9<Card title="Active users"></Card>
10<Card title="Conversion"></Card>
11</section>
12</div>
13);
14}
Comment Thread
Cards layout
Jake1d ago
@Sarah The spacing between these cards feels tight on mobile, can we stack them vertically below 768px?
Sarah1d ago
@Jake Good call, will update!
Mike12h ago
Also can we increase the touch target size on mobile? The buttons are hard to tap.
Emma8h ago
@Mike Good point about touch targets. 48px minimum would be better for accessibility.

From comment to code, automatically

The AI reads each comment, finds the exact code to change, and proposes fixes. Accept the diff or tweak manually - either way, you're shipping changes faster than ever.

CardsRow.module.css
1.cards {
2display: flex;
3flex-direction: row;
4gap: 16px;
5}
6
7.card {
8flex: 1;
9min-width: 0;
10}
11
12@media (max-width: 768px) {
13.cards {
14flex-direction: row;column;
15gap: 12px;
16}
17}
AI Agent
Fix comment from @Sarah "Stack the cards vertically below 768px (mobile spacing)"
Finding layout styles… located `.cards` in `CardsRow.module.css`
Done: cards stack vertically below 768px and spacing is adjusted for better readability.

Plugs into your workflow

Connect Checkpoint to the tools you already use. Turn feedback into issues, messages, and tasks, automatically.

Comments in. Change list out.

Checkpoint's AI reads every comment across every session, groups them by theme, and generates a prioritized list of what to change, so you stop re-reading threads and start shipping.

SarahSarah
The hero headline is way too small on desktop, it doesn't feel like a primary heading. Can we bump it to at least 48px and test a bolder weight?
JakeJake
These feature cards feel cramped, the text is right up against the edges. More inner padding and maybe 24px gap between cards.
MMia
The "Get Started" button blends into the background, it should be our orange brand color so it actually stands out as the primary action.
Suggested changes
Bump hero h1 to 48px / semibold#typography
Increase card padding to 24px, gap to 24px#spacing
Swap CTA background to --orange-500#design
Raise subtitle to #a1a1a1 for WCAG AA#accessibility
Add bold font-weight to hero heading#typography

Your code never leaves your machine

Checkpoint doesn't proxy, store, or touch your source code. We rely on trusted tunneling providers you already know.

Tunneled by ngrok & Cloudflare

No custom tunnel servers. Your traffic flows through ngrok or Cloudflare Tunnel, encrypted and audited.

Nothing stored

We never save your HTML, assets, or source code. The tunnel is live passthrough, stop it and the link dies.

You control access

Tunnels are private by default. You control who can view and revoke access anytime. No public URLs by default.

Ready to skip the PR queue?

No credit card required • Free while in beta