Skip-Level

Anthropic Adds Claude Whiteboards Sheets and Data for Paid Plans

By ยท 11 Nov 2026

An IT manager, seen from behind, sits at a butter yellow desk and looks at a landscape monitor with five blank amber and cream tiles arranged in a plus shape, against a bright tangerine wall.
  • Anthropic launched Claude Whiteboards and Claude Sheets in beta on Nov 10, and made Claude Data generally available on paid plans, renaming it from Claude Dashboards.
  • On Team plans all three are on by default. On Enterprise plans, Whiteboards and Sheets stay off until an admin turns them on, and Claude Data turns on by default on November 19.
  • A Nov 6 Google Developers Blog post finds that stale TODO or FIXME bug comments showed up in 13% of file reading sessions, and that unprompted detours were associated with 70% more steps, 77% more tokens, and 105% more wait time.
  • According to CIO Dive's Oct 27 report on a Gartner survey of 251 executives at companies with more than $1 billion in revenue, 82% say CIOs should guide enterprise AI, while more than half of non tech executives see technology as informing strategy rather than shaping it.

Three things engineering and IT managers should know this Wednesday, from new collaboration surfaces inside Claude to the cost of stale comments once coding agents start reading them as work.

1. Anthropic Adds Claude Whiteboards Sheets and Data for Paid Plans

On Nov 10, Anthropic published a Claude product post launching Claude Whiteboards and Claude Sheets in beta, and making Claude Dashboards generally available under a new name, Claude Data. The post says Whiteboards is a shared board where a team brainstorms with Claude, Sheets is a spreadsheet Claude builds and edits with you, and Claude Data adds data stories, certified queries, and live sharing. All three are available on paid plans, and they work on web, desktop, and mobile. Claude Data needs a data connector, such as a warehouse or CRM. Certified queries and live sharing are still in beta even though Claude Data itself is generally available. With live sharing, colleagues can see up to date numbers on a shared dashboard even if they do not have access to the connectors, and they only see the results of queries an owner has approved.

The admin settings are the part that matters for rollout. On Team plans, all three are on by default. On Enterprise plans, Claude Whiteboards and Sheets are off by default, and Claude Data turns on by default on November 19, 2026. Admins can change those settings in the Artifacts section of Organization settings.

Why it matters: This is a collaboration and data access change, not just a new chat feature. Our read: decide now whether these surfaces should be on for your organization, who may share live dashboards, and how you will keep connectors and certified queries under review, especially before the Nov 19 Enterprise default for Claude Data. Source: Claude

2. Google Says Stale TODO Comments Pull Coding Agents Off Task

Google published Agent Distraction on its Developers Blog on Nov 6. The authors, Sam Saccone and Madhuri Garikapati, looked at traces across thousands of engineers and hundreds of millions of agent steps. They used inline TODO and FIXME comments that point at bug tickets as a proxy for stale instructions in the code. Of the millions of file reading sessions, 13% exposed the agent to those comments. In 6% of encounters the agent then took action aimed at that bug, and 83% of those actions were unprompted. Of the unprompted detours, 41% chased tickets that were already closed, and 57% involved bugs that were still open, which Google calls scope creep. After controlling for developer, codebase complexity, task type, and other factors, Google reports that unprompted detours were associated with 70% more steps, 77% more tokens, and 105% more wait time per session.

Google also built cleanup agents that removed thousands of obsolete references over six months, with more than 95% acceptance from human reviewers, and only after confirming that both the comment and its intent were obsolete. The post describes this leftover material as a tax on agents and says cleanup projects that were once deprioritized should be looked at again.

Why it matters: The figures come from Google's own traces and a regression, not a controlled experiment on your stack, and the comments they measured are specifically TODO or FIXME notes that point at bug tickets. Our read: stale comments are no longer harmless leftover text once agents treat them as work. Ask how many open TODO comments in your repos still point at closed tickets, and whether a cleanup pass is now worth scheduling. Source: Google Developers Blog

3. CIO Dive Reports the C Suite Still Split on Who Owns AI

This one is older, so the date matters. According to CIO Dive's Oct 27 report on a Gartner survey, the survey covered 251 technical and non technical executives at companies with more than $1 billion in revenue and was presented by Gartner senior principal analyst Jennifer Carter at the company's IT Symposium event. In that report, four fifths of CEOs view technology as the enterprise's business strategy, and 82% of executives surveyed say CIOs should be responsible for guiding enterprise AI initiatives. But more than half of executives in non tech roles said they view technology as informing business strategy, not shaping it. Only 54% of non technology executives said they have a strong partnership with their IT departments.

Why it matters: The survey measures views at large companies, not proof that CIO ownership produces better results. Our read: if you are being asked to lead enterprise AI, the gap to close is with non tech peers who still see technology as an input to strategy rather than part of it. A practical step is to brief those peers on one current AI initiative in business terms, and to write down who owns the outcome, not only who owns the tool. Source: CIO Dive

Compiled daily with Grok from public sources and edited by the AIDevPulse team.

Get Skip-Level and the daily brief in your inbox: sign up for the AIDevPulse newsletter. For today's developer news, read today's main brief.

Sources:

Recommended AI prompt

Copy this paragraph into ChatGPT, Claude, Gemini, Grok, or whatever AI you use.

Prompt

I manage an engineering or IT team. Using only the three items in this readout, help me draft a one page plan for the next month that does three things: recommends whether Claude Whiteboards, Claude Sheets, and Claude Data should be on for our plan type, including the Nov 19 Enterprise default for Claude Data and who may share live dashboards, outlines a cleanup pass for TODO or FIXME comments that still point at closed bug tickets and how we would measure whether agents are taking unprompted detours, and briefs my non tech peers on who owns enterprise AI, using the figures CIO Dive reported from the Gartner survey on CIO responsibility, strategy views, and IT partnership. Keep my team's context in mind: [describe your team's size, your Claude plan if you have one, and how you track comments in your repos]. Do not add facts that are not in the readout, and flag anything I should check before sharing.