u/penguinothepenguin

disclosure up front: I work on Slashy and there's a link at the end. the automation breakdown is the actual point, judge it on that.

for about a year my email/calendar "automation" was the usual pile: a few zaps, a couple of cron scripts, some keyword rules. it worked until anything needed judgment. is this email actually urgent. who is this person. does this meeting request collide with something. every time I tried to automate one of those I ended up hardcoding a dumb rule that broke within a week.

The realization that fixed it: I was trying to make deterministic automation do a judgment job. the fix wasn't a smarter zap, it was giving Claude the actual inbox and calendar so the judgment steps run with real context instead of a keyword guess, and leaving the genuinely deterministic parts as plain automation.

concrete, what's now reliable instead of brittle:

- morning: Claude pulls unread from a defined list of people, summarizes, drafts replies for the ones that need one, queues them for my approval. the old script could fetch mail but had no idea what mattered.

- meeting requests: it checks the actual calendar, proposes times that don't collide, writes the email. I send. the part that used to need babysitting is gone.

- before any call: it assembles who this person is + last thread + calendar into one brief automatically. killed three tabs.

the thing that makes it production-stable: it is not autonomous. it drafts and proposes, I approve anything that leaves the building. an automation that sends the wrong

Thing once is worse than no automation, especially with email where you can't unsend. the scheduled parts run on triggers, not a polling loop burning tokens. setup is OAuth, no API keys sitting in a config file, and it runs over MCP so it works inside Claude (and Cursor/whatever speaks it) rather than being one more siloed app.

The tool is Slashy if you want to look: https://slashy.com genuinely curious what everyone here uses for the judgment-heavy steps of their automations, because "deterministic automation + Claude in the right place with real context" is the pattern that finally held for me and I want to know where it breaks for others.

I keep having the same four arguments with people wiring AI into their inbox. Posting them so I can stop repeating myself.

"It should just handle my email autonomously."

No. Email is irreversible and adversarial. The cost of one wrong sent message isn't symmetric with the time saved on the other 200, it can end a customer relationship you spent two years building. What you actually want is it drafting everything with full context and you hitting send. You keep one checkpoint, the only one that mattered.

"The model isn't good enough yet, that's why this fails."

Usually not the model. The failure is handing it a goal ("manage my inbox") instead of a job ("draft a reply using this thread and my calendar, queued for approval"). Same model, completely different reliability. The bottleneck is scope, not intelligence.

"More autonomy means more productivity."

Backwards in practice. The setups still running six months later are the boring constrained ones. The autonomous demos are the ones quietly ripped out after the first 2am misfire. People keep the version that prepares, not the version that decides. I can't give you a clean failure-rate stat because everyone defines failure differently, but the direction is consistent across every build I've seen.

"I need it to be smart. Context is a detail."

it's the whole thing. An AI guessing at your week writes confident nonsense. An AI that can actually see your inbox, calendar and prior threads writes the reply you would have written. The judgment problem is mostly a context problem. This is the part people underrate the most.

The honest version of the takeaway: if you can describe your email process as steps on paper, you want the AI in the judgment slots with a human on send, not an autonomous agent over the whole thing. Rule of thumb, not a law, some open-ended cases are real, but it sorts most people correctly. The reason I land on "give it real context, keep the human on send" is that's literally what we built Slashy as, an MCP server and Mail Client that lets the AI see your actual mail and calendar and draft against it, autonomous by nobody's request. you can search Slashy

Curious which of these four you'd push back on, and what's actually working in your own setup.

Hey everyone! I made a small site to help people find the moment their name was called during Georgia Tech Spring 2026 Commencement:

https://gtgradmoments.com

The idea is simple: instead of scrubbing through the full commencement livestream, you can search for a graduate’s name and jump straight to the clip where they walk across the stage/ get announced.

https://preview.redd.it/5lg4nykeaj0h1.png?width=961&format=png&auto=webp&s=6c16f3d65323b52f7abe1e4d70644cbd85ba8d9f

I built this because I know a lot of families and friends want to save or share that moment, but it can be annoying to find in a long recording. The site has an all-graduates list too, so you can browse if OCR/search doesn’t catch the exact spelling.

A couple notes:

* This is unofficial and just something I made to help people.

* The indexing is based on OCR, so there may be mistakes.

* If your name is missing, misspelled, or linked to the wrong moment, comment or message me and I’ll try to fix it.

Hope this helps some grads and families save their commencement memories! 🎓

--
Harsha (C/O 25)
My email is Harsha@slashy.com