01What Are the Claude New Features This Week?

The Claude new features this week are Fable 5.2, Whiteboards, Sheets, Data, Meetings and interactive connectors. Together they work like one back office that runs while you talk to Claude.

In this episode, Julian Goldie goes through each feature with a workflow you can copy. He says a member of his community asked how to replace a messy client system, and these six features answer that question.

Here is the quick list:

  • Fable 5.2, a new model that can hold a whole client folder at once.
  • Whiteboards, a shared board where Claude groups your team's notes.
  • Sheets, where you describe a spreadsheet and Claude builds it.
  • Data, which builds live dashboards from your data.
  • Meetings, where Claude joins a call and takes notes.
  • Interactive connectors, which open your apps inside Claude.

Each one fixes a different part of running a business. Julian sums it up this way: Fable thinks, Whiteboards plan, Sheets organize, Data reports, Meetings capture and connectors act. The sections below explain what each feature does and how a store owner or agency can use it.

02Fable 5.2: The New Claude Model

The first of the new features is Fable 5.2, a new Claude model. It is available to everyone in the Claude apps and in Claude Code.

Here is what is new about it:

  • It has a 1 million token context window. In plain terms, it can hold a whole client folder in its head at once.
  • Adaptive thinking is always on.
  • You steer it with the effort setting, which goes from low up to max.

The large context window matters for real business work. Instead of feeding Claude one document at a time, you can give it everything for a client in one go. That means it can spot problems that only show up when you look at all the pages together.

The effort setting gives you control over how hard the model works. A low setting suits quick, simple jobs. A higher setting suits bigger jobs where you want the model to dig deeper.

Julian uses medium effort in his test, which is covered next.

Because Fable 5.2 also works in Claude Code, you can use it on work that lives on your computer, not just in the chat window.

03How to Test Fable 5.2 Against Opus 5.5

A member asked Julian where Fable 5.2 beats Opus 5.5 on real work. Instead of guessing, he suggests a fair test on a job you already run.

His example is an SEO agency's monthly audit across 40 pages. Here is how to run it:

  1. Pick one real job you do every month, like a 40-page site audit.
  2. Write one prompt and keep it exactly the same for both models.
  3. Paste in every page.
  4. Ask for the 10 biggest problems, ranked, with a fix for each one.
  5. Run it once on Opus 5.5.
  6. Run it once on Fable 5.2 at medium effort.
  7. Compare how many problems each model found.
  8. Check how many of those problems were real.

The last step is the most important. A model that lists more problems is not better if half of them are wrong. Counting the real problems tells you which model is more useful for your work.

If you build in Claude Code, Julian points out that you can run that same audit over your whole setup in one pass. This kind of side-by-side test works for any job, not just SEO audits.

04Claude Whiteboards: Turn Messy Notes Into a Plan

Whiteboards is in beta. It is a shared board where your team drops notes, and Claude groups them into themes.

Here is the workflow Julian shows:

  1. Open a whiteboard.
  2. Paste in your team's notes.
  3. Ask Claude to group these into themes.
  4. Ask it to build a launch timeline with an owner and a date for each step.
  5. Watch Claude sort the board in front of you.
  6. When it looks right, turn the board into a doc or a deck.

There is also a handy trick. You can drag a box around one corner of the board and ask a question about just that part. That helps when a board gets big and you only care about one area, like the tasks for one person.

This is useful for any team that plans launches. Instead of a pile of sticky notes and a long chat thread, you end up with clear themes, a timeline, owners and dates. Then you can share it as a doc or deck without rewriting anything.

05Claude Sheets: Describe a Spreadsheet and Get It Built

Sheets is also in beta. You describe the spreadsheet you want, and Claude builds it with tabs, formulas, formatting and drop-downs.

Julian's example is for a link building agency. You ask Claude to build a tracker with three tabs:

  • A tab for prospects.
  • A tab for outreach status.
  • A tab for placed links.

Claude builds it, then explains each change it makes to a cell. That way you know what every formula does, even if you are not a spreadsheet expert.

Here is how to use it from start to finish:

  1. Describe the tracker and the tabs you need.
  2. Let Claude build it with formulas, formatting and drop-downs.
  3. Read its explanation of each change.
  4. Share the sheet so your team can edit it together.
  5. When you are done, export it to Excel or CSV.

The export option matters. You are not stuck inside Claude, so the sheet can move into the tools your team already uses.

06Claude Data: Live Dashboards From Your Business Data

Data used to be called dashboards. It is now generally available, which means it is out of beta.

You connect a data source, like a data warehouse or your CRM. Then Claude answers questions about that data and builds live dashboards from it.

Julian's example is a course owner with a community. They connect their member data and ask questions about it. Here is what they get back:

  • Charts that update as the data changes.
  • Certified metric definitions, so everyone on the team reads the numbers the same way.
  • Data stories you can review before you share them.

The certified metric definitions solve a common problem. When two people define the same number in different ways, reports stop matching and nobody trusts them. Locking the definitions keeps everyone on the same page.

The review step matters too. You see the data story first, check it, and only then share it with your team or clients. For anyone who spends hours building reports by hand, this turns a question into a chart in one step.

07Claude Meetings and Interactive Connectors

Meetings is rolling out in beta for team plans, starting with Google Meet. Claude joins the call, takes notes, and starts updating your docs while people are still talking.

Julian's example is an AI automation agency on a client call. Every action item lands in the task doc before you hang up. After each call, ask Claude to:

  1. List the decisions.
  2. List the owners.
  3. List the deadlines.
  4. Update the project page.

Interactive connectors are the sixth feature, and Julian calls this the big one. Apps now open inside Claude, either beside the chat or full screen.

His example is an e-commerce store. You open your design tool inside Claude and ask for the new banner sizes. Everything happens in one window, with no tab hopping.

  • Meetings capture what was said.
  • Connectors let Claude act inside the apps you already use.

Together, these two cut out a lot of copying and pasting between tools after calls and during design work.

08How the Claude New Features Work Together

Each feature is useful alone, but Julian's point is that they fit together into one system. Put the six together and you have a back office that works while you talk.

  • Fable thinks. It holds a whole client folder and works through big jobs.
  • Whiteboards plan. Notes become themes and a launch timeline.
  • Sheets organize. Trackers get built with formulas and drop-downs.
  • Data reports. Live dashboards answer questions.
  • Meetings capture. Decisions and owners land in your docs.
  • Connectors act. Your apps open inside Claude.

Some tips before you start:

  • Whiteboards, Sheets and Meetings are in beta, and Meetings is rolling out for team plans first.
  • Test Fable 5.2 on a real job with the same prompt before you switch models.
  • Always check how many of a model's findings are real, not just how many it lists.

These features suit agencies, online stores and course owners who are tired of messy systems spread across many tools.