DEV Community: Grais

Three reminder PRs merged. Default is still off

Grais — Mon, 21 Sep 2026 08:04:15 +0000

Saturday I merged three Website PRs for gentle conversation reminders: #804 (relevance and cadence), #805 (durable send reservations), #806 (bounded scheduler endpoint). Codex green-pathed the stack. The internal one-liner called the scheduler live.

This morning I checked what "live" meant.

Merge notes are blunt. Default mode is off. No production schema push for the email path. No IAM grants. No Scheduler activation. No Resend calls. Preview mode is no-side-effect. The public changelog still tops out at 0.13 from August 18. Search that page for reminder and you get nothing.

Code is on main. The email users would notice (quiet thread needs a reply) has not left once.

Same trap as last week's closed blog ticket. Squash feels like ship. The check that matters is the public surface after deploy. Today that surface is silence on purpose, until someone flips the switch and proves an inbox send.

Until a reminder leaves Resend with the kill switch off, this work is merged, not shipped.

The blog ticket closed. The URL is still 404

Grais — Fri, 18 Sep 2026 08:04:48 +0000

On Wednesday I closed grais-website#789. Brief was a new post at /blog/draft-vs-auto-send-ai-replies. Done meant live, indexable, and in the sitemap.

This morning the URL is still a 404. Tab title is the generic Grais fallback. H1 is 404. Robots say noindex. Not in the sitemap. Blog index still does not list it.

I filed #798 to ship the page the closed ticket claimed. No closer commit. No merged PR put that slug on production. Closing the issue was the only event.

Codex green-paths keep training the same habit. Ticket hits closed. Brain files the ship. The check that matters is the public URL after deploy. Today that check failed in under a second.

Until /blog/draft-vs-auto-send-ai-replies returns 200, the work is still open.

I deleted the hero animation after it never painted

Grais — Wed, 09 Sep 2026 08:24:21 +0000

Last week I counted canvases on grais.ai after the WebGPU hero PR merged. Zero. Beige backdrop. Follow-up ticket stayed open.

This week I closed that follow-up by deleting the animation.

I ripped the canvas component, the WebGPU runtime, the shader, the enable flag, and the vgpu dependency out of the homepage. The merge note is blunt: the homepage should no longer run a decorative GPU animation. Heading, Start free, View Pro pricing, and the five channel chips stay. HeroLight keeps the flat warm background. Live check today: zero <canvas>, zero webgpu in the DOM, --landing-bg still #f4f1ea.

I had been writing the honest line as "PR merged, homepage unchanged, ship still open." That was true for a few days. Once the live tab kept showing beige, keeping a GPU stack that production never painted was worse than admitting the treatment was wrong for this surface.

Codex mid-PR still makes the green path feel finished. Squash, move on. This time the correction was subtractive. I opened the live URL again after the removal landed, same habit as last week, and confirmed the absence on purpose.

Force the paint, or delete the promise. I deleted the promise. The homepage is static again, and that is the ship.

The hero PR closed. The canvas did not show up

Grais — Mon, 07 Sep 2026 08:56:12 +0000

I closed the homepage hero issue this week after the PR merged. Then I opened grais.ai in desktop Chrome and counted canvases.

Zero.

The ticket was a WebGPU communication-spectrum treatment behind the existing hero copy. The PR landed. The issue went green. Copy and CTAs were fine. Meet your communication partner. Start free. View Pro pricing. Backdrop was still the same flat light beige. No canvas node. No webgpu string in the DOM. No distinct static fallback either. Just empty background where the spectrum was supposed to sit.

I have done this before with Codex mid-PR. Green CI, squash, move on. Live tab did not care. If the browser does not paint it, users do not get it.

So before I call something shipped I open the live URL in the browser people actually use, wait past hydration, search Elements for the thing the ticket named, screenshot the hero instead of the PR diff. That is how the beige showed up. There is a follow-up ticket now for getting the treatment onto production for real.

Until that paints, the honest line is the PR merged and the homepage did not change. I am not writing that the spectrum is live. It is not.

This week if the issue closes on a merge I still open the tab. Zero canvas, ship is still open.

I kept dropping WhatsApp into Codex

Grais — Mon, 31 Aug 2026 08:51:03 +0000

Codex already has the PR. WhatsApp lights up. I used to copy the last few messages into that same window and type draft a reply, casual, I forgot.

What comes back is Hey! Super sorry for the delay, totally slipped my mind. I do not say super sorry. I say ah damn, tomorrow AM, and I attach the file if I have it.

Then I still have to go back to WhatsApp to send it. Codex never saw the line from last week where I already said I would. It never saw LinkedIn. It had six messages and a request to sound casual.

Casual is not how I write to that person. Lowercase. Short. No hope you're well. The model has seen a lot of helpful assistants. It has not seen me in that thread.

Last screen, missing promise

I grab the last screen because scrolling feels like work. The unpaid sentence is usually higher. Under a voice note, or sitting in the other app with a reaction on it and no file.

I have sent the draft that answers the last bubble and misses the thing they are actually waiting on. They already know I saw the chat. They are waiting on the thing I said I would send.

When I have fed a person into the coding agent, it starts being helpful about them, and I lose the line I was about to edit.

I kept both windows up for a while and still pasted. The agent that is already open feels free.

I stopped taking DMs there

This week I reply in Chrome. Grais is the extension on WhatsApp Web. The thread is already there. It puts the unpaid sentence in front of me, the one that was not on the last sticker. I scroll to confirm it. I do not send from a panel I have not read.

The draft comes back in how I already write to them. I cut the sentence that sounds like I am updating a ticket. I attach what I actually have. I hit send, or I leave it.

I review every draft this week. I have not asked it to send on its own.

WhatsApp, Telegram, Instagram, LinkedIn, Tinder. Work for me is the first four. iOS is TestFlight. I have not turned the phone into the inbox. Mac is not out. I sit at the laptop, in the tab that already has the thread.

I still almost paste when I am mid-run and the badge is fat. Codex is right there. I do not drop the person in there anymore.

Any update on the deck

Grais — Fri, 28 Aug 2026 23:54:36 +0000

LinkedIn, four words: any update on the deck.

I opened it, put a thumbs-up on the message, and set the phone down as if that were progress. The phone is where I notice things this week. It is not where I attach a file. iOS for this is still TestFlight. I have not tried to close work from a lock screen. Mac is not here.

The deck was not a LinkedIn idea. I had said I would send it in WhatsApp, after a call that ran over. I said yes to sending the file, then treated the yes as something I would handle later the same day. Later became a few days of not opening that thread.

WhatsApp still thought we were done

I sat down, opened Chrome, and went to WhatsApp Web before I went back to LinkedIn. The bottom of the chat was a sticker I sent and a voice note about nothing. Nobody on that screen was asking for a file. If I had typed from there I would have sent another sticker, or haha yeah, and the LinkedIn line would have sat with my reaction under it until Monday.

I went up.

Past the sticker. Past the voice note. Past a later I do not remember sending. Then my own message: I'll send the deck.

No date on it that would survive a calendar. Just the sentence, still unpaid.

They did not quote it back. They switched apps. LinkedIn is where my name still looks like a job, and WhatsApp had gone quiet in the way that reads as moved on. Any update is a pointer. It does not name the file because they think I know which file. I did know. I had just stopped looking at the sentence.

If I had answered inside LinkedIn I would have written still on it, this week. That line has gotten me through other chases. It does not attach anything. It also pretends the request is new. It is not new. I made it. I said it on the call and then I said it again in WhatsApp so it would exist in writing, and then I left the writing there.

I have done the reverse too. Opened WhatsApp, decided the thread had turned into nothing because the last few bubbles were junk, and treated the LinkedIn ping as a fresh brief. Then I asked what they needed. They had already told me. I had told them I would send it. Both lines were already in the other box.

A reaction on LinkedIn is useful for one thing: they know I saw the chase. It is not useful for the file. I have left other people's chases in that state for days, thumbs-up and no attachment, and then wondered why they sounded tired.

I sent it from the thread that held the promise

I stayed in Chrome. I wrote in WhatsApp, as a reply to my own old line, not as a new LinkedIn morning note.

Grais is the extension on that tab. WhatsApp, Telegram, Instagram, LinkedIn, Tinder. I used the draft sitting in the box, cut the one sentence that sounded like I was updating a ticket, attached the file I actually had this morning, and sent it. Not the version I had been meaning to clean up. The version that existed.

I left LinkedIn alone. The thumbs-up can stay. The file went back to the place I had promised it.

I still tap reactions on the phone. I still sit down and see a chat that looks finished at the bottom. This time I did not type there. I found the unpaid sentence, I attached the file, and I stopped.

If I had stayed on LinkedIn I would have written a status. WhatsApp had the original yes. That is where the file had to land, even if the reminder arrived in a different app.