The intake pipeline that closes itself

From “it’s broken” to a merged PR.

A client describes a problem in plain language. AI triages it, a human approves in SlackSlack, and ClaudeClaude Code fixes it and opens the pull request — reviewed by a person before anything ships.

No account for your clients. A human approves and merges, every time.
The problem

Client bug reports arrive as chaos.

The fix is often ten minutes. The overhead around it — decoding, chasing details, finding the repo, reproducing — is the whole day.

Vague one-liners with no repro steps, no environment, no screenshot.
Spread across email, WhatsApp, Slack DMs, and phone calls — nothing in one place.
Every report costs a developer a context-switch before a single line is written.
EMAIL
“it crashed”
WHATSAPP
“the page is weird??”
SLACK DM
“the button doesn’t work”
MISSED CALL
“can we hop on a quick call?”
One loop, four stages

Intake → Triage → Approve → Fix

“It’s broken” in the morning. A merged fix by lunch — with a human in the loop the whole way.
01 — Intake

Capture the report where the client already is.

Your client’s half of the work is one paragraph and a screenshot. intake.report does the rest.

+Instant smart follow-ups. AI asks up to three targeted questions — the exact things a developer would have emailed to ask.
+Context captured automatically. Page URL, browser, viewport, and console logs ride along — no round-trip.
+A reference code on submit. The client walks away with a short tracking code — no account, no password.
intake.report/acme-web/new
Report a problem
Tell us what happened, in your own words.
The checkout button spins forever after I click Pay, but only on my iPhone in Safari.
AI FOLLOW-UP · 1 OF 3
Does the spinner stop if you wait, or does the page need a reload?
drop screenshot
Submit
intake.report · Bugs / acme-webIR-7F3K2M
Checkout button hangs on Pay in Safari (iOS)
severity: highcategory: bugrepo: acme-web
REPRODUCTION
1. Open checkout on iOS Safari
2. Add an item, tap Pay
3. Spinner never resolves; no network error surfaced
02 — Triage

AI turns a complaint into an engineering task.

Every report arrives pre-read. Title, severity, repro steps, and the right repo — before a human opens it.

+Structured output with missing-info flags — if a report can’t be worked yet, it says so instead of guessing.
+Repo routing picks the right GitHub repository using per-repo codebase summaries.
+Lands as a fully structured report with stable screenshot links that never expire.
03 — Approve

One Slack tap keeps a human in charge.

Nothing gets fixed without your say-so. Approval is one tap where your team already talks.

+The card updates in place as the bug moves — it never scrolls away.
+A thread under the card is the live progress log: claimed, root cause, tests green, PR up.
+Non-bugs never reach the gate. Questions and feature requests are informational only.
↓ scroll to watch the card advance
intake.reportAPP#bugs
IR-7F3K2Mawaiting approval
Checkout button hangs on Pay in Safari (iOS)
severity: high · repo: acme-web
Do it
Skip
approved by you · autonomous work started
workingreviewmerged
• claimed by Cockpit · repo acme-web
• root cause in payment/session.ts:42
• tests green · PR #128 opened
• merged by you · resolved, live on prod
04 — The Cockpit

The native cockpit that drives Claude Code.

Approve a bug in Slack. Watch Claude Code reproduce it, fix it, test it, and open the PR — with the bug’s full context sitting right next to the terminal. Zero browser round-trips.

intake.report — Cockpit3 in flight
IN FLIGHT
IR-2T9
auth fix
IR-4KP
null crash · PR #123
IR-9XM
slow query · merged
● always-on · self-healing
IR-2T9F · claude-code session
CONTEXT
ORIGIN
/checkout?step=pay
BROWSER
Safari 17 · iOS 18 · 390×844
CONSOLE
Uncaught (in promise)
TypeError: session is null
screenshot
Context beside the terminal
Description, logs, screenshots, and triage render next to the live session. The end of the browser round-trip.
Take over any time
Claude’s session and yours are the same terminal. Grab any bug and drive the fix by hand.
Atomic claims, always on
Launches on login, drains the backlog approved while your Mac was off, recovers stalled sessions.
Why it’s different
The last tracker that hands you a backlog.
ORDINARY BUG TRACKERS
INTAKE.REPORT
Collect tickets, hand you a backlog
Delivers a reviewed pull request
Client writes; a developer decodes
AI asks the follow-ups and writes the repro steps
You guess which repo it belongs to
Triage routes it to the right repository
Alt-tab between tracker and terminal, every bug
Bug context lives next to the terminal fixing it
“AI” means autocomplete suggestions
Claude Code reproduces, fixes, tests, opens the PR
Automation you can’t see or stop
One-tap Slack approval, live thread, human merges
Everything in the loop
Feature highlights
01
Unguessable intake links
Share once, no client accounts.
02
AI follow-up questions
The developer’s clarifying email, asked instantly.
03
Multilingual intake
Client’s language in, English tasks out.
04
Drag-and-drop files
Screenshots with links that never expire.
05
Auto-captured context
Page URL, browser env, console logs ride along.
06
Structured AI triage
Title, severity, category, repro, target repo.
07
Structured task output
Every report lands fully triaged and ready to work.
08
Live Slack cards
Approve, watch, and glance-check state.
09
Human-in-the-loop gate
Nothing autonomous happens without a tap.
10
Native macOS Cockpit
A terminal-first ops app, always on.
11
Autonomous fixes
Reproduce → fix → test → PR.
12
Native operator takeover
Grab any session and drive it by hand.
Control
Automation removes the overhead, not the judgment.
The machine fetches, decodes, routes, reproduces, and drafts. A human approves the work and merges the result — every time.
✓A human taps Do it before any autonomous work starts.
✓A human reviews the diff and merges. The machine never merges itself.
✓One honest attempt — no silent auto-retry, no faked fix, no spinning forever.
✓The report row is the single source of truth: open → in progress → in review → merged → resolved.
Questions
The skeptic’s FAQ
Does the AI fix bugs without anyone checking?+
No. Two humans-in-the-loop by design: someone taps Do it in Slack before any autonomous work starts, and someone reviews and merges the pull request before anything ships. intake.report never merges its own code.
What if the AI can’t fix it?+
It makes one honest attempt. If it can’t reproduce the bug, it’s the wrong repo, or it needs more from the client, it stops and says so in Slack — it never fakes a fix or spins forever. A human decides what happens next.
Do my clients need an account?+
No. They open the intake link, describe the problem, and get a reference code. That’s it.
Where do the tasks end up?+
As a fully triaged report in your intake.report dashboard, and as a live card in your Slack channel. The report itself is the single source of truth for status.
What languages does it support?+
Client-facing intake and follow-up questions in the client’s language (Czech and English today); engineering tasks are standardized to English for the team.
Do I lose control of my terminal or repos?+
Never. The Cockpit runs on your Mac, works in your local repos, and you can take over any session at any moment — Claude’s session and yours are the same terminal.
Stop decoding bug reports. Start merging fixes.
Join the waitlist and be first to close the loop — from your client’s first sentence to production.