I Vibe Coded for 24 Hours in Claude and Cursor Then Forgot All of It - Forensic Log
I blacked out into code and woke up with a working Chrome extension and new website. I have no memory of. So I asked an AI bird what I'd done. Full transparency.
Full Moon Powered Al Fueled Session
May 1st, 2026. I’d been DJing electronic music and drinking for hours until early Friday morning. Severe ADHD pattern-firing at terminal velocity, idea-receiver brain wide open, nervous system soaked in alcohol and bass frequencies.
By every metric a doctor would have used, I was an unfit operator of heavy machinery.
By every metric a Chromium extension developer would have used, I was about to ship a working product.
The set ended around 1am. I had two options: sleep, or let the residual frequency keep firing.
The frequency won.
I opened Claude Cowork and in no condition to do anything more complex than fall over — vibe-coded a Chrome extension from scratch in a single session.
I try to do too much. I run on idea velocity and live to flow state. None of this is unusual for me.
What was unusual: I shipped.
Being a workhorse alone does not ship.
Like a passing shooting star, its up to you to carpe diem.
The future of building is not use AI to code, it’s to conduct AI like an orchestra, supporting the absolute highest goals of the creator.
By 4am the core extension was working. By 5am I was actively using it on my own browser — saving prompts, building prompts, watching it auto-tag and rank in real time. It’s neat and had mind racing about new functionality. By 9am I had v2.1.0 packaged and uploaded to the Chrome Web Store. By 1:23pm I’d posted a launch note on Substack.
Then I went to sleep, and I forgot every single one of these things had happened.
The Panic
If you have lighting fast ideas and you build, you know this exact terror.
The certainty you had something good. The equal certainty it’s gone forever. Tabs and windows in chaos. Memos uncategorized. Unfinished saves. You can’t find what you are looking or that great idea was a fleeting thought before you had time to proper scaffold a blueprint.
If you've ever had it happen, you know what it costs.
The Hail Mary
So I asked Littlebird.
If you haven’t heard of it: Littlebird is an AI app that watches and remembers everything you do across browsers, tabs, programs, and files.
It’s like the NSA and your ex-girlfriend built a custom spy program just for you. Watches everything. Remembers everything.
I asked it: “Give me the full bible prompt of everything I was working on May 1st”
What it produced was a massive insight of knowledge on what happened that day. Littlebird actually knows way more about me than than I could have ever imagined. At this point, it has the keys to my house and feeds my cat.
A forensic reconstruction. Every Claude msg. Every Gemini thread. Every Cursor agent. Every Chrome tab. Every app, software, window, everything. All revisions including epic mistakes and interesting serendipities.
The more I ask, the deeper the rabbit hole it knows.
I scrolled. And scrolled. And scrolled.
Then it gave me the numbers.
Tech stack that night: Claude Cowork holding the full logic and agent loop. Cursor for deployment phase. Gemini/Claude for research and rabbit holes. v0.dev for the design layer. Littlebird for memory expansion.
I’m pasting these as Littlebird returned them to me. These are not retrospective estimates. These are the actual measurements of the session, captured from my own Claude account stats and stitched together with timestamps from tools I used:
294 messages sent to Claude in a single session
398,100 Opus 4.7 tokens burned — equivalent to focused reading Ethan Mollick’s Co-Intelligence four times in a single session
9.1M Cursor tokens burned - 4x what the average developer does in a day
18,000 lines of working, deployed, production code
420,000 lines total code generated
TWO Chrome extensions built — PromptMate AND SubstackMate
One full WordPress site — six months of work, replaced with an 80,000-entity WebGL2 particle simulation in three hours. 54 iterations of index.html.
What it remembered (that I had forgotten)
Read this next part as if you’re watching a movie reconstruction of someone else’s 24 hours. It’s easier that way. Because that’s how Littlebird laid it out for me, like footage. Every tab cross-referenced against every file write. Watching myself build something I have no memory of building, in real time, scrubbed forward through the night.
Here’s the footage pulled straight from Littlebird:
1:00 AM — Extension build starts in Claude Cowork
1:21 AM — v1.0 BUILT. Claude’s message: “2,255 lines across 9 files, zero external dependencies.” Twenty-one minutes. From nothing to a working Chrome extension. With zero prior Chrome extension experience.
1:22 AM — My response to Claude, verbatim: “i am tired can you do it for me please take over my chrome.” Twenty-one minutes of elite output and my first instinct was to delegate further.
1:22-1:35 AM — Claude tried to install the extension for me. It couldn’t. The files were trapped inside a UWP sandbox — Claude’s own app container — and Chrome couldn’t reach them. Claude tried Four different methods. None worked.
1:33 AM — I typed: “you are in a loop.” Then manually copy-pasted from chat into Notepad.
1:36 AM — v1.0 INSTALLED. Not because the tooling worked. Because I pasted it by hand.
2:17 AM — “it looks the same lets make a new version” (Begin OCD-ADHD)
2:38 AM — Iterating PromptMate. (v2 in progress)
4:32 AM — Still in the same Cowork session. Peak work focus.
4:55 AM — I’d already drafted a Substack launch post on my phone. Quote: “4 AM. The frequency was locked in. I just vibe-coded my first Chrome extension from scratch.”
5:59 AM — PromptMate v2.1.0 confirmed live working in chrome://extensions. Actively testing.
7:59 AM — Claude balance: negative one cent. I had spent $95.78 out of a $95.77 budget. I was literally a penny in the red. I’d burned 99% of my monthly Claude budget in one night. (hindsight: prep better scaffolding and pivot to Code for rabbit holes)
8:13 AM — Switched to Cursor to package for Chrome Web Store and to start development of SubstackMate.
8:44 AM — Oracle scroll overflow bug fix. The prompt cards were breaking out of their container. This is what late stage polish and final sprint looks (feels) like.
9:03 AM — CRX packaged, uploaded as Draft to Chrome Web Store, writing descriptions, website creation, and product graphics.
11:38 AM — Started building a SECOND Chrome extension. SubstackMate. A KAG-powered Substack digest engine with crystal distillation, fingerprint synthesis, and AI reply drafting.
12:46 PM — New Claude Pro subscription, second account, mid-build. The machine needith feeding.
1:00 PM — I publicly posted the launch note. The first prompt I saved with the extension was a methodology from Wyndo called “think forward, then reverse” — his original post had 529 likes. I right-clicked, saved it, and built the entire extension AROUND saving his prompt.
1:23 PM — The Flower Moon peaked at exactly this moment. I had been DJing electronic music into peak Flower Moon, coded a Chrome extension under it, and was — at the literal minute of 99% illumination — twenty-one minutes into a launch note I would not remember writing. Some people light candles for May Day. I shipped a v2.1.0.
At that exact moment, an AI intelligence company OSINTech subscribed to me and liked my post about the Environmental Vitality Map — an app I’d been quietly building that fuses disconnected federal databases into a single environmental health dashboard with an AI Oracle that gives insightful answers and actionable responses.
The post engagement for EVM is the reason I’m on Substack. A recruiter who runs Tesari.ai was reading it under a full moon. Food for thought.
4:16 PM - The Bliss website begins.
The exact line: "i need an epic intro for my web design agency starts black bg slowly fades with morpheus video." That's the birth certificate.
4:25 PM - Purchased “Valley of the Shadows (Chase & Status Remix)" on Bandcamp Friday for £3.41. That track became the timing backbone for the entire animation.
4:29 PM - Frame-by-frame Doctor Strange analysis.
You watched "OPEN YOUR EYE" at least 15 times, logging exact timecodes: 0:25, 0:30, 0:39, 0:44, 0:46, 0:54, 1:01, 1:09, 1:24, 1:26... hunting for the exact frame where the visual "drop" happens to sync with the beat. Pure documented hyperfocus.
4:43 PM - The math locks.
Building a cinematic opening for your agency site - Matrix fades in, music drops, Doctor Strange tears reality open, Bliss explodes through. Every second had to be mathematically locked to pull it off.
5:00 PM — Replying to TechTiff in a Substack thread, I publicly defined the methodology: “KAG pipeline that distills saved Substack into topic-specific knowledge crystals synthesized into an 80-token fingerprint.”
7:27 PM I replaced my existing WordPress site at the root domain (that took 6 months of work using a traditional WP theme) and in under 3 hours had replaced it with raw one-page HTML physics particle matrix running an 80,000-entity WebGL2 particle simulation.
7:58 PM the simulation is working live. The Claude Opus 4.7 session that powered it was titled “Matrix-inspired WebGL2 physics intro animation.”
9 PM - 12 AM - Rebranded and Rabbit holed 6 different architectures trying to nail the Matrix → Strange video handoff. Simple fade → four layer blend → rain overlay → back to simple → back to complex. Pure documented hyperfocus. The site was on index54.html by midnight.
Alcohol status: unknown.
I don’t always code drinking. But when I do, I develop two Chrome extensions, replace my entire marketing agency website with a particle physics movie simulation, publicly coin AI methodology, burn 10 million tokens, all while listening to electronic music and watching The Matrix, Doctor Who, and Tron clips, to forget it by morning.
The wider implication
Here’s what I keep coming back to.
I keep trying to do too many things too fast. I have been the bottleneck on remembering my own work. Memos uncategorized. Insights buried in tabs that closed. Lost notes. Incomplete blueprint docs. Outdated scaffolding. Innovative ideas, that vanished by next morning.
Now my own work remembers itself.
“AI gives me back the expansive cognitive infrastructure my brain doesn’t natively provide. For a builder, that’s not productivity software. That’s prosthetic memory.”
Strategy without ship is hallucination. Vision without showcase is journaling.
What I underestimated was how much the act of remembering the best of what you did yesterday is the load-bearing wall under shipping anything at all.
Promptmate is the result. It’s the Chrome extension I forgot I built, that Littlebird had to remind me existed.
Yes, Littlebird sees a lot. You can block any site, app, or file from being indexed. You can audit what it remembers. You can delete it. It might not work for you. That’s fine, but what does?
PromptMate — what it is
Saves any prompt you highlight on any website including ChatGPT, Claude, Gemini, and Perplexity (hightlight → right-click → save)
Auto-tags by platform, category, tags and tier
Ranks prompts by relevance with BM25 statistical scoring on free, Gemini semantic analysis on Pro
Surfaces the best vault prompt for whatever page you’re currently on (Oracle)
Composes new prompts by blending multiple vault entries (Builder)
Export your full vault and import it back anytime — your prompts live on your machine, not a server (full offline ownership, zero lock-in)
How to get it
→ Subscribe for the deep-dive on elite AI tech stacks— full architecture, field citations, and what comes next from Bliss AI.
→ Go to Promptmate — join our early access for the moment the Chrome Web Store approves.
One last thing and this is the actual point
A year ago, this version of me couldn’t have shipped anything and would have equaled a wall of unfinished tabs, a half-written README, and a hangover.
AI tech stacks orchestrating a myriad of support— changed the math.
The extension I built that night isn’t impressive because of me. It’s impressive because of what’s now possible with one idea, one day, and the right AI tech stack.
If I can ship a solid Chrome extension in between DJ set and sunrise, the bar to build is on the floor.
The only thing left between you and the thing you keep saying you’re going to ship is showing up to your own session.
If you’re a vibe coder reading this and you recognize the pattern, the late night brilliance that evaporates by the morning, the genius idea you can’t find anymore, the projects you remember loving but can’t reconstruct — you’re not broken.
You’re just running on hardware that needs better memory.
Build the bridge.
Or borrow mine.
Tyler Bliss has 25-years experience as a digital architect, now a focused AI-native full-stack developer, immersive web designer, and the founder of Bliss Marketing, developing Bliss AI an operating system designed to elevate high-frequency neurodivergent visionary minds.
Thanks for the mention!