29.10.26

"We Bought You ChatGPT": Setting AI Expectations With Clients


When a client thinks AI makes everything instant, you fix it with one short conversation about scope, time, checking and price, before the work starts. Setting realistic AI expectations with clients isn't about saying no to AI. It's about showing them the part of the work they can't see.

Here's a real example of how it goes wrong, and the exact words I'd use to stop it.

The 500-Images-a-Week Story

In September, someone posted on Reddit's r/buhaydigital with the title "Local company expects us to generate 500 AI images PER WEEK."

They work in-house in marketing at a mid-sized online retail company. After the company bought AI tools, 500 AI images a week, about 2,000 a month, got added to their KPIs (the targets their performance is measured on). That was on top of their existing workload.

The poster summed up management's attitude like this: "We bought you Chatgpt, so just generate a bunch of photos."

Then they listed what one usable image really takes: writing prompts, generating several versions, checking for AI errors, making sure the products look accurate, fixing things and regenerating. One reply (11 upvotes) said it best: "Sounds like management is hallucinating worse than AI."

The top reply (17 upvotes) suggested a smarter move: run a small pilot batch first and measure how long the checking actually takes.

Why AI Expectations With Clients Go Wrong

Clients see the fast part. They type a prompt, get an answer in seconds, and think the job is done.

They don't see the checking. AI "hallucinates," which means it states wrong things with total confidence. It can also put the wrong label on a product or invent a statistic. Someone has to catch that, and that someone is you.

There's a second problem. On r/freelance, in a thread called "AI has completely changed freelance work and honestly, I'm struggling with it" (265 upvotes), one commenter (29 upvotes) put it this way: "a conversation can solve someone's problem now and they won't pay you for a conversation."

And a third: another r/freelance post (113 upvotes) was about a former client who came back eight months after the project ended, asking the freelancer to "fix" what ChatGPT says about them, for free.

Scripts for Talking to Clients About AI

You don't need a big speech. You need a few calm sentences ready before the topic comes up.

Scope. Agree on what "done" means, not just what AI can produce.

"AI can make dozens of drafts in an hour. What you're paying me for is the ones that are accurate and ready to post. Let's agree on how many finished pieces you need each week."

Time. Use the pilot idea from that Reddit thread.

"Before we commit to a number, let me run a small test batch this week. I'll time the whole process, including checking and fixing, and we'll set the target from real numbers."

Quality checks. Make the checking visible so it stops being invisible work.

"Every AI draft goes through my check before it reaches you: facts, names, numbers, and whether it sounds like your brand. That step is why you can post it without worrying."

Pricing. If AI makes you faster, don't hand all of that speed back as a discount. Price the result, and list the review as its own line.

"I use AI to speed up the first draft, so you get more output for the same budget. My rate covers the finished, checked work, not the minutes the tool takes."

Old work. The eight-months-later thread had a fix in the comments (21 upvotes), a line you can put in your contract: "the deliverable reflects the facts at the time it's delivered. anything that changes after that is a new engagement, new quote, no exceptions."

What This Means for VAs

When a client says "just use ChatGPT," they're telling you they don't see the work AI doesn't do. That's an opening.

The VA who explains the checking, runs a quick test and prices the finished result looks like a pro. The VA who quietly says yes to 500 images a week burns out.

Pick one of the scripts above and save it in your notes today. The next time a client gets excited about a new AI tool, you'll have your words ready.

If this helped, tell me the wildest AI request a client has sent you.

28.10.26

30 Free Virtual Assistant Prompts for ChatGPT and Claude


Here are 30 free virtual assistant prompts you can paste into ChatGPT or Claude today, sorted by the task in front of you. Every one of them tells the AI to ask before it guesses.

I use prompts like these every day in my own VA work. Search for a list like this and almost everything that comes up is a paid prompt pack. So here's mine, free, and you can copy any of them straight off the page.

How to Use These Virtual Assistant Prompts

Anything in [square brackets] is yours to fill in: the client's name, their tone, the email you're working on. The more real detail you give, the better the answer.

You'll also see the same three habits in almost every prompt: ask me questions, flag what you're unsure about, and don't make things up. AI tools sometimes fill gaps with confident guesses. Those lines make it show you the gap instead, so you can check it before your client ever sees it.

One privacy rule before you paste anything. Leave out passwords, bank details and anything your client hasn't agreed to share with an AI tool. If you use Claude, its privacy settings have a toggle for whether your chats help train future models, and you can switch it off.

Inbox and Email

Email is where most of us start, so these come first. They sort, draft and nudge, and none of them send anything. You stay the one who hits send.

1. Sort this inbox

You're helping me manage [client name]'s inbox. Below are [number] emails. Sort them into: Reply today, Reply this week, FYI only, Can archive. Give one line on why for each. If you can't tell how urgent something is, put it under "Not sure" and tell me what you'd need to know. Don't guess at deadlines that aren't written in the email.
[paste emails]

2. Reply in my client's voice

Draft a reply to the email below for [client name], who is [role] at [company]. Their tone is [warm and brief / formal / casual]. The reply needs to [goal]. Keep it under [100] words. Don't promise dates, prices or anything that isn't in the email or my notes. If something is missing, write [CHECK: what's missing] in the draft instead of filling it in.
Email: [paste]
My notes: [paste]

3. Polite follow-up

Write a follow-up email to [recipient] about [topic]. We first wrote on [date] and haven't heard back. Give me two versions, one friendly and one firmer, both under 80 words. If you need the original email to get the details right, ask me for it first.

Calendar and Scheduling

Time zones are where small mistakes get expensive. These prompts make the AI show its working, so you can spot a wrong offset before a client misses a call.

4. Find a time across time zones

[Client name] is in [time zone] and works [hours]. The other person is in [time zone] and works [hours]. Suggest 3 meeting slots in the next [5 working days] that fit both working days. Show each slot in both time zones. If daylight saving time could change the offset on any of those dates, say so and tell me to double-check. Don't assume.

5. Review next week's calendar

Here is [client name]'s calendar for next week: [paste]. Point out double bookings, back-to-back meetings with no break, days with no time for focused work, and events missing a location or video link. Don't move anything. Just list what you'd flag and a suggested fix for each.

6. Offer meeting times by email

Write a short email to [person] offering these times for a [30-minute] call with [client name]: [times, with time zone]. Ask them to pick one or suggest another. Their time zone is [time zone]. If any slot falls on a weekend or very early or late for them, point it out to me before you write the email.

Meeting Notes

A transcript is only useful once someone pulls the decisions out of it. These three get you from messy notes to something your client will actually read.

7. Transcript to action items

Below is the transcript of [meeting name] on [date]. Pull out: decisions made, action items (with owner and due date) and open questions. Use only what's in the transcript. If an action item has no clear owner or date, write "owner unclear" or "no date given" instead of guessing.
[paste transcript]

8. Recap email

Turn these meeting notes into a recap email from [client name] to [attendees]. Start with the 3 most important decisions, then the action items with owners. Keep it under [200] words and easy to skim. Copy numbers and dates exactly as they appear, and mark anything that looks contradictory with [CHECK].
Notes: [paste]

9. Brief before a meeting

[Client name] is meeting [person or company] on [date] about [topic]. Using only what I paste below (past emails, their bio, old notes), write a one-page brief: who they are, what we've discussed before, open items, and 3 questions [client name] could ask. List anything important that's missing under "Gaps" at the end.
[paste]

Research

Research is where an AI is most tempted to sound sure when it isn't. Each of these asks it to separate what it knows from what you should check.

10. Compare options for a client

I'm researching [type of tool or service] for [client name], a [type of business] with a budget of [budget]. Compare [option A], [option B] and [option C] on price, main features and [what matters most to the client]. For every price or feature, tell me how sure you are. If you can't confirm current pricing, say so plainly so I can check the official site.

11. Quick research brief

Write a short research brief on [topic] for [client name], who needs it to [purpose]. Start with a 3-sentence summary, then the key points, then what's still uncertain or disputed. Keep facts you're confident about separate from things I should verify. Don't make up statistics or sources. If my request is unclear, ask me up to 3 questions before you start.

12. Find the claims I need to check

Here's a draft [post / email / report] for [client name]: [paste]. List every factual claim in it: numbers, dates, names and quotes. For each one, tell me whether it needs a source and what kind of source would confirm it. Don't mark anything as true unless it's common knowledge.

Client Communication

These are for the messages that need a bit of care: a tone fix, an awkward conversation, or the weekly update your client skims on their phone.

13. Fix the tone, keep the facts

Rewrite this message to [name] so it sounds [calmer / warmer / more professional]. Don't change any facts, dates or amounts. Under the rewrite, list what you changed and why in a few short lines.
[paste message]

14. A tricky message

Help me write a message to [client name] about [situation, e.g. a delay or a request outside our agreement]. What I want: [outcome]. What I can offer: [options]. Keep it honest and short, with no over-apologising. Ask me questions first if you need more context about our agreement.

15. Weekly update

Write a weekly update for [client name] from me, their VA. Done this week: [list]. In progress: [list]. What I need from them: [list]. Put the "need from you" part first and keep it under [150] words. Don't add tasks I didn't list.

Social Media

Good for first drafts of client posts. The rule in all three: no claims, prices or stats the client didn't give you.

16. Caption options

Write 3 caption options for [platform] for [client or brand]. Their audience is [audience] and their tone is [tone]. The post is about [topic or photo description]. End with this call to action: [CTA]. Keep each under [number] characters. Don't add claims, prices or stats I didn't give you.

17. Two-week content plan

Plan [2 weeks] of [platform] posts for [client name] using these themes: [themes] and these key dates: [launches, holidays]. Give me a table with date, post idea, format and an opening line. If a date might clash with something, like a public holiday in [country], flag it for me to check.

18. Repurpose one piece of content

Turn this [blog post / video transcript] from [client name] into [3] short [platform] posts. Use only points from the original and keep the client's own wording where you can. Flag any line you shortened in a way that might change the meaning.
[paste]

Documents and SOPs

An SOP is a standard operating procedure: written steps anyone could follow to do a task the same way. These turn your notes into documents without inventing missing steps.

19. Rough notes to SOP

Turn my rough notes below into a step-by-step SOP for [task] at [client's business]. Number the steps and add who does each one and which tool they use. Where my notes skip a step or aren't clear, add a [QUESTION: ...] line instead of filling the gap.
[paste notes]

20. Reusable template

Create a reusable template for [document type, e.g. onboarding checklist / meeting agenda / invoice reminder] for [client name]. Use [square brackets] for every detail that changes each time. Before you start, ask me which sections they usually include.

21. Proofread without rewriting

Proofread this [document] for spelling, grammar and consistency (names, dates, formatting). Don't change the style. Give me a list of each change with the original and the fix. If something looks factually wrong, flag it instead of changing it.
[paste]

Data Cleanup

Spreadsheet work is where a quiet AI guess can do the most damage. These keep blanks blank and leave the numbers alone.

22. Clean up a list

Below is a list of [contacts / products] from a spreadsheet. Fix capitalisation, split full names into first and last name, format phone numbers as [format] and remove exact duplicates. Don't invent missing data: leave blanks blank. At the end, list any rows you weren't sure about.
[paste]

23. Explain a formula

I'm working in [Google Sheets / Excel]. Column [A] has [what], column [B] has [what]. I want to [goal]. Give me the formula, explain in plain words what it does, and tell me what could break it, like empty cells or mixed date formats. Ask me for a sample row if you need one.

24. Spot problems, change nothing

Here is [client name]'s [expense list / invoice tracker]: [paste]. Point out possible problems: duplicates, missing dates, amounts that look unusual next to the rest, and totals that don't add up. Give the row for each one. Don't change any numbers.

Travel

Prices, visas and entry rules change, so these prompts make the AI organise and point you to official sources instead of quoting rules from memory.

25. Build the itinerary

[Client name] is travelling to [city] from [date] to [date] for [purpose]. Using the bookings I paste below, build a day-by-day itinerary with local times, confirmation numbers, addresses and travel time between stops. Flag any tight connection or anything missing, like a night with no hotel.
[paste bookings]

26. Shortlist options

Suggest [3] [hotels / areas to stay / flight routes] in [city] for [client name], who prefers [preferences] and has a budget of about [budget] per [night / trip]. Tell me what to search for and what to check. Don't state prices or availability as fact, because those change. I'll confirm on the booking site.

27. Pre-trip checklist

Make a pre-trip checklist for [client name]'s trip to [country] on [dates]: documents, apps, chargers, business etiquette and things to confirm 48 hours before. For anything about visas or entry rules, write "check the official government site" instead of giving rules from memory.

Managing Yourself

The last three are for you. Juggling several clients is a job in itself, and these help with the planning around the work.

28. Plan my day

Here is my task list for today across [number] clients: [paste]. I have [hours] hours and these fixed calls: [times]. Put the tasks in order with time blocks, deadlines first. If something won't fit, tell me what you'd move and ask me which client is safest to push.

29. End-of-day log

Turn these quick notes into a tidy end-of-day log for [client name]: what I finished, what's in progress, what's blocking me, and what's first tomorrow. Use only what I wrote.
[paste notes]

30. A personal assistant prompt for Claude

You're my assistant for [client name], a [role] at [company]. They prefer [tone] and [preferences, e.g. short emails, no meetings before 10 am, time zone]. When I give you a task: ask up to 3 questions if anything is unclear, never invent facts, dates, prices or names, mark anything you're unsure about with [CHECK], and never say something has been sent or booked. I do that part.

That last one works best as standing instructions. In Claude, you can save it as the instructions for a Project, which is a separate workspace with its own chats and files, so every chat inside it starts with your client's details already loaded. Free accounts can create up to five Projects.


What This Means for VAs

Prompts don't replace your judgment. They give it a head start. A good prompt gets you a draft in under a minute, and the [CHECK] marks show you exactly where your own knowledge of the client has to come in.

If you have a client who sends you a pile of meeting transcripts every week, start with prompt 7 and prompt 8 together. If inbox work eats your mornings, start with 1 and 2.

Then change the wording until it sounds like you and your client. The ones you end up using daily won't look exactly like mine, and that's how it should be.

Try one today, then tell me which prompt you started with.

27.10.26

Will AI Replace Virtual Assistants? What the 2026 Data Shows


Will AI replace virtual assistants? From everything I've read this year, no, but it is replacing the easy parts of the job. The 2026 numbers show simple, repeatable tasks getting cheaper while AI-heavy work pays more, and that second group is where a VA can stand.

I'm a VA for an AI YouTuber, so I work with these tools every day. Here's what other VAs are saying, what the data shows, and what I'd do about it.

The Post 3,549 People Upvoted

In September, a post on Reddit's r/buhaydigital, a big Filipino remote-work community, was titled "My boss thought AI could replace my role." It got 3,549 upvotes and 149 comments.

The original story has since been deleted, but the replies are still there. One of the top replies, with 400 upvotes, came from someone who had been through it:

"Happened to me too. I resigned because of the so-called operations manager, then the CEO hired me back after a month. This time, I asked for a retainer with a minimum commitment, so they just renew it."

Another reply (129 upvotes) put the human edge in one line: "until AI can pay taxes, can be jailed, or can be blamed, professionally, it cant replace people."

That's accountability. Somebody still has to own the result, and a chatbot can't.

Not Every Story Ends Well

I won't sugarcoat this part. In October, a post on r/phcareers titled "im an advocate of AI until it caused me to be layed out" got 624 upvotes. The top reply (349 upvotes) said: "you probably got laid off for the company to hire a cheaper resource."

Look at what that reply is about: cost. In a lot of these stories, AI is the excuse and the budget is the reason.

Another r/phcareers thread, "AI ruined my work ethic, I might get fired eventually." (608 upvotes), was about the opposite problem: leaning on AI so hard that your own thinking gets rusty. The top reply (446 upvotes) was blunt: "Practice thinking and writing. For the next 2-3 YEARS. Yes, years."

A reply with 127 upvotes shared a habit I like: "I ensure I create the first draft and then use AI to refine wording, sentence structure, or formatting."

Will AI Replace Virtual Assistants? The Numbers

Reddit tells you how people feel. Here's what the bigger numbers say.

Upwork, one of the biggest freelance marketplaces, reported in August that the total amount clients spent on its platform fell 4% year over year in Q2 2026. In the same report, spending on AI-related work grew more than 22%.


Its CEO, Hayden Brown, said that "lower-complexity work continues to shift toward automation," while demand grows for "high-value AI talent, more complex projects, and new categories of work."

Upwork's Future Workforce Index 2026 adds detail. Freelancers doing AI work on its marketplace earn 34% more per hour than those not using AI in their work. And freelancers doing more complex work with AI saw their earnings rise 45% in Q1 2026.

There's a catch, though. In one category, "Generative AI and creative production," new contracts grew 90% while earnings per contract fell 13%. When anyone can do a task with one prompt, the price of that task drops.

What about official job numbers? The US Bureau of Labor Statistics projected "little or no change" (0%) in jobs for secretaries and administrative assistants from 2024 to 2034. Its newest update, for 2025 to 2035, shows a 2% decline, with about 314,400 openings a year.


That covers office admin jobs in the US, not remote VAs, but it's the closest official number we have. It's a slow shift, not a wipeout.

Why So Many Answers Feel Off

If you Google this question right now, one of the top results was written in 2016. That's six years before ChatGPT came out.

A lot of the fear you read, and a lot of the hype, is old or written by people who don't do this work.

What This Means for VAs

My honest view: AI is changing the work. It isn't ending it.

Tasks you can describe in one sentence, like "write a caption" or "summarize this email," are getting cheaper. The work that pays is everything around them: picking the right tool, catching what the AI got wrong, and owning the result for your client.

That's my day. AI helps me research and draft, and I check the facts and catch mistakes before anything goes out.

If you're worried, try three things this month. Learn one AI tool properly instead of ten badly. Write your own first draft before you ask AI to polish it, so your thinking stays sharp. And if a client starts talking about replacing you, remember that 400-upvote reply: offer a retainer with a minimum commitment, so you're something they renew, not something they cancel.

Want to see what AI-assisted VA work looks like up close? Read how I made a full YouTube video with Claude.

26.10.26

Gmail AI Inbox: The Catch for VAs Managing Client Inboxes


Gmail AI Inbox is rolling out to paid Google Workspace accounts, and it turns a busy inbox into a to-do list. The catch for VAs: Google's help page says it doesn't support delegated inboxes, which is how a lot of us get into a client's email.

So here's what it does, who actually gets it, and how to make it useful for your client anyway.

What Gmail AI Inbox Does

Google announced the Workspace rollout on October 15, 2026. AI Inbox is a separate view in Gmail with two sections.

"Suggested to-dos" pulls action items, deliverables and deadlines out of email threads. Think "send the signed contract by Friday," lifted out of a long reply chain. "Topics to catch up on" gives short summaries of your most important threads, so you can see the latest decisions without reading 14 messages.

It's part of Gemini, Google's AI, so it's built into Gmail itself. Your client doesn't install anything.


Who Gets It (Read This Before You Promise Anything)

This is where I'd slow down before telling a client "you have this now."

It's only for users in the US with English (US) as their language. Google's list names Business and Enterprise (Starter, Standard and Plus), Frontline Plus and AI Pro for Education, but the same post says Starter and Education editions get it later, "in the coming months." So for now, count on Standard and Plus. Personal Google accounts need a Google AI Plus, Pro or Ultra plan.

There's no admin switch for it. It rolls out over up to 15 days: Rapid Release domains started October 12, and Scheduled Release domains start October 26. If your client's account is on Scheduled Release, it may show up any day in the next two weeks.


The Fine Print for VAs

Google's help page lists a few limits that matter if you manage someone else's email.

It reads only the Primary tab, not Social or Promotions. It skips anything archived, deleted, muted or snoozed. And it "does not support attachments, delegated inboxes, or encrypted emails." Delegated access is when your client lets you open their Gmail from your own account. If that's your setup, AI Inbox won't help you there.

It also needs Gmail's smart features turned on, and Google says your first to-dos can take up to 7 days to appear.

One more: the "Mark all as read" button in AI Inbox also marks those emails as read in the regular inbox. If your client relies on bold unread emails as their reminder system, don't click it on their behalf.

Gmail Live: The Voice Version

Google rolled out a second feature the same day, Gmail Live. On the Gmail phone app, you tap Live in the search bar and ask your inbox a question out loud, like "when is my next mandatory training due?" It answers by voice and shows a card with the source email every time, so you can check where the answer came from.

Same rule: US users with English (US) only. It's on by default for organizations with Gemini, across Business Starter, Standard and Plus, Enterprise plans, and Google's consumer AI Plus, Pro and Ultra plans.

What This Means for VAs

If your client is in the US on an eligible plan, their inbox is about to start writing its own to-do list. That's good news for you, not bad news.

Here's how I'd use it. Ask your client to open AI Inbox once a day and forward you anything in "Suggested to-dos" they want handled. You turn their list into action: the reply, the calendar block, the follow-up. Their AI spots the task, and you get it done.

If you work through delegated access, keep your own triage routine. AI Inbox won't see what you see, so your morning sort is still the one your client can trust.

And if your client is outside the US, or on Business Starter, you have time. Learn how it works now so you're the one explaining it when it arrives.

Want more updates like this one, translated for VAs? 

25.10.26

Claude Duet Is a Robot Assistant: Where VAs Still Win


Claude Duet is Anthropic's new app that works like a robot assistant: it briefs you every morning, keeps an eye on your inbox and calendar, and asks before it sends anything. If you're a VA, that reads a lot like your job description. It doesn't replace you, and below I'll show you exactly where you still win.

Quick note first: I haven't used Claude Duet. Almost nobody has yet, because it's a research preview with a waitlist. So this is an explainer built from Anthropic's own pages, not a review.

What Claude Duet Actually Is

Anthropic opened Claude Duet on October 21, 2026, as a research preview. That means an early version they're still testing with real users.

It's a separate app for iPhone and Android, and you can also open it on claude.ai. Anthropic calls it "a proactive agent." An agent is an AI that can take actions on its own, not just answer questions. Proactive means it comes to you first instead of waiting for you to type.

Who can get it right now: Claude Pro and Max subscribers in the US, through a waitlist. The FAQ says Team and Enterprise plans are "not included yet."


What It Does All Day

Each morning it sends a short brief on the most important things across your connected apps. After that, it checks those apps every few hours and messages you only when something needs you. Anthropic says it doesn't check nonstop because that would use up your plan's limits much faster.

You can also hand it tasks by text or voice, all in one ongoing thread. The announcement gives examples like finding Gmail and Slack messages you missed, checking QuickBooks or Stripe for unpaid invoices and drafting reminders, preparing payroll in Gusto, and drafting follow-ups from HubSpot. It works on its own computer in the cloud, so your laptop doesn't have to be on.

One early user, Lydia Hallie, whose X bio says she works on Claude Code at Anthropic, posted that she has it "watch Slack/email/cal and only ping me when it matters." She works at the company that makes it, so read that as an insider's setup. The post still got 1,049 likes.

The Rules It Can't Break

This is the part I'd read twice if I were a client.

Before Claude Duet sends a message, makes a payment, signs a document, or deletes anything, it shows you exactly what it's about to do and waits for your OK. Some things are off-limits even if you say yes, like trading securities or moving money between accounts.


Anthropic's safety post, published two days later, adds that it never sees your passwords. When a site asks for one, you type it into a form inside the app, and it goes to Duet's cloud browser without passing through the AI.

Where a VA Still Wins

Anthropic is upfront about the limits. Its own FAQ says Duet "may misread a thread or miscalibrate what's urgent," and it can miss something that arrives between check-ins. The announcement also says personal errands, like booking tickets, "aren't quite as strong" yet.

That's your gap. Knowing which email is actually urgent comes from months of context: which client panics, which "quick question" is really a fire, which Tuesday is already packed. A check every few hours doesn't have that.

And because Duet stops and asks before it sends, pays, signs or deletes, someone has to look at each request and say yes or no. For a busy founder, that someone could be you.

What This Means for VAs

Anthropic says it built Claude Duet for "professionals and small business owners with more on their plates than they can track." That's exactly who most of us work for. So expect a client to ask, "Do I still need you if I have this?"

Here's how I'd answer. A tool like this flags and drafts. You decide, follow up, and fix what it misreads. If your client gets access, offer to set it up with them: connect only the apps it needs, tell it what counts as urgent for this business, and review its morning brief together for the first two weeks.

That's a new service on your menu, not a lost job. If you're in the US on Pro or Max, you can join the waitlist on the Claude Duet product page and learn it before your clients do.

If a client has already asked you about tools like this, tell me what they said on the comments below.

24.10.26

1Password for Agents: AI Logs In, Never Sees Client Passwords


1Password for Agents lets an AI agent log in to a website for you without ever seeing the password. The agent asks, you approve in 1Password, and 1Password types the login straight into the site.

If you've ever been tempted to paste a client's password into an AI chat so it can "just finish the task," this is the safer way. Here's how it works, who can use it today, and what I'd tell a client.

The Problem It Solves

An agent is an AI that does tasks on its own, like filling in a form or checking an order status, instead of only answering questions. Agents are getting good at this. But the moment one hits a login page, it stops.

1Password's announcement on October 22, 2026, describes the two bad options you have today. You take over and type the password in yourself every time, which is slow. Or you paste the password into the prompt, which gives the agent your login "potentially beyond the task at hand."

The post also points out that agents can't use passwords saved in your browser or written in notes. So without something like this, you keep getting pulled back in.


How 1Password for Agents Works

When the agent reaches a login, it asks for the credential it needs. You get the request in 1Password, check which login it wants, and approve it. Then 1Password fills in the username and password directly on the site. The agent never gets the password or the one-time code.

In 1Password's own example with Muse, you pick which login the agent can use, and it doesn't get anything else in your vault. You can also disconnect the integration at any time.

There's a nice side effect for anyone who changes passwords often. Your logins stay in one vault, so when a password changes, you update it once and every connected agent uses the new one.

Which AI Agents Work With It

Not all at once, and this is where I'd be careful with clients.

Two integrations are "rolling out over the coming days": Muse from Meta, and Grok Bot from SpaceXSI. Anthropic's Claude Duet, OpenAI's ChatGPT Work and dots, and Townie from Town are "coming soon." A longer list, including Perplexity, Browserbase, Browser Use and Ramp, is also marked "coming soon."

1Password adds that "the safeguards and controls vary by integration." So check each agent's own setup before you rely on it.

Is It Free?

For many people, yes. 1Password says it's available "at no additional cost" for Individual and Family accounts on 1Password.com.

Two limits. Accounts on 1Password.eu or 1Password.ca aren't currently supported. And the post only mentions Individual and Family accounts, so don't promise it to a client whose team uses a 1Password Business account.


What This Means for VAs

More clients are going to want an AI agent set up for them. Logins are the scary part of that job, and now there's a clear rule you can offer: the agent asks, a human approves, and nobody pastes a password anywhere.

Here's how I'd put it in practice. Write one line into your client SOP (standard operating procedure, your written how-we-do-things doc): "AI agents get logins through 1Password approval only, never a pasted password." Then list which agent the client uses and whether it's live yet or still "coming soon."

If your client is waiting on Claude Duet or ChatGPT Work, you have time to tidy their vault first. Remove old logins and name items clearly, so the right one is easy to spot when an approval request comes in.

You become the person who makes the AI safe to use. That's a skill clients will pay for.

If you're setting up agents for clients, tell me which one they picked.

Can Claude Make YouTube Videos? I Made a 4-Minute One



Yes, it can. This week I made a full 4-minute YouTube video with Claude: the research, the script, the voice, every scene, and the thumbnail. But it didn't happen the way most people imagine, and the part that surprised me most wasn't the video at all.

Here's exactly what Claude did, what I did, and what I'd tell any VA who wants to try it.

First, What "Making a Video" Meant Here

Claude didn't press a magic "make video" button. There's no camera and no AI-generated footage in this video.

I used Claude Code, the version of Claude that can run tools on your computer, not just chat. It wrote the video as a set of animated web pages, then recorded them frame by frame into an MP4. Think of it like building slides that move, then filming them.

The video is for my small test channel, The 1% Mindset. The topic: a new AI model that guesses an answer 93% of the time when it doesn't know.


How It Went, Step by Step

Research. I asked Claude to dig into the topic. It sent several research helpers out at once, then a separate set of fact-checkers who opened every source again. They checked 194 claims. Four were wrong, and none of those made it into the script.

Script. Claude wrote a 4-minute script in plain English, then checked its own opening against a retention checklist and rewrote the first lines. I read it and signed it off before anything else happened. That's the same job I'd do for a human writer.

Voice. The voice-over comes from Kokoro, a free voice model that runs on my laptop. Claude split the script into sections, voiced each one, then transcribed the audio back to check that every word came out right.

Visuals. Every chart and post you see is a real screenshot of the source. Claude added the red hand-drawn circles and underlines, timed to the voice. The only made-up art is the cartoon test sheets and bunny from the thumbnail, plus a few simple bar graphics.


Thumbnail. Claude wrote the prompt for Nano Banana 2 (Google's image model), then added the "100% SURE" text on top.


The final file: 4 minutes 12 seconds, full HD.

What Surprised Me

The checking. After the render, Claude pulled a frame from every 2 seconds of the video and looked at all of them, like a very patient editor.

It caught real mistakes. One red circle sat on the wrong bar of a chart, because the website had shifted its layout after the screenshot. Another section sat empty for 8 seconds. Both got fixed before I ever saw the video.


On a second video, it caught something worse: a screenshot that showed numbers we hadn't been able to verify. It cropped them out. As someone whose job is getting details right for a client, that's the part that won me over.

Is It Free?

Not completely. Claude Code needs a paid Claude plan. The voice model is free, and the thumbnail image costs a little through Google.

Time is the bigger cost. This took most of a day, with me reviewing at every step. It's still a fraction of what one person would need to research, write, voice, animate, and edit the same video by hand.

What This Means for VAs

If you manage YouTube for a client, this changes what you can offer. You don't need to be a video editor to turn a script and real sources into a clean explainer, a Short, or a slide-style video.

But notice who made the decisions. Claude did the heavy lifting, while I picked the topic, approved the script, chose the look, and said no when something felt off. That's still VA work. It's just a bigger version of it.

Start small. Ask Claude to turn one of your client's blog posts into a 30-second Short script, and see how much of the rest you'd want to hand over.

If you try it, tell me how it goes on the comments.

22.9.26

Putting Jev to work: a router that decides where your prompt goes

 The first two Jev videos were about what the thing is. This one builds something with it — a model router you run on your own machine.

The setup is a Next.js UI talking to a local FastAPI server. Every prompt goes to Jev first, and one call asks three questions at once against the same state:

  • choice — what kind of task is this? Chit-chat, simple question, rewrite, code, reasoning, image.
  • score — how much model capability does a good answer actually need? Trivial ("a 2B model handles this") through to frontier.
  • noul — does this contain personal, client, financial, medical or credential data?

Because all three evaluate in parallel, asking three costs about the same time as asking one. What comes back is just numbers, so the routing is ordinary if/else. Chit-chat goes to MiniCPM5 2B running locally. Code goes out to DeepSeek V4.1 Flash on OpenRouter. An image request goes to Qwen Image 2.1, also local. Privacy above 0.5 and the whole thing stays on the machine regardless of everything else. Hard work escalates a tier — Opus 5 if it's switched on. And when confidence comes back low, the router doesn't guess, it falls back to a safe default.

The numbers are the interesting part. A "how's it going?" prompt was judged in 331ms, difficulty zero, routed local. Drop in a fake API key and privacy comes back at 0.96 and it never leaves the machine. Over a session of 53 requests, 75% were answered locally — and a full run of demos cost under one cent.

There's an honest flaw he flags before building: if you send the prompt to TypeSafe to ask whether it's private, you've already leaked it. So the second half swaps Jev out for SemIf running locally. Same decisions, same shape, 88ms, nothing leaves the box.

That's the real takeaway. Once the decision layer costs almost nothing and answers in under 100ms, you can rethink how agentic systems are structured — put a fast gate in front of everything and only spend real money when the gate says you have to.

  • SemIf — https://github.com/TheoLeeCJ/SemIf
  • Bespoke Nimble 9B — https://huggingface.co/bespokelabs/Bespoke-Nimble-9B
  • Decider — https://github.com/Mapika/decider
  • Alex Wortega's OpenJev — https://huggingface.co/AlexWortega/openjev
  • DiffusionGemma (vLLM PR) — https://github.com/vllm-project/vllm/pull/57250
  • NanoJev — https://github.com/TianyuCodings/NanoJev
  • Layla — https://github.com/NandhaKishorM/laya
  • Jev, and the week everyone cloned it

     For two years every frontier lab has been pushing in the same direction: reasoning. Longer chains of thought, bigger thinking budgets, models that will happily sit there for minutes before answering — and won't show you the chain of thought you paid for.

    That's System 2 thinking, in Kahneman's terms. Slow, deliberate, effortful. But most decisions that actually sit inside software aren't System 2 problems. What kind of support ticket is this? Is this urgent? Did the agent's output break a rule? Those are gut calls. You shouldn't need 30 seconds for them, let alone two minutes.

    A lab called TypeSafe AI just came out of stealth going the opposite way, with System One models and a model called Jev. You can't chat with it at all. It doesn't generate text. The founder, Diogo Almeida, was a lead author on the InstructGPT paper that made models good at talking to people, and his argument now is that chat is the wrong interface for software. Software doesn't want a paragraph. It wants a value it can use.

    So you pass in a state — a ticket, a log, an agent trace — plus typed questions. Only three kinds: choice (pick one of these options), score (rate on my scale), and noul (yes/no, with a probability). What comes back is typed answers with real probabilities, in 70–500ms. Output tokens are free; input is four cents per million. Think of it as an if statement that understands language.

    The honest caveats: there's no paper and no architecture diagram — just three hints (new architecture, parallel sampler, and RLCD, reinforcement learning for calibrated decisions). "Can't hallucinate" really means it can't break your schema. It can still be wrong.

    Then the interesting part. Within 24 hours of that video, open replications started appearing — now 20 to 30 of them, and some are close. On JevBench, Jev scores 75.3 and SemIf — a frozen Qwen 3.5 4B with no training at all — sits right behind it. Everyone converged on the same trick: read the logits over the answer tokens and softmax, no sampling.

    The gap is still real on hard, multi-hop work. The move there is a cascade — fast model first, escalate only when confidence drops.

    When a client thinks AI makes everything instant, you fix it with one short conversation about scope, time, checking and price, before the ...