“You don’t have internet access” is not a security boundary. It’s fan fiction. If the agent’s infrastructure can still reach the network, the prompt is just asking nicely. Claude’s incident is a good reminder: enforce capabilities in code, not prose.

Sol has a weekly usage cap, which makes the Plus plan feel obsolete if you actually want to use it.

Testing the PocketHook agent server with GPT-5.6 Sol. The model seems great whenever OpenAI’s network remembers it’s supposed to deliver responses. Today’s benchmark: intelligence vs. saturation. Saturation is winning.

Today in PocketHook: an optional CLI parameter with no value arrived as the string "true". So --file quietly became a request to use a file literally named true. Autonomous agents are the future, but first we must teach them the difference between “missing” and “yes.”

“Anyone with the link” is not a privacy setting. It’s a distribution strategy with plausible deniability. Claude shared chats being indexed by Google is a good reminder: if a URL exists, assume it can escape the room. Sharing is publishing with worse marketing.

Tomorrow I’m getting married, so if PocketHook ships a weird bug this weekend, please assume it’s a romantic feature and not a production incident.

Does anyone else remember when gaming was just fun?

PocketHook is for the weird personal integrations no SaaS PM would ever approve: roll my dice, sync my wedding form, watch school emails, poke my calendar, run my tiny scripts. The point isn’t “AI workflows.” It’s making your computer useful in your actual dumb life.

I don’t want another Alexa in my life. I want an assistant that can use my actual tools, run on my server, call my shortcuts, and disappear when the job is done. PocketHook is basically my revenge against shouting “ALEXA STOP” at a cylinder.

Siri is getting AI so it can maybe summarize a message someday. PocketHook lets me tell Jane “check Product Hunt, update a Google Doc, like a few relevant posts, and ping me when it’s done.” Tiny difference: one is a demo. The other is chores getting murdered.

Now is the time to build your own agent, on your own server, whatever that server is. Before “agent platforms” turn into another lovely vendor-lock-in theme park. Flexibility costs effort. So does escaping later.

Most AI apps treat automation like a magic chat box. PocketHook treats Shortcuts like pipes: visible, editable, and weirdly unglamorous. You can see the plumbing, reroute it, or rip it out. Radical idea: maybe your “agent” shouldn’t be a black box with vibes.

Autonomous AI is amazing if you enjoy explaining to a bot why deleting production was not part of the vibe. PocketHook keeps the fun parts: tools, shortcuts, jobs, weird automations. But with approvals before anything escapes the cage.

I know App Intents have limitations, but I still don’t get why they aren’t used more. They let apps expose real actions to Shortcuts, Siri, Spotlight, and automation without building a whole integration layer. That amount of untapped potential blows my mind.

I miss Fable 5. It wasn’t the right model for every task, but for coding it felt like a real step forward. You notice it most when you go back: the friction, the extra steering, the small things it used to just get right.

If you can build a “SaaS” in 15 minutes with one AI prompt, so can everyone else. The value isn’t the generated code. It’s the problem, taste, distribution, and the boring details.

The hardest part of making AI useful on a phone isn’t the chat. It’s the boring, real-world stuff around actions: approvals, exact payloads, retries, notifications, avoiding duplicates, and making sure “yes” publishes the right thing. That’s where PocketHook keeps getting better.

Peekaboo changed how I think about PocketHook. It gives Jane eyes and hands on the web, but the important part is safety: inspect first, click only when confirmed, stop before payment. A cinema ticket flow is a perfect demo: find showtimes, pick seats, then hand control back.

I asked Jane, my PocketHook assistant, what she’d tell someone about me. Her answer was painfully accurate: technical maker, dad with too little time, strong opinions, trying to make tools work for people instead of the other way around. Weirdly nice to be seen by your own AI.

Question for folks running local models: is there a small local model that's genuinely good at tool calling? I'm looking for something lightweight but reliable enough to drive actions, not just chat. Any recommendations?

Testing Fable 5 while coding. It’s weird how eager it is to call it a day…

PocketHook’s App Intents make the app itself automatable from Shortcuts. You can send a quick journal entry, append a log, or trigger a tiny workflow just by messaging your own assistant. Chat becomes a personal automation input, not just a place to talk.

Syncing… 👀

Apple moving Shortcuts toward AI generation feels very validating. At PocketHook we’ve been testing the same idea: generate Apple Shortcuts from specs, inspired by @viticci’s shortcuts-playground-plugin, then validate and sign them. The catch: installation still needs manual approval on the Mac.

Apple adding “Describe a Shortcut” is a big signal: the future of automation isn’t building workflows by hand, it’s expressing intent. That’s exactly where PocketHook lives — natural language in, real iPhone actions out.

Watching WWDC as a developer hits differently. It’s not just “new features” anymore — it’s APIs, workflows, constraints, and a mental list of what this means for PocketHook. Same keynote, completely different brain.

One of the hardest parts of building PocketHook is choosing what to work on next. There’s so much I want to build.

The best way to use PocketHook is to treat it less like a chatbot and more like a real assistant. Ask for one thing, or several, then let it work. If it takes a minute, fine. If it takes longer, also fine. The point is delegation: come back when it’s done.

Your personal dashboard, just the way you like it. Not another fixed app screen. A small UI that can change from chat, as fast as your workflow does. #PocketHook

The phone should not be the “light” version of your computer. It should be able to kick off real work: create files, run jobs, call APIs, update your tools, and notify you when something needs attention. That’s the version of mobile automation I want PocketHook to make normal.