How to vibe codeScribe
Workflow context for teams & AI agents
scribehow.com ↗Documentation & AI Workflow Capture
The verdict: can you vibe code Scribe?
Build a web-only subset using a Chrome extension and Next.js, but keep paying if you need native desktop recording and enterprise compliance.
Replicating Scribe's web-based guide generation loop is a rewarding side project, but the cross-platform native desktop recorder and enterprise PII auto-redaction are major engineering hurdles. A solo developer can build a robust web extension that records click streams and pushes them to a Next.js web dashboard where an LLM turns raw events into clean SOP steps. However, capturing native desktop apps like Excel or Photoshop requires building and signing separate macOS and Windows binaries with OS-level screen-capture hooks, which takes months of tedious native debugging.
Estimated effort: 3-4 weeks part-time
What you can't replicate
- Native desktop app capture for non-browser software
- Enforced automatic PII/PHI redaction across enterprise workspaces
- Enterprise SAML SSO and strict data governance agreements
Founded
2019
Raised
$130M
Team
~120
Cheapest paid tier
$25/mo
What Scribe does
Automatically capture how work gets done and generate step-by-step Standard Operating Procedures (SOPs), tutorials, and guides.
Core features
- Browser extension event capture (DOM click, input tracking)
- Automatic screenshot capture and bounding box annotation
- AI-driven step title and description generation
- Step editing, cropping, and manual PII redaction
- Export to Markdown, HTML, and PDF
- Workspace and document management dashboard
The business
Pricing
- BasicFree
- Pro Personal$25/mo
- Pro Team$13/seat/mo
- EnterpriseCustom
Funding
$130M from StepStone Group, Amplify Partners, Redpoint Ventures, Tiger Global, Morado Ventures
Pay vs build, cumulative
Break-even at month 1 — after that, every month is money kept.
The hard parts of vibe coding Scribe
- Building a reliable cross-browser extension that intercepts clicks without breaking page behavior
- Client-side screenshot manipulation, bounding-box overlays, and redaction pipelines
- Asynchronous sequencing of raw DOM events into coherent natural language instructions
How to vibecode Scribe
Prerequisites
Node.jsFree
Required runtime for Next.js web application and browser extension build tooling
GitHubFree
Source control and deployment pipeline integration
Google ChromeFree
Required host for developing and testing the Manifest V3 capture extension
AI coding tools
Recommended stack
| Frontend | Next.js |
|---|---|
| Backend | Next.js Server Actions |
| Database | Turso |
| Auth | better-auth |
| Payments | none |
| Other | Vercel AI SDK, Tailwind CSS, Lucide React |
Hosting & infrastructure
| Vercel | Hosting the Next.js dashboard and API routes | $0/mo |
| Cloudflare | Storing guide screenshots in R2 object storage | $0/mo |
Build guide
01Scaffold Next.js Dashboard & Database Schema
Initialize the Next.js project with Tailwind CSS, configure Turso database with Drizzle ORM, and set up user authentication.
Create a new Next.js project using App Router, TypeScript, and Tailwind CSS. Set up Turso for database connectivity via Drizzle ORM. Define tables for users, guides (id, title, description, user_id, created_at), and steps (id, guide_id, step_number, action_text, screenshot_url, selector). Implement better-auth for email/password authentication. Create a clean dashboard UI that lists the user's recorded guides with options to view, edit, or delete them. Ensure all components use Tailwind CSS and Lucide React icons.02Build Chrome Extension Manifest V3 Recorder
Create a browser extension that listens for click and input events on web pages and transmits raw interaction payloads back to the web app.
Build a Chrome extension using Manifest V3 that includes a background service worker, a popup UI with 'Start Recording' and 'Stop Recording' buttons, and a content script. The content script must attach a click listener to the document, capturing the target element's outerHTML, text content, CSS selector, and viewport coordinates. When a click occurs, use chrome.tabs.captureVisibleTab to snap a screenshot of the active tab. Send the event payload (screenshot data URL, element metadata, timestamp) via background script to our Next.js API ingestion endpoint. Handle authentication tokens securely in extension storage.03Implement Ingestion API & Screenshot Storage
Build the backend API endpoint to receive raw extension payloads, upload screenshots to Cloudflare R2, and create guide step records.
Create a Next.js API route at `/api/guides/ingest` that accepts a recorded session payload containing an array of steps (each with a base64 screenshot and DOM metadata). Authenticate the request via session cookie or API token. For each step, upload the base64 image buffer to Cloudflare R2 object storage, returning a public CDN URL. Insert a record into the Turso database linking the guide to the newly stored image URLs and captured action metadata. Return the created guide ID on success.04AI Step Description & Title Generation
Integrate the Vercel AI SDK and Anthropic API to analyze recorded DOM actions and automatically write clear tutorial text for each step.
Install the Vercel AI SDK and Anthropic AI provider package. Create a server action `generateGuideContent(guideId)` that fetches all steps for a given guide from the database. Pass the DOM element tag, inner text, action type (click/input), and step sequence to Claude 3.5 Sonnet. Prompt the model to return a JSON array of polished step descriptions (e.g., 'Click on the "Settings" button') and an overall guide title. Update the database records with the generated titles and descriptions, and return the updated guide object to the frontend.05Build Guide Editor & Screenshot Redaction Canvas
Develop an interactive guide editor view allowing users to reorder steps, edit description text, and apply blur or redaction boxes over screenshots.
Build a guide editor page in Next.js (`/guides/[id]/edit`) displaying a vertical timeline of all steps with editable text inputs for title and instructions. Render each step's screenshot inside an interactive HTML5 canvas element. Implement a drag-to-select redaction tool on the canvas that allows users to draw black blur rectangles over sensitive parts of the screenshot, saving the updated image back to R2 storage upon clicking 'Save Changes'. Add buttons to delete or reorder steps.06Export & Share Functionality
Add public view sharing links and Markdown/HTML export options for generated guides.
Create a public viewer route at `/guides/share/[id]` that renders the guide in a clean, read-only layout optimized for printing or reading. Add an 'Export' dropdown menu with options to download the guide as a formatted Markdown file (`.md`) containing embedded image links and step lists, as well as a standalone HTML export. Ensure public guides respect a `is_public` boolean column on the guides table.
Cost vs paying for Scribe
What will you build it with?
Starting total with Claude Code~$20 one-time
Starting costs (one-time)
- Claude Pro / Cursor Pro subscription$20
Total~$20 one-time
Ongoing costs (monthly)
- Vercel Hobby Hosting$0
- Turso & Cloudflare Free Tiers$0
- Anthropic API usage (personal testing)~$2
Total~$2/mo
Paying for Scribe
$25/mo
Your time to build
25-35 hours
AI tool credits
$20
Break-even
1 month
Vibe code Scribe: FAQ
- Can you vibe code Scribe yourself?
- Solid side project — 68/100 vibecodeable. Build a web-only subset using a Chrome extension and Next.js, but keep paying if you need native desktop recording and enterprise compliance.
- How long does it take to vibe code Scribe?
- 3-4 weeks part-time — roughly 25-35 hours of hands-on time with an AI coding agent.
- How do you build your own Scribe?
- Scoped to personal use: Next.js on the front, Next.js Server Actions behind it, Turso for data. Follow the 6-step build guide on this page — each step has a paste-ready prompt for an AI coding agent.
- How do you code your own Scribe without being an expert?
- Use an AI coding tool (Claude Code or Cursor) and work in small steps: scaffold, data model, core screens, then deploy. Realistic effort: 3-4 weeks part-time. The prompts on this page are written so the AI does the heavy lifting.
- How much does it cost to vibe code Scribe instead of paying?
- About ~$20 one-time to start and ~$2/mo to run, versus $25/mo for Scribe. Break-even: 1 month.
- What stack should you use to vibe code Scribe?
- Next.js; Next.js Server Actions; Turso; plus Vercel AI SDK, Tailwind CSS, Lucide React.