A few months back I wrote about running an always-on Claude agent from a Mac Mini in my apartment. Telegram bot. Cron jobs. Browser automation. The kind of setup you have to want to build.
Poke is what happens when someone wraps that idea for people who do not want to install a daemon. Some have called it OpenClaw for normies, which is a fair shorthand. Chat-first AI assistant. Integrations they call "recipes." Reportedly $300M raised, depending on which post you trust. Whether the number is exactly right or not, the category is real and worth paying attention to.
I have been using it daily for about a month. Here is where it lands.
What Poke actually is
Poke is a consumer AI assistant you talk to in a chat thread. You give it access to the apps you already use through recipes, and it does work on your behalf. Calendar. Email. Notion. Strava. Vercel. A flight tracker. A few others.
If you read my always-on agent post, the pattern is familiar. The difference is that Poke hides the Mac Mini. There is no daemon to install, no caffeinate command to run, no BotFather to message. You sign in, connect your accounts, and start chatting. That packaging matters more than people give it credit for. Most of the people who would benefit from an always-on agent are never going to spin one up themselves.
The unexpected win is calorie tracking
I went in expecting calendar and email to be the killer features. The thing that quietly stuck was calorie tracking.
I had been using Cronometer for a while. The data is good. The UI is clunky enough that I open it less than I should, which is the whole game with food logging. If the friction is high you stop doing it, and a calorie tracker you do not open is worse than nothing.
Poke is a chat interface. I send a photo of what I am eating and it estimates the dish and the portion. The image recognition and portioning are at least as good as what I was paying for. The thing that actually makes it better is that I can shape the loop in one sentence. I told it: when you are not sure what is in the photo, ask me. And every time I send a food picture, ask me whether there is dressing, oil, or sauce I have not mentioned. It started doing that immediately and has not stopped. That kind of refinement is two minutes of conversation. In Cronometer it is a settings page I would never find.
Pair that with the Notion recipe and you have something durable. I asked Poke to keep its long-term memory about me in a Notion page and to append a daily food log there too. Now there is a single source of truth for what I have been eating, what it knows about me, and what I have asked it to remember. That outlasts the chat thread.
Where it breaks. The flight that was late.
A friend was flying out at 5pm. I asked Poke to ping me when boarding started and when the plane landed. Standard request. The kind of thing you would tell a human.
It nailed both of those events. It also missed the only thing that actually mattered: the flight was late.
When I asked about it later, Poke told me the flight tracker integration had been pinging it repeatedly, the volume looked off, so it had turned the integration off. It followed the letter of my instruction. Tell me at boarding. Tell me at landing. The spirit of the instruction, which any human would have read as "keep me in the loop about this flight," got lost.
This is the same gap I wrote about in the bottleneck is not the model, it is the interaction. The base model is fine. The interaction design is the thing that breaks. An assistant that does exactly what you said and nothing more is less useful than one that understands what you would have wanted.
Recipe by recipe
Quick verdicts on what I connected.
Notion. The unsung hero. Memory and a food log in one place. This is what makes the calorie use case stick across days and weeks instead of dying inside a chat thread.
Calendar and email. Solid. Drafting replies, reading threads, setting reminders. The reminders fire reliably, which is more than I can say for most assistant features I have tried.
Strava. Cool that it can read my runs. The data lags, so when I ask about a run I just finished it often does not see it yet. Useful as a weekly summary, not as a live coach.
Vercel. Noise. It pings me on every build, which Vercel already does. Connected and disconnected within a day.
Flight tracker. See above. The tool exists. The judgment about when and what to surface does not.
The three things missing
Three gaps I would close before anything else.
- Location. Siri-level location awareness. Reminders without location are half a feature. "Remind me to grab the package when I am home" should just work.
- Health and steps. Poke has the food side of the equation. Without steps, heart rate, or sleep, the calorie loop is one-sided. The data is sitting on my phone.
- Intent over literal. This is the deep one. Most of the misses I have had with Poke, including the flight, are the assistant taking my instruction word for word instead of reading what I actually wanted. This is not a model problem. This is the interaction design problem the rest of the industry is starting to wake up to.
Final thought
I do not love everything about Poke. The flight thing annoyed me. The Vercel recipe should not have shipped. Strava is half wired up. And yet it has already replaced a paid app I used for years, because the chat surface plus a couple of well-placed recipes is a better fit for how I want to log my day than any app I have tried.
The gaps are not model gaps. They are gaps in how the assistant decides what to do with what you tell it. That is the bottleneck for this whole category right now, and it is the most interesting place to be working.
AI assistants are at the top of my list for what AI is actually going to change in everyday life. More than chat windows. More than image generators. The version of this that has location, health, and a sense of intent is going to feel like a step change.
If this is the kind of thing you think about, stick around. I write here about AI and what it is actually doing to how I work and live, as often as I have something worth saying.
