Keep a human on the click

They shipped memory, a Slack trigger, and a real browser

What is up people.

This is issue 1 of AI Mentorship. If you can open ChatGPT and Notion, you can use what is in here. This is about understanding AI, using it well, and staying optimistic without pretending the hard parts are not there.

This week is a product week, not a speech about the newsletter. The labs did not ship a new flagship model for you to chase. They shipped memory, a trigger, and a browser.

The assistant can carry what you already told it, start when Slack or Gmail moves, and click through pages that never got a connector (a connector is a proper hook into an app, like Gmail or Slack, so the model does not have to click around a website as you). That is more useful than last week’s chat box, and it is also easier to leak a rant into an email, or to click a button you did not mean.

Both things can be true. Pick one control. Edit it. Keep a human on the consequential click.

📌 TL;DR

• Claude memory → Chat and Cowork now share one memory you can read and edit. The catch is that junk and private rants get remembered too, unless you clean them.

• ChatGPT Work triggers → Plus and Pro can start a task when Gmail, Slack, or GitHub moves. Free cannot. Narrow the filter or it will fire on noise.

• Claude’s browsers → Paid Claude can click in Chrome, or use a built-in Cowork browser that is not your tabs. Prompt injection (hidden instructions on a page that try to hijack the agent) is still real.

• Builder’s notes → A 20-minute setup: audit Claude’s memory topics, then write one Notion skill. This is a how-to, not a fake diary.

Claude finally remembers across chat and Cowork

The most annoying part of using two Claude surfaces was briefing the second one like a new hire. You would think something through in chat, then open Cowork (Anthropic’s hand-off mode, where Claude runs a longer task in the cloud instead of chatting back and forth) and type the same facts again.

On August 25, Anthropic made the memory in chat the same as the memory in Cowork. TechCrunch called it the difference between two products under one roof and one continuous assistant, and that is the right read.

Claude now writes topics into memory as you chat, instead of waiting to summarize after you leave. Mention that a deadline moved to September, and the next conversation already has it. You do not have to say “remember this.”

The part that actually makes this safe enough to use is the list. Settings, then Memory, then Topics: every saved topic is a short file you can read, edit, or delete. Fix the company’s old name once, and every later chat and Cowork run gets it right.

Memory is on by default on Free, Pro, and Max, on web, desktop, and mobile. On Team and Enterprise, an admin has to allow it, and it stays off for you until you turn it on. Sensitive topics (health, beliefs, politics, and similar) stay out unless you opt in, and government IDs and a few other categories stay out even then.

Ben Tossell wrote on August 27 that he is not sure shared memory is a good thing. You do not want a frustration you mentioned in a random chat to change the tone of an email Cowork writes later, and he is not wrong.

If the list is editable, the job is to EDIT the list. Open Topics this week, delete anything you would not want sitting next to a client email, and write one sentence about how you like updates, who they go to, and what “done” means on the project in front of you. That is the whole upgrade: a notebook you can actually correct.

Anthropic Claude’s memory works everywhere, August 25, 2026

TechCrunch Claude Cowork finally remembers what you told the app in chat, August 25, 2026

Ben’s Bites Who let the agents in, August 27, 2026

ChatGPT Work can start when Slack or Gmail moves

Scheduled tasks used to mean a clock: every Monday at 9, every Friday at 4. That is fine for a recap. It is useless for the email that actually matters, which arrives at 2:14.

On August 25, OpenAI’s ChatGPT release notes added webhook-triggered tasks in ChatGPT Work. A webhook is a signal from another app that something happened, and the first supported signals are a new Gmail message, a new Slack channel message, and GitHub pull request activity.

Plus and Pro can create these in Work on web, iOS, and Android. Free and Go cannot. Free users can still run up to three ordinary scheduled tasks, once a day at most. If you are on Enterprise or Edu, an admin has to turn on “Allow event-triggered scheduled tasks” first, and it is off by default.

The setup is short. Settings, then Apps, then connect Gmail, Slack, or GitHub. Open Work, describe the event and what ChatGPT should do, and fill the three boxes you will see: Trigger, Condition, Prompt.

For Slack, add @ChatGPT to every channel the task watches. Reactions, edits, deletes, and DMs do not fire it. Only new messages, and that last line is the constraint that saves you.

If your team marks “this needs a human” with an emoji, this feature will not see it. If you watch a busy channel with no sender filter, you will get a pile of summaries nobody asked for.

OpenAI’s own example is the right size. Summarize an email that says registration opened, or draft next steps after a named client leaves feedback in Slack. Use one sender, one channel, and one output you will actually read.

Actions that need approval pause until you review them. Leave that on for anything that sends, files, or spends.

This is the week ChatGPT stopped waiting for you to remember to check. It still needs you to decide what is worth checking.

OpenAI ChatGPT release notes, August 25, 2026

OpenAI Help Scheduled tasks in ChatGPT

Claude can click the pages that have no connector

A lot of real work still lives on a site with no Gmail-style connector: a vendor portal, an internal dashboard, a form that only exists as a webpage.

On August 26, Anthropic made Claude in Chrome generally available on every paid plan. Claude can view the page you are on, click, type, move between tabs, and fill forms, using the logins you already have. It can also approve some actions on its own now, instead of tapping you for every click. A safety classifier (a second check that asks “does this match what the user asked?”) reviews the action before it runs, and you can turn auto-approve off.

The same day, Anthropic shipped a built-in browser inside Cowork on the desktop app, with nothing to install. When a task needs the web, a browser opens in the side panel. That browser is Claude’s, not yours. It does not see your tabs, bookmarks, or passwords unless you bring a login over, site by site, and banking, email, and single sign-on stay out unless you choose to include them.

Use the split the way Anthropic described it. Claude in Chrome is for the page you already have open, with the accounts you are already in. The built-in browser is for handing off research, invoices, or a portal while you keep working.

If you already use the Chrome extension, it stays the default. Otherwise the built-in one takes over once it reaches you.

Pro, Max, and Team are getting it this week, and Enterprise admins can turn it on now. Chrome only, not other Chromium browsers, and not mobile. You still need the desktop app for files on your computer.

The hard part is prompt injection. Hidden instructions in a page, an email, or a form field can try to redirect the agent. Anthropic spent a year on this before calling Chrome generally available.

They say probes scan tool results, and the classifier blocks actions that do not match your request. They also say the risk is reduced, not gone, and you should start on sites you trust.

Take that at face value. Do not point either browser at a bank, a payroll admin, or a page you would not let a new intern click unsupervised. Watch the first run, and if it drifts, stop it.

A browser that works is a gift. A browser you do not watch is a liability.

Anthropic Claude in Chrome is generally available, August 26, 2026

Anthropic Claude gets its own browser in Cowork, August 26, 2026

Anthropic Help Get started with Claude in Chrome

Also this week...

• Slack Code → As of August 26, a coding agent can spin up a dedicated Slack channel for a longer job, with diffs, HTML previews, and a place for the team to review before anything ships. Live today with Claude, Devin, Copilot, and Vercel. ChatGPT is coming soon. You still need access to the partner agent.

• Gemini Live → August 26. Talk, then let it act. Daily Brief (Google AI Plus and up) reads Gmail and Calendar out loud. Spark (Google AI Pro and up) can turn a voice brain dump into a Doc and keep running when you leave. Connect apps in Personal Intelligence first.

• ChatGPT Work, signed-in sites → Also August 25. Work’s cloud browser can pause on a login, let you enter credentials in a form the model cannot see, then keep going. Plus and Pro. Confirm before payments. Still do not start with a bank.

• OpenAI and Cursor → August 28. OpenAI says it will wind down model access in Cursor, proposed shutoff November 12, 2026, after SpaceX bought Cursor. If you live in Cursor, that is a calendar date, not a vibe. Have a second model ready inside the same tool before November.

💡 Builder’s notes

A 20-minute setup, not a diary

Here is a setup you can actually finish before lunch, using things that shipped in the last seven days.

1. Audit Claude’s memory (8 minutes)

Open Claude, then go to Settings, Memory, Topics, and read the files. Delete anything you would not want in a client email. If a topic is close but wrong, edit the sentence so it is true.

Add one short topic of your own, in plain language:

I send weekly updates in five bullets: what shipped, what slipped, what I need, risks, and the next decision. No fluff. No hedging.

That sentence will now sit next to Cowork when you ask for the update. If you are on Team or Enterprise, memory may be off until you or an admin turns it on.

2. Write one Notion skill (12 minutes)

A skill is a reusable instruction stored as a page. Notion’s own rule is the right one: if you would paste the same prompt twice, it is a skill.

Go to Library in the sidebar, open the Skills tab, and add a skill. If you want Notion Agent to pick it automatically, put it in a skills database and write a clear Description. Automatic use only works when that description exists.

Paste this as a starting page, then change the names:

Weekly recap

Description: Use when someone asks for a weekly update, a status recap, or “what happened this week.”

Goal: a sendable update in five bullets.

Inputs: the page or notes the user has selected. If nothing is selected, ask for the project name.

Format:

1. Shipped

2. Slipped

3. Need from others

4. Risks

5. Decision needed this week

Constraints: no adjectives that do not change a decision. No “hope to.” Name owners. If a fact is missing, write UNKNOWN instead of guessing.

Run it once on last week’s notes, then tighten the page when the output is wrong. The skill gets better because you edited the page, not because you wrote a longer prompt in chat.

If you also live in ChatGPT Work, the cousin of this skill is one webhook task for a single sender, not a whole Slack workspace. Same idea: narrow the input, name the output, and a human still sends it.

🧰 Tools to try

• Claude in Chrome → Official Anthropic extension. Paid plans only. Confirm the publisher is Anthropic before you install. (Chrome, not Edge or Arc)

• Notion Skills → Reusable instructions as pages. Library, then Skills. Put them in a skills database if you want automatic use.

• Scheduled tasks in ChatGPT → Clock tasks for Free. Event-triggered Gmail, Slack, and GitHub tasks for Plus, Pro, and eligible workspaces.

• Claude Academy → Anthropic’s free learning site. Start with Claude.ai or Cowork if you are not a developer. Browse without signing in. Sign in to save progress.

🥣 Brain food

• 5 Rules for Better AI Writing → Nathaniel Whittemore (NLW) on The AI Daily Brief, August 27. The purity fight is over. Quality is not. Lock the thesis before you hand the middle to a model, then strip the obvious AI-isms.

• What We Learned From 15 Hours of Anthropic Certification Training → Natalia Quintero at Every, August 31. The courses give a shared vocabulary, not a playbook. Her team’s consensus: Anthropic’s docs beat the videos if you actually want to use the tools.

• Who let the agents in → Ben Tossell, August 27. The memory caveat in beat 1 lives here, plus a clean explanation of ChatGPT Work’s sign-in form. Read him when you want the “I am not sure that’s a good thing” line before you turn a feature on.

If you only do one thing after this letter, do the memory audit, then write the skill. If you have never named how you like work done, that part takes some thinking. The setup itself is simple. Don’t overcomplicate it.

That’s it. That’s the whole thing.

P.S. This issue was written by AI. Payton built the automation, then put taste and judgment on what it was allowed to argue, what it had to cite, and what it was forbidden to invent. Value is still value. When he writes one himself, it will say so and he will sign it.