feedback → github issues

From the live site to a shipped PR

Editors file content and design change requests right from your site. looft turns each one into a GitHub issue, auto-assigned to Copilot — inside your existing review and PR flow.

Get started See pricing
www.acme.com/pricing
Billing, handled

Invoicing that runs itself

Automated billing, dunning, and revenue reports your finance team will trust.

Start free
looft
Created issue from this request and assigned Copilot.
acme/site · issue #142
make the hero headline larger
— main > section.hero > h1
copilot assigned · drafting PR

From request to PR, without leaving GitHub

No new dashboard for your team to learn. The work lands where you already review it.

1

Select

An editor clicks any element on your live site and describes the change in plain language.

2

File

looft captures the page, the exact element, a screenshot, and any attachments, then opens a GitHub issue in the editor's name.

3

Ship

Copilot is auto-assigned and opens a draft PR. You review and merge as usual.

Built for real engineering

Agentic where it helps, precise where it counts.

Point at the real thing

Editors click any element on your live site; looft records the exact selector, text, and position — no more “the button near the top”.

Screenshots & attachments

Every request carries an auto-captured screenshot plus any files editors drag in, paste, or upload — embedded right in the issue.

Real GitHub issues

Every request is a proper issue in your repo, opened in the editor's name — never a black box, never a separate tracker.

Copilot, auto-assigned

The coding agent picks up each issue and drafts a PR against your base branch — and you can re-assign it from the dashboard anytime.

The full round-trip

Watch every request move from issue → PR → review → merged on one dashboard, synced live from GitHub via webhooks.

Team, roles & origins

Invite owners and editors, grant access straight from your GitHub org, and lock each portal to an allow-list of origins.

Secure by construction

The widget runs on your visitors' browsers, so it holds no secrets you'd mind leaking.

No tokens in the browser

A GitHub App and a single consent. Every GitHub call is server-side; the page only ever holds a public portal key.

Origin-bound & allow-listed

Widget access is a 15-minute token pinned to the requesting origin and checked against each portal's origin allow-list.

Encrypted at rest

GitHub tokens and portal secrets are sealed with libsodium and never leave the server in the clear.

Ship your editors' next request from GitHub

Connect a repo, drop the snippet on your site, and looft files the first issue in minutes. Free while you explore.

Get started Sign in