Every content operation now has a second bottleneck. It’s not ideation, not editing, not even burnout — it’s the moment an AI agent stops mid-run and waits for a human thumb to approve the next step. I felt that exact stall recently while using Claude Code to build a small video-metadata pipeline: start the task, step away, return twenty minutes later to a terminal prompt that had been sitting there the whole time. port22, a small utility from solo maker harsha chaganti, is built around that pain. If you never run a coding agent, it still matters: port22 is the clearest working example yet of how asynchronous approval should work when AI does the heavy lifting — and that is exactly where social media production is heading.
The 20-minute promise: why a stalled AI agent is your next time sink
The launch story is specific and, for anyone who has automated content operations, painfully familiar. The maker says he builds with Claude Code and OpenAI Codex most of the day, and the thing that kept getting him was starting a long run, walking away, and coming back twenty minutes later to find it waiting for one file edit to be approved. So he built port22. It attaches to agents running on a Mac and puts them on your phone. When an agent needs permission, your phone buzzes, and you tap the actual option the agent offered — not a guessed yes/no.
I recognize that pattern because it’s the same shape as a content repurposing failure. Picture this: you’ve set up an AI workflow that turns a YouTube video into ten Shorts scripts, a Threads thread, three LinkedIn posts, and a newsletter draft. You kick it off, go make coffee, and come back to a prompt asking whether to overwrite a CSV file that drives the whole batch. The work isn’t failing. It’s waiting. And if you’re running that pipeline inside an API-hungry tool, a stalled session can also eat rate limits or refresh tokens while it retries or hangs.
The real cost isn’t the twenty minutes. It’s the context switching. When I schedule a month of content in Buffer or Later, I don’t want to be interrupted for every draft. But when an interruption does happen, I want it to carry everything I need to make the call without going back to a laptop. Most notifications fail that test. They say “Your AI run needs approval” and leave you guessing. port22’s bet is that the approval itself should be a well-lit, self-contained decision.
Why TikTok creators should care more than LinkedIn ones
If your entire content strategy is one LinkedIn post a day, a twenty-minute delay is not a disaster. LinkedIn’s feed is more forgiving; a text post published an hour late still gets read. TikTok is not that. The recommendation engine is built around watch time, completion rate, and how quickly a video picks up early engagement. A hook that was perfect at eight in the morning is stale by ten. Creators running AI-assisted hook generation, trend analysis, or batch clipping need agents to keep moving while they are away. The difference between a tool that lets an agent stall for twenty minutes and one that pushes the decision to your phone is the difference between publishing in the trend window and missing it entirely.
What port22 actually fixes (and what it doesn’t)
The core mechanic: port22 attaches to what you already run. No wrapper, no special terminal, no config. Start Claude the way you always do and it shows up. It reads the options off the live session instead of guessing a keystroke, so a six-option prompt shows six buttons, not a hard-coded yes/no. Off your network, traffic goes through a relay the maker says cannot read your code, with end-to-end encryption between Mac and phone. No account, no signup. It’s free for one Mac and two sessions with every feature on — and the maker explicitly says it’s not a trial.
That last part matters more than it sounds. I’ve tested enough early-stage tools to be allergic to the word “trial.” port22’s free tier is a trust-building move, not a growth hack, and it makes the product easy to evaluate before you grant it deeper access.
Where it differs from existing options is the decision surface. A good SSH client like Termius gets you into the machine, but it gives you a terminal — not a session-aware approval queue. You still have to find the right screen, zoom in, tap carefully. A tool like Zapier can notify you when a webhook fires, but it doesn’t know the exact question the agent is asking. The thing port22 gets right is that the phone is not a dumb remote control. It is the place where the agent’s actual decision is recreated.
In my own tests of similar approaches — remote-controlling a Mac from a phone to approve agent actions — something almost always goes wrong. The terminal wraps, the keyboard is too small, and you end up tapping the wrong shell prompt. That’s exactly the failure the maker says he was trying to avoid: approving the wrong thing because the app guessed a keystroke. Reading the real options off the live session is the difference between approving what was actually asked and approving what you assume was asked.
Where the math breaks
The promise is that a twenty-minute wait becomes a two-second tap. But the math only works if the tap is trustworthy. One commenter, Martín Herrán, asked the sharpest question on the page: does approving from your phone make you quicker and less careful? The maker answered honestly: yes, he moves faster on the phone, and he has caught himself approving things he would have read twice at his desk.
That is the tension at the heart of every remote-approval tool. A twenty-minute wait saved is a win. A twenty-second wrong approval is a disaster with a longer tail. Another commenter, Asad M., put the bar perfectly: if the approval card carries enough of the change to judge it, he’ll clear a queue from a coffee shop. If it doesn’t, the buzz just moved the interruption earlier — you still have to walk back to the Mac. So the product’s entire value lives in the card, not the notification.
Right now, the card shows the exact question and the conversation above it, and you can tap into a tool call to see code that changed. What it does not yet do is render a proper diff on the approval card itself, or let you jump into the live terminal from that screen. The maker says both are on the list, and the diff highlighting with green and red lines is in progress. Until that lands, the tool is genuinely useful but not yet the “approve from a coffee shop” dream. It’s more like “approve from the kitchen without walking back upstairs.”
Three habits content operators should steal from port22
Even if you never install port22, the product is a masterclass in how to design human-in-the-loop automation. Content teams are about to be buried in AI-generated drafts, and the tools that win will be the ones that make approval quick without making it reckless.
Habit 1: Build the approval card before you build the automation. When you set up any AI workflow, ask yourself: what will the human need to know at the moment they’re interrupted? Not just “do you approve this post?” but “here is the copy, the visual, the platform, the posting time, and the link attached to this decision.” The best scheduling tools already do this — Buffer shows you the post on a calendar before you click publish. port22 does the same for a CLI agent: it shows the conversation that led to the prompt, then it shows the actual options. Your content pipeline should do the same. If the notification only says “Draft ready,” you’re building a ping, not an approval system.
Habit 2: Attach, don’t replace. port22 does not force you into a special terminal or a new workflow. It attaches to tools you already run. That seems obvious, but most AI tooling wants to own the entire stack: import your content, duplicate your accounts, make you learn a new calendar. The tools that survive in social media are the ones that fit into your existing workflow, not the ones that ask you to rebuild it. If you’re a creator, use tools that plug into your current posting schedule and analytics stack. If a new platform asks for a week of migration work before it returns any value, it’s not a workflow tool — it’s a project.
Habit 3: Make the machine show its work. The reason port22 displays actual options is that guessing a keystroke is how automation fails invisibly. One commenter described it better than most product reviews: firing an Enter key at a six-option prompt takes option one, the session keeps moving, and nothing anywhere says a choice was made for you. You only find out an hour later when the run went somewhere you never asked for. Guessing doesn’t just fail — it succeeds loudly and wrongly.
That maps directly to AI content tools. If an agent is going to append UTM parameters to your links, the approval card should show the destination URL and the full UTM string. If an agent is going to auto-post to multiple platforms, the card should show the specific account, the platform’s character limit, and the scheduled time. The extra two seconds of reading is not slowing you down. It’s the difference between supervising AI and being led by it.
Why approval UX is the next competitive advantage for content tools
The next wave of social scheduling tools won’t compete on how many platforms they support. Every serious tool supports Instagram, TikTok, YouTube, and LinkedIn by now. The differentiator will be how safely a human can approve a queue of AI-generated content in thirty seconds. port22 is a preview of that dynamic outside social media. It treats approval as a first-class product surface, not a notification afterthought. Content teams should watch this category closely — because the same design playbook is about to be copied into every AI content tool on the market.
Where I’d hold back: trust, dummies, and the quick-tap trap
I want to be clear about who should not install port22 this week. If you’re a social media manager whose only automation is a Zapier integration and a Canva template, you don’t need this. It’s built for people who run long-lived terminal agents — the source itself says the maker wants feedback from people who “run agents all day.” Non-technical creators should watch the product from a distance, not install a CLI companion on their only computer.
Security is the bigger open question for me. The maker says the relay cannot read your code and that traffic is end-to-end encrypted between Mac and phone. But no security audit is disclosed, no open-source client is mentioned, and the product is early. If I’m going to run this next to client API keys, saved passwords, or unpublished YouTube videos, I want more than a launch post. This is not a criticism specific to port22 — it’s the same question I ask about every tool that asks for deeper access to my machine. “End-to-end encrypted” is not the same as “independently verified.” The source says not disclosed, so I’m holding judgement until there’s a security page or at least a more detailed technical post.
The bigger risk is psychological. The maker admitted in the comments that approving from the phone makes him faster and less careful. That is a human truth, not a bug. The product can mitigate it by showing the diff, the conversation, and the exact option — but it cannot remove the temptation to tap quickly. My rule for any tool like this: if you can’t restate the change in your own words, don’t approve it. That rule is easy to state and very hard to follow when your phone buzzes during a meeting.
So who is port22 for right now? Indie founders and technical creators who run Claude Code or Codex on a Mac, have long-running sessions, and want to unblock routine decisions without being glued to a laptop. It’s for people who understand what they’re approving. It is not for everyone, and it doesn’t pretend to be.
What I’d watch / test next
This week, if you run coding agents, the test that matters is the one nobody can fake: install it, launch a real long-running task, then leave your Wi-Fi and approve a request from cellular. The comment section already asks whether the relay works once you’ve actually left the house, so that’s the exact scenario to push.
For content operators, spend an hour auditing your AI workflow for stalled-agent moments. Where does automation stop for a human? What does the notification show? If all you get is “Draft ready,” add context. That might mean a Zapier step that pulls in a preview, a scheduled Slack message with the full post, or a manual review step in the calendar. You don’t need a new tool; you need better approval cards.
Then watch whether port22 ships the diff-in-card experience. The maker says green-and-red highlighting is on the way. If that lands, the tool becomes a template for trustworthy remote approval — and every social scheduling tool should copy it. If it doesn’t, port22 remains a niche utility for developers. Useful, but not the preview of the creator economy’s future I think it could be. My bet is that the approval card becomes the most important UI in AI-assisted content production. The sooner content tools treat it that way, the sooner we can all stop walking back to the kitchen to check the screen.
