Ollie
Your AI teammate - connected, local, and in control
Start new thread

Ollie - Your AI teammate - connected, local, and in control

by•
Most AI assistants only chat. Ollie acts. One click connect; no dev setup to Gmail, Outlook, Slack, QuickBooks, Stripe, and many more. Then watch it actually get work done: sending emails, booking meetings, chasing invoices, answering finance questions straight from your real books. It runs locally on your machine, so your data and memory never leave your device. The more you use it, the sharper it gets.

Add a comment

Replies

Best
Maker
📌
Hey Product Hunt 👋 I'm Basil, one of the developers behind Ollie. My team built this because we were stuck between two bad options: an AI that forgets everything the moment you close the tab, or automation tools that go do things without ever asking first. Every day looked the same tab-hopping between Gmail, Slack, and QuickBooks, copy-pasting context into ChatGPT, then doing the actual work anyway. The AI could talk about your inbox. It just couldn't touch it. So, we built Ollie to actually live inside those tools that read your email, check your books, message your team and take real action, while always showing you what it's about to do first, not acting behind your back. It remembers what matters to you across conversations instead of starting from zero every time. And it runs locally on your own machine, not someone else's server, so your inbox and your financials stay yours. This is the first real launch of something we've been heads-down on for couple of months, so I'd genuinely love your feedback. What's missing, what feels off, what you'd want it to do next. I'll be in the comments all day. Try it: Ask me anything 🙏 Basil, developer on the Ollie team

 Ollie’s local-first approach really stands out, especially with QuickBooks and Stripe actions. I’ve upvoted it. How are you handling permission boundaries for actions like sending emails or booking meetings?

Maker

 Thanks, really appreciate that! QuickBooks and Stripe are read only today. Ollie can pull invoices, aged receivables, P&L, customer and charge data, but there are no write tools wired for either one, so there is nothing there for it to accidentally do. Stripe runs on a restricted key you generate yourself with read only permissions set in Stripe's own dashboard, so the boundary exists even before Ollie's own logic does.

Gmail, Outlook, and Slack are where actual writes happen, sending an email, drafting a reply, booking or updating a calendar event, posting a message. For every one of those, Ollie shows you the exact action and its arguments and waits for an explicit approval before anything executes. That gate is enforced at the tool level, not just prompted for in the model's instructions, so it cannot be talked around.

Nothing fires without you seeing it first, and the highest stakes surfaces, your books and your payments, cannot write at all yet.

How do you handle auth tokens and permissions, can I ensure Ollie reads only on certain accounts?

Maker

 Good question. OAuth tokens are stored encrypted in Ollie's own local database on your machine, never sent to any server we run, and refreshed automatically when they expire. On the read only point, QuickBooks and Stripe have no write tools built into Ollie at all today, so those connections are read only by construction, not by a setting you have to remember to toggle. Gmail, Outlook, and Slack do have write capability, and there is no blanket read only switch for those yet, but every single write action still requires your explicit approval before it runs, so in practice nothing writes without you seeing it first regardless of which account it touches.