Wandering Nomad

How to Become an AI Virtual Assistant: Skills That Pay

noreply@blogger.com (Unknown) — Fri, 30 Oct 2026 11:27:00 +0000

Here's how to become an AI virtual assistant: learn to do real client tasks with AI, then prove you can check what it gives you. You don't need to code. You need a handful of skills, and the 2026 data says clients are already paying more for them.

I use these skills every day as the VA for an AI YouTuber. Below is the roadmap I'd follow if I were starting today.

Why AI Skills Pay Right Now

Upwork's Future Workforce Index 2026 found that freelancers doing AI work on its marketplace earn 34% more per hour than those not using AI in their work.

In its Q2 2026 results, Upwork said spending on AI-related work grew more than 22% year over year, even while total spending on the platform fell 4%.

The Future Workforce Index even has a section called "AI orchestrator." That's a fancy name for a person who directs AI tools to get a job done. A good VA already directs people, calendars and inboxes. This is the same muscle.

The AI Skills for Virtual Assistants I Use Daily

1. Research with AI, then fact-check it. AI is fast at finding sources. It's also confident when it's wrong. My rule: every number and date goes back to the original page before it goes into my client's work. That checking step is the part clients can't skip, and it's the part they pay for.

2. Drafting and scripting with AI. AI writes my first drafts of video scripts. I read every line and sign it off before anything else happens, the same job I'd do for a human writer. Knowing what your client would never say is a skill AI doesn't have.

3. Building small things with Claude Code. Claude Code is a version of Claude that can run tools on your computer, not just chat. I've used it to research, write and render a whole YouTube video. You don't start there. Start by asking it to rename and sort a messy folder.

4. Picking the right tool for the job. Some tasks need a chatbot, some need an automation, and some need a human. Knowing the difference saves your client money.

AI Automation Virtual Assistant Jobs

Automation means connecting apps so a task runs by itself. Say a new form entry automatically lands in a spreadsheet and sends a welcome email. That's the work behind most "AI automation virtual assistant jobs."

Demand is real. In Upwork's In-Demand Skills 2026 report, AI integration (connecting AI to the tools a business already uses) grew 178% year over year, and AI video generation and editing grew 329%.

VAs are hungry to learn this too. A Filipino YouTube video, Kuys RJ's "10 AI Automation Projects That WILL Get You Clients," got about 31,000 views, around 5.4 times what his videos usually get.

My advice: build one small automation for yourself first. Then show it to a client as a before-and-after.

Pick a Growing Niche

Upwork's same report lists the fastest-growing skills in customer service and admin support: Ecommerce Management (+130%), Medical Virtual Assistance (+44%) and Supply Chain and Logistics Project Management (+37%). General virtual assistance is still the most in-demand skill in that category.

So you don't need to stop being a VA. Add AI to a niche that's already growing.

Make Your Profile Easy for AI to Read

On August 10, Upwork launched an MCP server. MCP is a standard that lets AI tools like Claude and ChatGPT connect to other services. With it, a client's AI agent (an AI that can take actions, not just answer questions) can post a job, surface talent and summarize proposals as they arrive.

That means an AI might read your proposal before your client does. Write it plainly. Name the tools you use and the results you got, in the first lines.

Freelancers can use it too. Upwork says your own agent can flag best-fit jobs and draft a tailored proposal. Just read every draft before you send it.

How to Become an AI Virtual Assistant in 3 Months

Here's the roadmap, one month at a time.

Month one: learn one AI assistant well, Claude or ChatGPT, and use it on your real tasks. Month two: practice research and fact-checking until checking is a habit. Month three: build one automation and one small project you can show.

What This Means for VAs

Skilled freelancing is growing. Upwork says it rose from 28% of US skilled knowledge workers in 2025 to 38% in 2026. More people are competing, and AI skills are how you stand out.

Keep a simple portfolio of before-and-afters as you go. Clients don't hire "knows AI." They hire "saved me hours every week."

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

noreply@blogger.com (Unknown) — Thu, 29 Oct 2026 11:26:00 +0000

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.

30 Free Virtual Assistant Prompts for ChatGPT and Claude

noreply@blogger.com (Unknown) — Wed, 28 Oct 2026 11:22:00 +0000

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.

Will AI Replace Virtual Assistants? What the 2026 Data Shows

noreply@blogger.com (Unknown) — Tue, 27 Oct 2026 11:21:00 +0000

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.

Gmail AI Inbox: The Catch for VAs Managing Client Inboxes

noreply@blogger.com (Unknown) — Mon, 26 Oct 2026 11:19:00 +0000

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?

Claude Duet Is a Robot Assistant: Where VAs Still Win

noreply@blogger.com (Unknown) — Sun, 25 Oct 2026 12:00:00 +0000

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.

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

noreply@blogger.com (Unknown) — Sat, 24 Oct 2026 11:24:21 +0000

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

noreply@blogger.com (Unknown) — Sat, 24 Oct 2026 10:33:15 +0000

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.

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

noreply@blogger.com (Unknown) — Tue, 22 Sep 2026 08:29:43 +0000

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

noreply@blogger.com (Unknown) — Tue, 22 Sep 2026 08:27:51 +0000

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.

How to Cut Your Fable Bill by 50–90% (Lessons From Someone Who Burned $1,486 in 4 Hours)

noreply@blogger.com (Unknown) — Sat, 04 Jul 2026 14:34:50 +0000

Fable is back, it's brilliant, and it will happily drain your wallet. One creator spent over $1,400 in the first four hours after release — deliberately — to stress-test which token-reduction strategies actually work. I went through the whole breakdown, and the good news is most of the savings come from a handful of simple habits. Here's what stuck with me.

The core insight running through all of it: token management is context management. Almost every dollar wasted goes to Claude reading things it didn't need to read.

1. Minify tool output (RTK)

Claude Code runs tool calls constantly — hundreds or thousands per session — and the raw output is full of repeated noise: stdout, stdout, stdout, fixture setup lines, boilerplate. A tool called RTK (Rust Token Killer) strips and reformats tool inputs/outputs down to what the model actually needs. In the demo, one tool call went from 612 lines (36,700 characters) to 4 lines (177 characters) — a 99% reduction on that call. Not every call is that bloated, but across a real session you can expect 30–50% savings with zero quality loss.

2. Semantically compress your CLAUDE.md

Most system prompts and memory files are padded with pleasantries that carry zero information. "Hello, thank you so much for helping out with this project, we really appreciate..." compresses to "Project instructions and guidelines." Same meaning, fraction of the tokens. The demo took a CLAUDE.md from 865 words to 211 — roughly 1,125 tokens down to 274. Run this pass on every project's system prompt and memory files. Bonus: tighter instructions often produce better output, not just cheaper output.

3. Never let Claude read logs raw

If Claude needs to dig through a 5,000-line log file, don't let it read the file. Load the log into SQLite and give Claude a small query script instead. It finds the root cause — with exact line numbers — by running a query rather than eating thousands of lines of text. The same principle applies to CSVs and Google Sheets: query, don't read.

4. Block huge reads generally

Some files are just too big to read start to finish, and most never needed to be. A good pattern: have Claude sample the beginning and end of a large file, infer the structure, then use sed, grep, or a search function to jump straight to the relevant region. Instead of 20,000 lines, it reads 20 or 30. On large-resource tool calls, that's ~99% saved.

5. Prompt in English

English is unusually information-dense per token. The same query cost 51 tokens in English, 87 in Italian, 118 in German, 74 in Japanese. (Mandarin is a notable exception — symbolic characters are token-efficient.) Most models are also trained predominantly on English, so you're not trading quality away. If you work in another language, this alone can be a 20–80% swing.

6. Add context frugality rules

Bake frugality directly into your CLAUDE.md: read only files directly relevant to the task, ask before expanding beyond three files, prefer glob/grep to locate then read the region, never read generated files or fixtures unless asked. One caveat — this is the only tactic on the list that can hurt quality, because you're constraining where the model looks. The trade: be more specific in your prompts, pay less.

7. Audit your context regularly

Run /context periodically. Things creep in silently — the creator discovered he was running a dozen Chrome MCP instances simultaneously, each loaded with full context, bloating every request and confusing the model. System prompt, tools, memory files, and skills can quietly eat 8%+ of your window before you've typed a word. A neat trick: set up a looping watcher instance that snapshots your context daily and flags anything new.

8. Cap your thinking

Adaptive thinking tends to overspend. In a head-to-head bug-hunt test, low thinking found the bug in 7 turns and 1,028 output tokens; extra-high found the same bug in 9 turns and 1,363 tokens — typically closer to 1.5x over repeated runs. With a model as capable as Fable, default to low thinking and opt into big budgets only when a task demonstrably needs them. That's a 30–40% saving on its own.

Agent Loops, Explained Simply (And Why They're Not Magic)

noreply@blogger.com (Unknown) — Sun, 21 Jun 2026 13:00:00 +0000

There's a lot of buzz online lately about "agent loops" and "loop engineering," with some people claiming you shouldn't even prompt your AI anymore — you should build systems that prompt it for you. A recent video does a nice job cutting through the hype and explaining what this actually means. Here's a plain-English version, plus an honest take on what's useful and where the hype gets ahead of reality.

What's an agent loop?

Strip away the jargon and a loop is simple. Instead of asking the AI to do something once and accepting whatever comes back, you let it repeat a cycle: reason (figure out what to do), act (do it), and observe (check the result). It keeps going — adjusting each time — until it hits a goal you've defined, then stops and tells you it's done.

The video compares it to a smart intern you don't micromanage. You hand them a goal and a clear definition of "finished," and they figure out the steps, check their own work, and only come back when it's actually done.

A loop really comes down to three things: a trigger (what starts it), an action (what it does), and a stop condition (how it knows to quit). And two pillars matter most — a clear goal and a way to verify progress.

Why this is genuinely useful

The big insight is that AI rarely nails something on the first try. Normally you would look at the output, give feedback, and ask for changes — over and over until it's good enough. A loop just hands that tedious back-and-forth to the AI itself, so it arrives much closer to "good" before it ever shows you the result.

In the video, the creator builds things this way: thumbnails scored against a rubric, a 3D plane that the AI repeatedly renders and inspects, even video edits where the AI cuts pauses and checks its own timing. The magic of "I did this in one prompt" is usually just a well-designed loop with verification baked in.

Where the hype gets ahead of reality

Here's the refreshing part of the video: most tasks don't need elaborate loops. You don't need five agents running 24/7 commanding other agents. The creator admits that for his own knowledge work, a single agent with a good prompt does the job most of the time, and that round-the-clock "swarms" mostly make sense for full-time coders building software.

The honest takeaways worth remembering:

Loops aren't meant to deliver 100% perfect output — they just get you much closer, faster. In the video, the AI's attempt to recreate a famous photo in code still came out looking nothing like the original.
A loop is only as good as its "done" check. Vague criteria like "until you're satisfied" lead to vague results; the best loops aim for something measurable.
Just because an expert online does it doesn't mean you should. AI shows up differently in every job — staying informed isn't the same as copying someone else's setup.

The part that stays human

Notice what you still own in all of this. You define the goal, and you decide how "done" gets verified. The video is blunt that AI is never perfect and a loop without a good verification check just produces polished-looking mistakes faster. Some runs even went 12 hours and weren't useful.

So the human role doesn't disappear — it moves up a level. Instead of correcting every draft, you're designing clear goals, sensible stop conditions, and real checks — and reviewing the final result before trusting it.

The bottom line

Agent loops are a genuinely smart idea: let the AI handle its own feedback-and-iterate cycle so you get better results sooner. But they're a tool, not a miracle. Start simple, define "done" clearly, and keep checking the work — because a loop will happily repeat a mistake until you tell it not to.

Anthropic Just Made Claude Agents Boring. That's the Whole Point.

noreply@blogger.com (Unknown) — Sun, 21 Jun 2026 09:13:06 +0000

The flashy AI announcements get the headlines — new model, higher benchmark, longer context. But if you've ever tried to actually deploy an agent inside a company with a security team, you know the model was never the hard part. The hard part is the question every CISO asks in the first meeting: how does this thing touch our systems without becoming the breach we read about next quarter?

On June 18, Anthropic answered the last open piece of that question. And the answer is delightfully unglamorous.

The news: identity finally caught up

Anthropic shipped Enterprise-Managed Authorization for Claude's MCP connectors. In plain terms: an admin provisions a connector once through the company's identity provider, and every employee inherits access automatically on first login. No individual OAuth consent screens. No "click allow" forty thousand times across the org. When someone leaves or changes roles, their connector access gets revoked alongside every other app — because it's governed by the same identity rules.

Okta is the first identity provider, using its Cross App Access plumbing. The connectors live at launch: Asana, Atlassian, Canva, Figma, Granola, Linear, and Supabase, with Slack rolling out. It's in beta, Team and Enterprise plans only.

If you've never run IT for a large org, this sounds like a footnote. If you have, you know it's the difference between "we piloted it with five people" and "it's live for the whole company."

The two pieces this builds on

Here's the context most of the recap posts are getting wrong: this isn't a standalone drop. It's the capstone on two features Anthropic shipped a month earlier, on May 19. Together the three are the actual enterprise story.

Self-hosted sandboxes (public beta) moved tool execution out of Anthropic's infrastructure and into an environment you control — your own infra, or a managed provider like Cloudflare, Daytona, Modal, or Vercel. The clever bit is the split: the agent loop that handles orchestration, context, and error recovery stays on Anthropic's side, but the code actually runs inside your perimeter. Your files don't leave. Your network policies and audit logging already apply. You set the compute.

MCP tunnels (research preview) solved the other half. Your agents can now reach MCP servers sitting inside your private network without exposing them to the public internet. A lightweight gateway you deploy makes a single outbound connection — no inbound firewall rules, no public endpoint, encrypted end to end. Your internal Postgres, your private APIs, your ticketing system become tools the agent can call, and none of them ever face the open web.

Why the trio matters

Line them up and you can see the strategy. The classic enterprise objection to AI agents has always been some version of "we can't let an external service into our internal systems." Anthropic just dismantled that objection at three different layers at once.

Tunnels mean no public endpoint and no VPN exceptions. Sandboxes mean code execution never leaves your walls. And enterprise-managed auth means access is provisioned and revoked through the identity system you already trust. Each one removes a specific veto that a security team can throw. Stack them and the "no" gets very hard to justify.

That's the real shift here. The bottleneck for enterprise AI was never reasoning quality. It was governance, and governance is exactly what this release is about.

The honest caveats

I'd be doing you a disservice if I made this sound finished. MCP tunnels is still a research preview — you request access, it's not broadly available. Self-hosted sandboxes is public beta, which means it's real but you should expect rough edges. And the enterprise-managed auth is beta, Team and Enterprise only, with Okta as the sole identity provider for now. If your stack runs on a different IdP, you're waiting.

So this is a direction, not a finished product. But it's the right direction, and it's further along than anything comparable from the other labs.

The takeaway

This release won't trend the way a new model does. There's no benchmark to screenshot. But if your job is getting agents past a security review and into production, this is the most important thing Anthropic has shipped this quarter. They made the deployment story boring — predictable, governable, auditable — and boring is precisely what enterprise buyers have been waiting for.

The model was always good enough. Now the plumbing is catching up.

Building an Affiliate Marketing Business with AI: An Honest, Friendly Look

noreply@blogger.com (Unknown) — Sat, 20 Jun 2026 13:00:00 +0000

There's a video making the rounds where someone claims to build an entire affiliate marketing business in about an hour — a website, Pinterest pins, an email system, even the emails themselves — using Claude plus an AI tool called GenSpark. It looks almost magical. So is it real, and should you try it?

Here's a plain-English take on what's genuinely great about the idea, what's harder than it looks, and the one habit you can't skip.

The idea in a nutshell

Affiliate marketing just means promoting someone else's product and earning a commission when people buy through your link. The video's plan is simple: pick a niche (say, kitchen gadgets), build a clean website with AI, add an email signup with a free guide, and create eye-catching Pinterest pins that send curious people to your site. AI does most of the heavy lifting — writing, designing, and even building the website from a single prompt.

What's genuinely good about it

The biggest win is speed. Things that used to take days — designing a website, writing emails, making pins in Canva — can now come back in minutes. For someone starting out with no budget for a designer or developer, that's a real head start.

It's also more approachable than ever. You describe what you want in normal language and watch the website build itself, with no code to touch. And the underlying strategy is sound: sending people to your own site and capturing emails (so you "own" your audience) is smarter than dropping raw affiliate links on social media and hoping.

Finally, it's easy to experiment. Once you've built one funnel, you can repeat it across niches and see what sticks.

What's harder than the video makes it sound

A polished website is the easy 10%. The hard 90% is getting actual people to visit — and that part the video mostly skips. Pinterest, traffic, and steady sales take time, consistency, and a bit of luck. Most affiliate sites earn little or nothing for a long while.

There are also rules you have to follow, not optional extras. Amazon and other programs require you to clearly disclose that your links are affiliate links, and they have strict terms you can get banned for breaking. AI won't handle that compliance for you.

And be skeptical of the "people are making money with this" framing. Real money is possible, but these videos rarely show the failures, the months of effort, or the fact that the easiest person to make money is often the one selling you the tools.

The rule you can't skip: check everything yourself

This is the part to underline. AI makes mistakes, and a human always needs to review the work before it goes live.

AI will confidently invent product details, quote wrong prices, recommend items that are out of stock, or write claims about a product that simply aren't true — and it sounds just as sure when it's wrong. In affiliate marketing, that's not just embarrassing; misleading claims can break platform rules or even consumer-protection laws.

So treat every output as a first draft. Before anything is published, verify each product, price, and link is real and current, read every email and pin for accuracy and honest claims, and make sure your affiliate disclosures are clearly visible. You are the editor and the one responsible for what your audience sees — not the AI.

The bottom line

The tools really can collapse hours of work into minutes, and that's exciting, especially if you're not technical. But building the site is the beginning, not the business. Go in with realistic expectations, follow the disclosure rules, and keep a human firmly in the loop. AI can do the building — you do the checking.

Can You Really Build a Whole AI Marketing Team? A Friendly Look at the Idea

noreply@blogger.com (Unknown) — Sat, 20 Jun 2026 04:18:23 +0000

There's a popular video going around that promises something pretty wild: turn Claude into a full marketing team — five "agents" and a dozen "skills" — all working together to research, write, design, and even build landing pages for you. And the best part of the pitch? "Even if you're not technical, let's go."

It's a genuinely exciting idea. But before you dive in, here's an honest, plain-English take on what's great about it, what's tricky, and the one rule you should never skip.

What's the big idea?

Think of it like hiring a small team that never sleeps. You give the AI some "skills" (reusable instructions for tasks you do all the time, like making a branded slide deck or writing a blog post) and a few "agents" (specialists, like a data analyst or a content writer). Then you hand it a job — "launch our summer campaign" — and it produces research, social posts, images, and a landing page, mostly on its own.

In the video, it works impressively well. The decks follow the brand template, the images match the style, and the whole package looks professional.

What's genuinely good about this

The most appealing part is the time saved. Tasks that used to eat a whole afternoon — drafting posts, pulling a report together, mocking up a deck — can come back in minutes. For a small business or a solo marketer, that's a real gift.

It's also more approachable than it used to be. You're mostly talking to the AI in normal language, not writing code. And the idea of building reusable "skills" is smart: you teach it your style once, and it remembers. That consistency is hard to get when you're rushing.

Finally, it lowers the barrier to trying things. Want three versions of a campaign to compare? You can have them quickly, then pick what actually works.

What's not so easy (especially if you're non-technical)

Here's the honest part. The video says "even if you're not technical," but the setup involves downloading VS Code, installing tools, connecting "MCPs," and editing configuration files. That's a fair bit more technical than the friendly framing suggests. None of it is impossible to learn, but expect a real learning curve, not a five-minute setup.

There's also a cost to maintaining all this. Skills and agents need updating as your brand and goals change. And the more you pile on, the more you have to keep organized.

The rule you should never skip: check everything

This is the most important point, so I'll say it plainly. AI makes mistakes, and a human always needs to check the work.

Even in the video, the creator admits the result is "90% done" and that some charts still need fixing. That last 10% matters enormously. AI can confidently state facts that are wrong, invent statistics, misquote a source, or get your pricing or product details subtly off. It won't always tell you when it's unsure — it often sounds just as confident when it's wrong as when it's right.

So treat every output as a first draft, never a finished product. Before anything goes public:

Fact-check the claims and numbers against a trusted source.
Read it for tone and accuracy — does it actually sound like your brand, and is everything true?
Double-check names, prices, links, and dates, which AI gets wrong surprisingly often.

You are the editor-in-chief. The AI is a fast, tireless assistant — not a replacement for your judgment.

The bottom line

Building an "AI marketing team" is a powerful idea, and the tools really can save you hours. If you're non-technical, go in knowing the setup is more involved than it looks, and start small with one or two simple skills.

Most of all, keep a human in the loop. AI can do the heavy lifting, but a person should always have the final read before anything reaches your audience.

I'm Stealing This AI Researcher's Workflow for My Own Projects

noreply@blogger.com (Unknown) — Sun, 05 Apr 2026 02:39:00 +0000

Karpathy doesn't use a fancy app to manage his research. He uses a folder, Obsidian, and an AI — and I want to copy it.

He posted about it last week. The short version: he dumps raw material — articles, notes, papers, images — into a folder, then lets a large language model (LLM — the AI brain behind tools like Claude or ChatGPT) build a wiki from it automatically. The LLM writes the summaries, creates the links between ideas, organizes everything into categories. He barely touches the wiki himself. When it gets big enough, he asks it questions and gets answers pulled from his own research.

I've been sitting with this for a few days, thinking about what it would look like for my work.

---

What My Work Actually Looks Like

I build things. Agents, content apps, Claude Code workflows, automation scripts. A lot of what I do involves figuring something out — what tool does what, how to wire two things together, what prompt pattern produces the right output, what broke last time and why.

Most of that knowledge lives in my head, or in scattered notes, or in past conversations I can't find anymore.

That's the problem. Every time I start something new, I spend time re-learning things I already know. What flags to use in Claude Code. What agent structure works for what kind of task. What API response format caused everything to break last month.

Karpathy's idea is simple: stop keeping that knowledge in your head. Dump it in a folder. Let the AI organize it. Ask it back when you need it.

—

The Specific Thing I Keep Thinking About

He mentioned that his wiki grows and gets more useful with every question he asks. He asks something, the AI goes through his notes and answers it — and then he saves that answer back into the wiki. So every session adds something. Nothing gets lost.

That hit me because the opposite is true for how I work right now. Every build session ends and most of the small things I figured out just disappear. The next session starts almost from scratch on some of the same ground.

If I had a knowledge base for my Claude Code workflows alone — prompts that worked, structures that didn't, patterns I figured out, error fixes — and an AI that could surface the right piece when I needed it, I'd stop repeating myself.

—

The Part That Actually Excited Me

He also runs "health checks" on his wiki. He asks the AI to find gaps, spot inconsistencies, and find connections between ideas he hadn't noticed yet. The AI suggests new things to look into.

That's the part I can't stop thinking about.

Not just a system that stores what I know. A system that notices what's missing. For someone building content automation apps, that means the system isn't just remembering what tools I've used — it's noticing when two things I built separately could be connected. It's pointing to the next piece.

That changes how building feels. Less like starting from zero every time, more like picking up a thread.

—

What I'm Going to Test

I'm starting with one folder. My Claude Code workflows — the scripts, prompts, notes, fixes, things that broke and how I solved them.

I'll ask Claude to read through everything and build an index: summaries of each file, links between related ideas, a map of what I already know.

From there, I'll ask it questions mid-project. "What pattern did I use last time for a multi-step agent?" "What was the issue I kept hitting with streaming output?" Instead of digging through old files or trying to remember, I just ask.

I'm not building the full Karpathy setup yet. I'm testing whether the core idea holds: does having a searchable, AI-organized version of my own work actually save time and reduce the re-learning?

I Told an AI to Build a Full Newsletter. One Sentence. No Code.

noreply@blogger.com (Unknown) — Sat, 14 Mar 2026 09:12:00 +0000

I used to spend half a day on client newsletters. Last week I did it in 15 minutes — and I'll show you exactly what I typed.

🤖 What Claude Code Actually Is

Claude Code is an extension you install inside VS Code — a free code editor. Once it's set up, you have an AI agent sitting inside your project that can read files, write code, call APIs, fix its own errors, and run automations — all through a chat window.

You talk to it. It builds things. That's the whole loop. You don't need to know how to code. You need to know what you want.

🧪 What I Actually Tested

I set up a project, gave the agent a brand logo and a color guide, connected a few API keys (one for research, one for Gmail), and typed one prompt. That was it.

What came back:

Research pulled from live sources
Three branded infographics generated with AI images
Full HTML newsletter formatted to the brand's colors and fonts
Email sent directly to a list via Gmail
Sources linked at the bottom, clickable

It hit errors along the way. An API endpoint had changed. A Gmail formatting issue broke the layout. Both times, it found the problem, explained what happened, fixed the tool, and kept running. I didn't touch anything.

🏗️ How the Whole Thing Is Organized

The system behind this is called

Component	What It Is
Pipeline	The instructions, written in plain English — like a step-by-step recipe
Tools	The specific actions the agent can take (research, generate image, send email)
Orchestrator	Claude Code itself, reading the pipeline and running each tool in order

You also give it a file called CLAUDE.md — a standing brief that tells the agent what the project is, where things live, and what it's supposed to do. Every time you open the project, it reads that first.

Once you've built and tested a pipeline, you can schedule it to run on its own — every Monday morning, every time a form is submitted, whatever you need. At that point the agent isn't running live. The code it built is. It runs predictably, like any other automation.

💼 What This Means for VAs and Small Business Owners

You don't need to learn to code. You need to be able to describe a process clearly.

If you manage newsletters, reports, client updates, or social content for clients — build a pipeline, test it once, let it run. If you spend hours every week on the same repetitive tasks in your own business, same idea.

What makes this different from something like Zapier is what happens during the build. The agent adapts. It hits an error, investigates, fixes the tool, and updates the instructions so the same thing doesn't break again. The final automation is more reliable — and you got there faster than mapping every node by hand.

💰 If You're Thinking About Offering This as a Service

Businesses aren't paying for a pipeline or a blueprint. They're paying for a solved problem.

Don't open with "do you want AI automation?" Ask: where are you losing the most time or money right now? Find that, build the thing that fixes it, and price it on what it's worth — hours saved, errors cut, costs gone — not on how long you spent building it.

A pipeline that saves a client 20 hours a week isn't a half-day job. Over a year, that's tens of thousands of dollars in time they're not paying someone else to cover. Price it that way.

🚀 Where to Start


Tool	Claude Code — runs inside VS Code (free to download)
Cost	Paid Claude subscription — $17/month on the Pro plan
Setup time	~1 hour, most of it connecting API keys

Pick one task you do every single week. Something repetitive, something predictable. Let the agent build the first version, watch it run, fix what doesn't land, and build from there.

The hardest part isn't the tool. It's deciding what to automate first.

This Paper Says We've Been Fine-Tuning the Hard Way

noreply@blogger.com (Unknown) — Sat, 14 Mar 2026 08:49:00 +0000

I was reading a paper that dropped in March 2026 and about three paragraphs in, I had to stop. The claim seemed too simple: you can adapt a large AI model to a specific task without gradient descent at all. Just random sampling and a vote.

What Fine-Tuning Actually Is

When an AI model gets trained, it learns general patterns from a massive dataset. Fine-tuning is the step where you take that general model and push it toward a specific task — coding, reasoning, following instructions — using reinforcement learning or optimization algorithms.

Methods like PPO and GRPO (types of reinforcement learning commonly used to fine-tune large language models) work well. But they're expensive, require careful setup, and involve a lot of iteration.

The Paper's Core Claim

Title: Neural Thickets: Diverse Task Experts Are Dense Around Pretrained Weights Authors: Yulu Gan and Phillip Isola Published: March 12, 2026 · arXiv: 2603.12228

The idea: in large, well-pretrained models, the weight space around the original parameters is already densely packed with useful task-specific solutions. The authors call these clusters "neural thickets."

In smaller models, good solutions are scattered — you need gradient-based search to find them. In large models, they're close to where you already are.

The Method — Remarkably Simple

They call it RandOpt. Here's how it works:

Take the pretrained model weights
Randomly sample N small perturbations of those weights
Evaluate each perturbation on your task
Keep the top K performers
Combine them with a majority vote

No gradients. No reward model. No RL training loop. Perturb, evaluate, vote.

💡 Code at github.com/sunrainyg/RandOpt

What the Results Showed

RandOpt kept up with PPO, GRPO, and evolutionary strategies on the tasks they tested — and this held on large-scale contemporary models.

That stopped me. These optimization methods have entire research communities, years of papers, and significant infrastructure built around them. The idea that randomly sampling neighbors of the original weights and taking a vote can match them says something about what's already sitting inside a well-trained model — waiting, not absent.

The way they frame it: small models have sparse expert solutions, so you need search to find them. Large models have dense ones. The pretrained weights aren't just a starting point. They're already rich.

What I Took From This

This paper shifted something in how I think about pretraining. We usually assume the pretrained model is a rough starting point and fine-tuning is where the real work happens. This flips that. If the solution space is already dense around the initial weights, the pretrained model is doing more work than we give it credit for.

There's also a question I don't have a full answer to yet: if random sampling with ensemble voting matches expensive RL fine-tuning, what does that mean for how we should be spending compute? I'm still working through the paper and the code, but it's the kind of result that sits with you.

Full paper: arXiv 2603.12228

Google Just Replaced Five AI Search Tools With One

noreply@blogger.com (Unknown) — Thu, 12 Mar 2026 02:18:00 +0000

Have you ever tried searching through a client’s content library where videos are in one folder, PDFs in another, and audio recordings scattered everywhere?

That’s the reality for most content libraries.

Until now, AI search tools struggled with this kind of setup because each type of content needed a different system to process it.

But that may be changing.

Gemini Embedding 2 — recently released by Google — can search across text, images, audio, video, and PDFs at the same time, without converting everything first.

For anyone managing knowledge bases, course content, research archives, or client media libraries, this could be a major shift.

What an Embedding Model Actually Does

Before explaining why this matters, it helps to understand what an embedding model is.

When AI systems search through content, they don’t read information the same way humans do. Instead, they convert content into numerical representations that capture meaning.

For example:

A sentence about a cat
A photo of a cat

Both produce similar number patterns, which allows the AI to recognize that they are related.

That’s how modern AI-powered search works.

The tool responsible for converting content into these numerical representations is called an embedding model.

The Problem With Older AI Search Systems

Until recently, every type of content required a different embedding system.

Typical setups looked like this:

Text → processed by a text embedding model
Images → processed by image models such as CLIP or SigLIP
Audio → first transcribed using systems like Whisper
Video → broken into frames or transcripts
PDFs → converted into plain text

This created several issues:

Multiple models to manage
Several conversion steps
More chances for things to break
Slower search performance

In many cases, five different pipelines were required just to search one content library.

What Gemini Embedding 2 Changes

Gemini Embedding 2 solves this by creating one shared search space for multiple content types.

Instead of converting everything separately, the model processes different media formats directly and places them into the same semantic search system.

That means a single query can return results from:

Documents
Images
Audio clips
Video files
PDFs

All at once.

For example, you could:

Upload a photo and find related videos
Submit a voice recording and find matching documents
Search inside PDF files without converting them

Supported Input Types

Gemini Embedding 2 currently supports multiple media types in one system:

Text
Up to roughly 8,000 words

Images
Up to six images in one request

Audio
Raw audio files — no transcription required

Video
Clips up to two minutes long

PDFs
Original files can be processed without converting to plain text

All of this works through one model instead of multiple specialized ones.

Combining Multiple Inputs in One Search

One interesting feature is the ability to combine different types of input into a single query.

For example, you might have:

A photo of a product
A text description of what you want

Both can be submitted together, and the system generates one combined embedding representing the meaning of both inputs.

This allows searches that were previously impossible using single-modality tools.

Easy Integration for Developers

Another surprising detail is how quickly developers can start using it.

Gemini Embedding 2 launched with support for popular AI development frameworks, including:

LangChain
LlamaIndex
ChromaDB
QDrant

Because many AI applications are already built on these frameworks, developers can integrate the model without building a new infrastructure from scratch.

It’s available through:

Google AI Studio (free tier for experimentation)
Vertex AI (enterprise deployment)

Why This Matters for Virtual Assistants and Content Managers

Think about the kinds of content many clients manage.

A podcast brand might have:

Audio episodes
Show notes
PDFs
Promotional images

A course creator may have:

Video lessons
Slide decks
Written summaries

A consultant might maintain:

Recorded calls
Presentations
Research reports

Searching across all of that in a single step has been extremely difficult.

With models like Gemini Embedding 2, developers can build search tools where one query instantly returns:

the right video segment
the correct slide
the relevant document section

All from one search bar.

The Bigger Picture

You probably won’t interact with Gemini Embedding 2 directly.

Instead, it will power the next generation of search tools used in:

knowledge management systems
research databases
course platforms
internal company search tools

But knowing that technology like this exists helps you understand what’s becoming possible.

That knowledge can make a big difference when clients start asking about AI-powered search, automation, or content organization systems.

If you manage content libraries, research archives, or client knowledge bases, this is a technology worth paying attention to.

The tools many teams will rely on in the near future are already being built on models like this.

Google Just Had a Huge Week — Nano Banana 2, Opal's Agent Step and a New Developer Ecosystem for ADK

noreply@blogger.com (Unknown) — Sat, 28 Feb 2026 10:19:00 +0000

There's been a lot happening at Google lately, and honestly, the updates from this past week alone are worth talking about. In just a few days, Google dropped a new default image model, upgraded their Opal workflow tool with real AI agent capabilities, and announced a brand-new integrations ecosystem for developers building AI agents. That's a lot to unpack — and I've been digging into all three.

I've been paying close attention to how Google is quietly (and sometimes not so quietly) building out their AI stack. These three updates feel connected in a bigger way. They're all pushing toward the same idea: faster, smarter, more autonomous AI tools that don't require you to be an engineer to use — or that supercharge you if you are one.

Nano Banana 2 — Pro-Quality Images at Flash Speed

One of the things that's always frustrated me about AI image generation is the trade-off. You either get fast and mediocre, or slow and beautiful. Nano Banana 2 — Google's new default image model built on Gemini 3.1 Flash Image — is trying to change that entirely.

What makes this interesting is the combination it's pulling off. It's generating at Flash speed while delivering what Google is calling Pro-level quality. To put that in practical terms: you're not waiting around for results, but you're also not getting blurry, inconsistent images. And the resolution range is wide — from 512px all the way up to 4K. That means the same model works whether you're making a quick thumbnail or something that needs to look polished and production-ready.

Here's the detail that really caught my attention: it can consistently handle up to 5 characters and 14 objects in a single image. If you've ever tried to generate a scene with multiple people or items and watched AI completely fall apart — characters blending together, objects disappearing — you know why this matters. Consistency across complex compositions has been a real weak spot in image generation, so this feels like a genuine step forward.

Nano Banana 2 is rolling out across the Gemini app and Google Workspace, and it's also available for enterprise use through Google Cloud. It's already the new default — which means if you're using Gemini for image generation, you're already on it.

Google Labs Opal Gets an Agent Step — Workflows Just Got Smarter

I've been curious about Opal since Google Labs introduced it as a workflow builder. The idea is that you set up a series of steps — like a recipe — and Opal runs through them to help you create something, whether that's a video, a piece of content, or a research brief. It's been useful, but the steps were static. You'd set it up once and it would just follow the same path every time.

The new agent step changes that completely. Instead of a fixed sequence, Opal now has a step where an actual AI agent takes over — it understands your goal, picks the right tools (like Veo for video generation, or web search for research), manages memory across the workflow, and routes dynamically based on what's needed. Think of it like the difference between following a printed map and having a navigation app that can reroute you in real time when things change.

This is part of a bigger shift we're seeing across the AI space, where "agentic" capabilities — AI that can reason, decide, and act rather than just respond — are becoming the new baseline. Google adding this to Opal means even people without a coding background can now build workflows that genuinely adapt. You don't have to anticipate every scenario upfront; the agent figures it out.

You can try Opal right now at opal.google — the agent step is available for all users.

Google ADK's New Integrations Ecosystem — Big News for Developers

This one is more developer-focused, but it's worth knowing about even if you're not building apps yourself. Google announced a new integrations ecosystem for their Agent Development Kit, or ADK — which is the framework developers use to build AI agents.

The idea is to make it easier for developers to connect their AI agents with external tools and services, so agents can actually do useful things in the real world instead of just talking about them. It's similar to how apps on your phone connect to different services — except here, we're talking about AI agents that can go off and complete tasks on your behalf.

What I find fascinating is how this fits into the broader picture. Between Nano Banana 2 (powerful image generation, accessible to everyone), Opal's agent step (autonomous workflows without code), and the ADK ecosystem (tools for developers to build custom agents), Google is building out every layer of the stack at once. There's something for the casual user, the content creator, and the professional developer — all in the same week.

AI Is Finally Fighting Back — And Anthropic Just Made It Official

noreply@blogger.com (Unknown) — Sat, 21 Feb 2026 11:51:00 +0000

I've been watching the cybersecurity space for a while now, and I have to be honest — it's one of those areas that used to feel completely out of reach for someone like me. No coding background, no deep technical knowledge of exploits or patches. Just a person who's curious about what AI can actually do in the real world.

But here's the thing I kept noticing over the years: the good guys were always playing catch-up.

Think back to how security worked — and honestly, how it still works for most teams. You'd have a tool scan your code, it would match against a list of known bad patterns, and spit out a report. The problem? The sneaky stuff, the subtle logic flaws, the vulnerabilities that had been hiding in open-source code for decades — those never showed up. Because rule-based tools can't reason. They can only recognize what they've already been told to look for.

Meanwhile, attackers got smarter. And faster.

That gap — between what automated tools could catch and what skilled human researchers could catch — was always the weak point. And there just aren't enough human security researchers to close it. That's not a criticism, that's just math. The attack surface keeps growing. The backlogs keep piling up.

This is why what Anthropic announced on February 20, 2026 actually stopped me mid-scroll.

Claude Code Security is now in limited research preview, and what it does is genuinely different from what I'd seen before. Instead of scanning for known patterns, Claude reads your code the way a human security researcher would — tracing how data moves, understanding how different parts of an application talk to each other, and catching the complex, context-dependent vulnerabilities that traditional tools walk right past.

What really got me is the verification layer. Claude doesn't just flag something and move on. It goes back and tries to disprove its own findings, filtering out false positives before anything reaches a developer. Every validated finding comes with a severity rating and a confidence score, so teams know what to prioritize. And nothing gets applied automatically — a human always has to approve the fix. I love that. It's AI as a sharp, tireless assistant, not a rogue decision-maker.

But here's the connection I keep thinking about: Anthropic's Frontier Red Team has been quietly building toward this for over a year. They entered Claude in cybersecurity competitions. They partnered with the Pacific Northwest National Laboratory to test AI on critical infrastructure defense. They used Claude to review their own internal code. This wasn't a product announcement that came from nowhere — it's the result of real, careful work testing what Claude could actually do before putting it in the hands of others.

And the results of that work? Using Claude Opus 4.6, their team found over 500 vulnerabilities in production open-source codebases. Bugs that had survived years of expert human review, undetected.

That's the part that really lands for me. These weren't theoretical vulnerabilities. They were sitting in real code, in real projects that real people depend on — sometimes for decades.

The reason I find this so meaningful isn't just the technology. It's the timing and the intent. Anthropic is releasing this in a limited preview specifically because the same capabilities that help defenders could help attackers. They're being deliberate about who gets access first — Enterprise and Team customers, plus open-source maintainers who can apply for free expedited access. They're working with the community to get this right before it scales.

That's a different posture than "ship it and see what happens."

We're at a point where AI is going to scan a significant share of the world's code — that's not speculation anymore, it's the direction things are clearly heading. The question has always been who benefits from that first. Attackers who use AI to find weaknesses faster? Or defenders who use it to find and patch those same weaknesses before they're exploited?

Claude Code Security is Anthropic's answer to that question.

Gemini 3.1 Pro Changed How I Actually Use AI — And It Has Nothing to Do With Benchmarks

noreply@blogger.com (Unknown) — Fri, 20 Feb 2026 09:00:00 +0000

I've been using AI tools almost every day for the past couple of years now, and if there's one thing I've learned, it's that a smarter model doesn't automatically mean you're getting smarter results. How you use the model matters just as much as what the model can do. And with Google's Gemini 3.1 Pro, there's something that I think is being really underrated in all the release coverage — the thinking level system, and what it actually means for the way you work.

This isn't a conversation about whether 77% on ARC-AGI beats 31%. It's about something more practical: the moment you realize you've been using these tools wrong, and how this new release hands you a dial you probably didn't know you needed.

What Even Is a "Thinking Level"?

Here's the quick version for anyone who hasn't come across this yet. Gemini 3.1 Pro lets you set how much thinking the model does before it responds. With the previous Gemini 3 Pro, you had two choices: low or high. With 3.1 Pro, there are now three — low, medium, and high.

Think of it like choosing between a quick gut reaction, a considered opinion, and a deep research session. The model isn't just choosing between "fast" and "slow" — it's choosing how much internal reasoning to do before it gives you an answer. At high, the model essentially behaves like a mini version of Gemini Deep Think, which is Google's most powerful reasoning model. That's a significant thing to have access to in a general-purpose assistant.

What surprised me when I started playing around with this is how much the choice actually matters. For a tricky math problem, setting thinking to high produced the right answer after several minutes of work. Setting it to low gave a fast but wrong answer. Same prompt, same model, completely different outcome.

The Problem Nobody Is Talking About

Here's what I find really fascinating about this. Most people who use AI tools have never really thought about what mode they should be in for a given task. We all tend to just fire off a prompt and expect the model to figure it out. But the thinking level system kind of forces you to be intentional, and that intentionality is where the real upgrade lives.

I started thinking about all the times I've used AI for tasks that fell into two completely different buckets. There's the stuff I need quickly — drafting a quick reply, summarizing a short article, brainstorming a list of ideas, generating a social post. And then there's the stuff where I actually want the model to sit with a problem — writing a full script outline, analyzing something complex, working through a nuanced question. Those two categories have always existed. What's new is that now I have a setting that actually reflects that difference.

Before 3.1 Pro, running everything at the same compute level was a bit like always driving in the same gear. Sometimes it worked. Sometimes it didn't. Now there's a gearshift.

How This Actually Changes My Workflow

When I started being intentional about thinking levels, a few things shifted for me pretty quickly.

For anything where I need a fast creative spark — like coming up with a hook for a video, finding synonyms, or doing a quick rewrite of a sentence — low thinking is more than enough. It's snappy, it's responsive, and frankly it's exactly what you want when you're in flow and don't want to wait. Speed matters there.

For medium tasks — things like drafting a structured outline, explaining a concept clearly, or building a content calendar — medium thinking has become my go-to. It takes a little longer, but the output feels more considered. Less surface-level. Like the model actually thought about the structure before it started writing.

And then there's high. I've started reserving high thinking for the things that actually deserve it. Complex analysis, tricky research questions, anything where getting the answer wrong would cost me time. The wait is longer — we're talking several minutes in some cases — but the quality of what comes back is on a different level. It's not just more text. It's more thoughtful text.

Why This Matters Even If You're Not Technical

I know a lot of people who use AI tools but feel like they're not getting as much out of them as they should. And honestly, after thinking about this thinking level system, I wonder if part of that frustration is just a mismatch between the task and the mode.

If you've ever asked an AI a complicated question and gotten a shallow answer, it might not be a model quality problem. It might be a compute budget problem. The model didn't spend enough time thinking. And now, for the first time, you have direct control over that.

That's actually a pretty big shift. Instead of just hoping the model figures out when to try harder, you get to tell it. It puts a little more responsibility on the user, sure. But it also puts a lot more power in your hands.

The Bigger Picture

What I keep coming back to is this: Gemini 3.1 Pro isn't just a smarter model. It's a model that respects the fact that not every question deserves the same amount of effort. And it's the first time I've felt like a general-purpose AI assistant is actually designed around how I naturally work — some things fast, some things slow, some things in between.

The AI tools that stick around aren't always the ones with the highest benchmark numbers. They're the ones that fit into how people actually think and work. This thinking level system feels like a step in that direction — and it's one I don't think enough people are paying attention to yet.

Grok 4.20: What Nobody Is Actually Talking About

noreply@blogger.com (Unknown) — Fri, 20 Feb 2026 06:22:00 +0000

There's been a lot of noise about Grok 4.20 this week. The four agents, the multi-agent setup, the "AI brains arguing with each other" framing. I get it — it's a fun story. But the more I dug into this release, the more I felt like everyone was covering the surface and missing the stuff underneath that's actually worth paying attention to.

So here's what caught my eye.

The model solved a real math problem nobody had solved before

I came across this one almost by accident and it stopped me completely.

Paata Ivanisvili, a math professor at UC Irvine, had been working on an open problem in harmonic analysis — trying to find the exact maximum of something called a Bellman function. He and his student had already published a paper on it. They had a partial answer. The problem was still technically unsolved.

He got early access to the Grok 4.20 beta, fed it the problem, and within five minutes it handed him an explicit formula — a cleaner, sharper result than what he and his student had managed. His reaction on X was basically just: "Wow."

What makes this different from the usual "AI is smart" story is that benchmarks test problems with known answers. This didn't. Grok wasn't pulling a solution from somewhere — it was reasoning toward something that hadn't been written down yet. That's a genuinely different category of thing, and it happened because the Benjamin agent (the math and logic one) is specifically built for this kind of step-by-step proof reasoning.

One result doesn't prove everything. But it happened, it's documented, and it made me think differently about what "AI for research" actually looks like in practice.

It was already winning competitions before anyone knew it existed

Here's something that got buried in the launch coverage: Grok 4.20 didn't launch when the public beta dropped on February 17. It had been running — quietly, under fake names — for weeks before that.

On LMArena it showed up as "Theta-hat" and "Slateflow." On DesignArena it appeared as "Pearl" and "Obsidian." And in Alpha Arena's live AI stock trading competition, a "Mystery Model" was quietly the only entry making money while every other AI lost. That Mystery Model was Grok 4.20.

xAI's last official model announcement on their news page is still Grok 4.1 from November 2025. There was no blog post for this launch. No announcement thread. Just posts from employees on X and a new option appearing quietly in the grok.com dropdown. By the time most people heard about it, it had already been competing for weeks.

The "four brains" framing is wrong — and the real version is more interesting

Everyone's been describing this as four separate AI models arguing with each other. That's not quite what's happening, and I think the actual explanation is more impressive.

Grok 4.20 is one model — estimated around 3 trillion parameters — with four different roles running from the same base weights. Grok the coordinator, Harper the real-time researcher, Benjamin the math and logic brain, Lucas the contrarian wildcard. They're not four separate models. They're four ways of prompting the same model, each with different tool access and context framing.

Why does this matter? Cost. Running four truly separate models would be four times as expensive. Because these agents share weights and the same input context, xAI puts the overhead at 1.5x to 2.5x — not 4x. That's what makes this available at a consumer price point rather than Grok Heavy's $300/month tier. The agents don't have long debates either. The rounds are short, structured, trained through reinforcement learning to be efficient. They send targeted corrections and move on.

I found it interesting that nobody in the coverage this week mentioned this. "Four brains" is a better headline, sure, but one brain wearing four hats is actually a harder technical trick to pull off.

The trading competition result deserves more scrutiny than it got

Alpha Arena Season 1.5 was a live stock trading competition — real transactions, verified on the blockchain. GPT-5, Gemini, Claude, open-source models, Chinese models — everyone participated in multiple strategy variants over several weeks. When it ended, every single configuration of every other model finished in the red. Grok 4.20's four variants were the only ones in profit, with the best posting around 35% returns from a $10,000 start.

A few people mentioned this. Nobody really asked why.

My read: it wasn't that Grok out-thought everyone on finance. It's that Harper — the agent that pulls from X's real-time feed of roughly 68 million English tweets per day — gave it a live information edge the other models didn't have. The competition fed other models summarized news prompts. Grok was processing raw market sentiment as it happened.

That's worth being honest about, because it means the result says more about data access than raw intelligence. But here's the thing — that data access is the architecture. That's what the Harper agent was built to do. So the win was real, and it was structural, and it came from a deliberate design choice.

Grok 4.20 is the proof of concept. Grok 5 is the actual bet.

While everyone's been testing the 4.20 beta, xAI is already training its successor. Grok 5 is reportedly sitting around 6 trillion parameters — roughly double the size of 4.20 — with a target launch somewhere between April and June 2026.

For context, Grok 4.20 arrived in a crowded week. OpenAI shipped GPT-5.3-Codex on February 5. Anthropic released Claude Sonnet 5 on February 3. By that measure, this was a delayed point release catching up while competitors were already moving to the next generation. Even xAI treated it like a soft launch.

Grok 5 will not be a soft launch. xAI is spending roughly $1 billion a month. SpaceX formally acquired them weeks ago. An IPO is on the table. A 6-trillion-parameter release is exactly the kind of moment you build that story around.

What I keep thinking about is that the ecosystem is already being built before most people have noticed. Perplexity is reportedly running Grok 4.20 under the hood for a new search mode. There are signs of something called Grok Build — a coding tool with up to 8 parallel agents. The multi-agent architecture isn't a feature. It's the foundation, and xAI is building on top of it fast.

Grok 4.20 showed the approach works. The math problem, the trading competition, the benchmark trajectory — all of it points in the same direction. Grok 5 is where we find out if xAI can actually deliver on the scale of that promise.

I'll have a full video on this on YouTube soon — I want to actually get hands-on time with it first before I say anything definitive. But if you're following AI closely, this release is worth paying more attention to than the "four agents" headline suggests.

Claude Sonnet 4.6 Is Here — And There's Way More Going On Than the Benchmarks Show

noreply@blogger.com (Unknown) — Thu, 19 Feb 2026 14:11:00 +0000

There's been a lot of buzz this week about Claude Sonnet 4.6, Anthropic's latest model release. And honestly? Most of the coverage I've seen is stopping at the surface level — benchmarks, pricing, computer use scores. All of that is interesting, sure. But when I started looking closer at what actually shipped alongside this model, I found four things that nobody's really talking about that I think matter a lot more for people who are actually using Claude day to day.

That 1 Million Token Context Window Has a Catch

Okay, so everyone is excited about the 1 million token context window. And I get it — the number sounds incredible. A million tokens is enough to hold entire codebases, thousands of documents, months of conversations. But here's what I didn't realize until I looked into this more carefully: a big context window doesn't automatically mean a useful context window.

There's a real issue in AI called context rot. The basic idea is that as you keep filling up a model's memory during a conversation, its ability to actually use older information starts to degrade. It's a bit like trying to hold too many things in your head at once — the stuff from earlier starts slipping away. Anthropic's previous model, Sonnet 4.5, scored just 18.5% on a benchmark called MRCR v2, which specifically tests whether a model can find information buried deep in a long context. That's... not great.

Sonnet 4.6 is genuinely better at this. But there are two things I think people need to know before they get too excited. First, the 1 million token window is still in beta — it's not just available to everyone right now, and you need to explicitly turn it on. Second, and this one surprised me, the pricing changes dramatically once you cross 200,000 tokens. Below that threshold you pay the standard rate. Above it, the pricing structure shifts significantly and applies to your entire request, not just the extra tokens. So if you're planning to throw huge amounts of text at this model, make sure you understand what that's going to cost before you build a workflow around it.

Here's the Part That Actually Impressed Me

Now here's where it gets interesting, because Anthropic didn't just train a better model and call it a day. They shipped two features alongside Sonnet 4.6 that directly address the context rot problem — and almost nobody is talking about them.

The first is dynamic web search filtering. When Claude searches the web, it now writes and runs its own code to filter search results before loading them into context. Instead of pulling in a full HTML page and reasoning over all of it — ads, navigation menus, irrelevant paragraphs and everything — it strips out the noise first and only keeps what's relevant. Anthropic tested this across two benchmarks and found it improved accuracy by an average of 11% while actually cutting input tokens by 24%. That's a really meaningful result. Quora's Poe platform tested it against all the major frontier models and said Opus 4.6 with this feature "achieved the highest accuracy on our internal evals" — specifically because it approaches research the way a human researcher would, filtering information programmatically instead of reasoning over raw noise.

The second is programmatic tool calling, which just hit general availability. This one is more for developers, but the idea is fascinating. When Claude needs to call multiple tools — say, querying a database five times to compare regions, then sorting and summarizing the results — it can now write code that does all of that inside a sandboxed container without bringing each intermediate result back into the conversation context. The result only shows up once everything is done. Think of it like doing all your rough math on a scratch pad before writing the final answer on the paper — the scratch work never clutters the main context.

Together, these two features tell a really clear story: Anthropic's answer to context rot isn't just a bigger bucket. It's smarter filtering so less noise goes in.

Should You Actually Cancel Opus?

This is the question I keep seeing pop up and I wanted to think through it properly. Sonnet 4.6 costs $3 per million input tokens and $15 per million output tokens. Opus 4.6 is roughly 1.7x more expensive on input and output. For most individual users that difference feels abstract — but if you're building on the API and processing a lot of requests, it compounds fast.

What made me look at this differently is where Sonnet 4.6 actually beats Opus. On agentic financial analysis — think tasks like researching stock data, calculating ratios, pulling together a market summary — Sonnet 4.6 scored 63.3% versus Opus 4.6's 60.1%. On office tasks, Sonnet leads again. On computer use benchmarks, the gap is almost nothing: 72.5% for Sonnet versus 72.7% for Opus. For everyday knowledge work, Sonnet 4.6 is genuinely at the same level for a meaningfully lower price.

The places where Opus still wins are specific: novel problem-solving, deep codebase work, complex situations where getting it exactly right is more important than getting it fast and cheap. Anthropic themselves describe Opus as the right choice for "codebase refactoring, coordinating multiple agents in a workflow, and problems where getting it just right is paramount." That's a real distinction — but it's a narrower one than it used to be.

And here's one more thing that matters for API developers. Because of programmatic tool calling, tool results from multi-step workflows don't count toward your token usage at all — only the final output does. So if you have workflows that currently make eight or ten tool calls in sequence, each one loading results back into context, you may be spending significantly more than you need to. That changes the cost math even further in Sonnet's favor for the right use cases.

The Security Problem Nobody Mentioned

I want to talk about prompt injection because every video I watched mentioned it in one sentence and moved on. I think it deserves more attention than that — especially now that Claude has computer use and can take real actions on your behalf.

Here's what prompt injection actually means in practice. Imagine you ask Claude to read through your emails and schedule any meeting requests it finds. One of those emails was crafted by someone who knew an AI would read it. Inside that email, hidden in the text, are instructions that tell Claude to forward any email with the word "confidential" to an external address before it drafts your replies. You'd never see it happen. That's the attack. Anthropic has described exactly this scenario in their own research on browser-agent security, and it's not hypothetical — it's an active concern for anyone building or using agentic AI.

Anthropic says Sonnet 4.6 is significantly better at detecting and resisting these attacks compared to its predecessor, and their evaluations show it performs similarly to Opus 4.6 in this area. That's meaningful progress. But independent testing on earlier Claude models found that while the model actively resists simple injection attempts, it can still be confused when the malicious instructions are buried inside what looks like a legitimate document or data structure.

What I didn't see anyone mention is a second security issue that comes with programmatic tool calling. When Claude calls your tools programmatically and gets results back, those results come back as raw strings — and those strings can contain anything, including code snippets that might get processed by the execution environment. If your tools are pulling data from external sources or user inputs, there's a real code injection risk if you're not validating what comes back before acting on it. This is separate from prompt injection — it's a layer deeper, and it's something every developer building agentic workflows needs to think about before shipping.

The honest summary is this: Sonnet 4.6 is more secure than what came before. But "more secure" and "fully solved" are very different things. The more autonomous you make your agents, the more carefully you need to think about what they can be tricked into doing.

What This All Means

I find the Sonnet 4.6 release genuinely exciting — not just because of the model improvements, but because of what the surrounding features tell us about where Anthropic is heading. They're building a system where Claude reasons over less noise, not more. Dynamic filtering, programmatic tool calling, context compaction, memory tools — these are all solving the same underlying problem. And the fact that accuracy went up while token usage went down on web search benchmarks suggests this approach is actually working.

If you're a knowledge worker using Claude through the app, the takeaway is pretty straightforward: this model is fast, capable, and meaningfully better at the kind of office work most people actually do. If you're a developer building on the API, there are real architectural decisions to make now — about when to use Sonnet versus Opus, how to take advantage of programmatic tool calling, and how to think about security in agentic workflows.

What I'm watching next is how the 1 million token context window performs in real production use cases over the next few weeks. The beta label is still on it for a reason. But the direction is clear — and it's more interesting than most of the coverage I've seen this week.

Sources: Anthropic Claude Sonnet 4.6 announcement · Dynamic Web Search Filtering · Programmatic Tool Calling Docs

Google's Gemini 3 Deep Think Just Got a Major Upgrade — And It's Designed for Real Science

noreply@blogger.com (Unknown) — Fri, 13 Feb 2026 03:19:00 +0000

There's been this interesting trend in AI lately where models are getting better at reasoning through complex problems. We've seen it with OpenAI's o1 and o3, DeepSeek's R1, and now Google is making a serious push into this space with a major update to Gemini 3 Deep Think.

What makes this update different from the reasoning models we've seen before is that Google specifically built it for scientists, researchers, and engineers working on real-world problems. This isn't just about solving math competitions anymore—though it still does that incredibly well. It's about tackling messy, incomplete data and problems without clear solutions, which is what actual research looks like.

I've been following the development of reasoning models closely, and Deep Think's focus on practical scientific applications is a shift I find really interesting. This is part of a larger movement where AI is moving from being a general-purpose tool to something more specialized for specific domains.

Google AI Ultra subscribers can access the updated Deep Think in the Gemini app starting today, and for the first time, researchers and enterprises can apply for early access to use it via the Gemini API.

Why Deep Think Focuses on Science and Engineering

The way Google approached this update is pretty clever. Instead of just making a model that's good at abstract reasoning, they worked directly with scientists and researchers to understand what kinds of problems they actually face in their work.

Real research isn't like solving textbook problems. You're dealing with incomplete data, messy information, and questions that don't have single right answers. Traditional AI models often struggle with this kind of ambiguity, but Deep Think was specifically trained to handle it.

What caught my attention in the announcement were the real-world examples. A mathematician at Rutgers University used Deep Think to review a highly technical paper and it found a logical flaw that had passed through human peer review. At Duke University, researchers used it to optimize crystal growth methods for semiconductor materials, hitting a precise target that previous methods couldn't achieve.

These aren't just impressive demos—they're solving actual research bottlenecks.

The Numbers Are Genuinely Impressive

Deep Think continues to push what's possible on academic benchmarks. It scored 48.4% on Humanity's Last Exam, a benchmark specifically designed to test the limits of frontier models. That's without using any external tools, just pure reasoning.

It also achieved 84.6% on ARC-AGI-2, which tests abstract reasoning abilities that supposedly indicate progress toward artificial general intelligence. The ARC Prize Foundation verified this result, which gives it more credibility.

On Codeforces, a competitive programming platform, Deep Think reached an Elo rating of 3455. To put that in perspective, that's gold medal territory at international programming competitions.

The really interesting part is that Deep Think now also excels at chemistry and physics olympiad problems, achieving gold medal-level performance on both. It scored 50.5% on CMT-Benchmark, which tests advanced theoretical physics understanding.

Built for Practical Engineering Applications

Beyond benchmarks, what makes Deep Think stand out is how it's being used in practice. Google designed it to interpret complex data and model physical systems through code, which means engineers can actually use it for real work.

One example they showed is turning a sketch into a 3D-printable file. You draw something, Deep Think analyzes it, models the complex shape, and generates a file ready for 3D printing. That's the kind of practical application that makes this more than just an impressive reasoning model—it's a tool people can actually use.

Google's also making this available through the Gemini API for researchers and enterprises, which is significant. Previous versions of Deep Think were mostly limited to the consumer app, but opening it up via API means developers can integrate it into their own workflows and tools.

What This Means for AI Reasoning Models

This release is part of a broader competition happening right now in the reasoning model space. OpenAI has o1 and o3, DeepSeek released R1, Anthropic has been working on extended thinking capabilities, and now Google is pushing hard with Deep Think.

What's interesting is how these companies are differentiating their approaches. OpenAI focuses on general reasoning, DeepSeek emphasizes efficiency and open-source access, and Google is positioning Deep Think as the model for scientific and engineering work.

The practical difference here is that Deep Think isn't trying to be everything to everyone. It's specialized for domains where deep reasoning through complex, messy problems actually matters—research, engineering, advanced mathematics, theoretical physics.

For anyone working in these fields, having a model that understands the nuances of scientific work rather than just being good at logic puzzles could be genuinely transformative.

The fact that Google worked directly with scientists to build this, and that early testers are already finding real research applications, suggests this is more than just benchmark chasing. It's an attempt to make AI actually useful for advancing human knowledge in concrete ways.

If you're a researcher, engineer, or working in a technical field, Deep Think might be worth keeping an eye on—especially if you can get into the early access program for the API. This could be one of those tools that changes how certain kinds of work get done.