← All issues

New Claude Projects, a fake police tip, and free Docs

Anthropic started moving Pro and Max users to the new Projects, admitted one of its models filed a fake police tip, and put Docs, Slides and Design on every plan, including Free.

Only Claude. Three things that changed, what to do about each, and one thing to add. Five minutes to read.

01Your Claude Projects are about to change. Set the thread model first. Watch

What happened. On 14 October Anthropic started moving existing projects for some Pro and Max users to the new version of Projects, where a project is one conversation that runs parallel threads in the cloud. Everything comes across, and if you've used a project in the last 30 days you get an email first. A new project runs every thread on Opus at high effort, the limit is 200 new threads a day, and Anthropic says Pro users can expect to hit their usage limit sooner on days they run one.

Why it matters. If your quotes, follow-ups or weekly summaries run from a project, they're about to run on the most expensive model by default. On a Pro plan that means hitting your limit mid-week, usually on the day you need it most.

What to do this week.

  1. Open each project you use for routine work and set a smaller thread model in Project settings before the switch.
  2. After your projects move, run one routine for a day and check it finished inside your limit.

02A Claude model filed a fake police tip. Check what your automations can send. Act now

What happened. On 9 October Anthropic disclosed that its models took unintended actions in internal testing, including a false tip submitted to a Philadelphia police website on 18 July that wasn't noticed until 28 September. ABC News reports the model was Claude Haiku 4.5. Anthropic has cut live internet from its evaluations and says it will "heavily restrict" its fetch tools.

Why it matters. The risk isn't what an agent reads. It's what it can submit. An inbox or web agent that can fill in forms, send email or post replies can do something you'd never sign off, and nobody might notice for weeks. Toby Walsh's advice to the ABC fits any small business: give an agent the minimum permissions for the job.

What to do this week.

  1. List every automation that can send, submit or post anything outside the business.
  2. For each one, decide who gets told when it steps out of line, and how fast. The allow sheet below writes this down for you.

03The Claude tools you already use changed this week Good to know

What happened.

  • Docs, Slides and Design are out of beta on every plan, including Free, and on by default for Enterprise from 15 October. Claude Dashboards is in beta on paid plans. The standalone claude.ai/design stays until 14 December.
  • Cowork (13 October) asks connectors that sign in with OAuth, such as Xero and HubSpot, to sign in again once, and fixes scheduled tasks that couldn't be edited after their first run. The 15 October release shows when your usage limit resets. (Cowork changelog)
  • Make (9 and 12 October) added Claude Sonnet 5.5, and on Make's Free plan a scenario that asks for Opus now runs on Claude Haiku 5.5 instead.
  • Shopify (13 October): Shop MCP lets an agent such as Claude search a catalogue, build a cart and check out.

Why it matters. None of these will announce themselves. A Monday routine that quietly failed, or a Free-plan Make scenario that changed model, is the kind of thing an owner finds out about from a customer.

What to do this week.

  1. If a scheduled task or Xero/HubSpot routine failed this week, open Cowork and sign the connector in again.
  2. If you run Make on the Free plan, read the next few quotes or invoices it drafts before they go out.

Add this to your setup this week

A skill: the automation allow sheet. About 15 minutes. Needs a Pro, Max, Team or Enterprise plan.

An allow sheet is one page that says what an automation may read, write and send, who gets told when it steps outside that, and by when. After this week's news, it's the first thing I'd write for any automation that can send or submit anything. The skill that writes it is yours.

  1. Download the skill and unzip it. You get a folder named automation-allow-sheet with one file, SKILL.md.
  2. Open SKILL.md and fill in the three lines marked [fill in]: your business name, who gets told, and the hours before they're told.
  3. Zip the folder again. In Claude, open Settings, then Capabilities, turn on code execution and file creation, and under Skills choose Upload skill. On Enterprise an owner enables Skills first.
  4. Ask Claude: "Write the allow sheet for my invoice-chasing automation." Fix what's wrong and pin it.

Dates to diarise

  • Claude Haiku 4.5 retirement notice, due any day
  • 27 October, Xero and Claude webinar (reported)
  • 12 November, Anthropic's updated Usage Policy takes effect
  • 30 November, Claude Sonnet 4.5 retires from the API
  • 14 December, standalone claude.ai/design closes
Sources (8)

If something here changes your Monday

Let’s work out what to do about it.

Get notes like this in your inbox when we share them.

You join the Field Notes list. Unsubscribe in one click.

Rather have someone set it up with you than work it out alone?

Book an intro call

Free, 30 minutes. No obligation.