TL;DR — Claude's Office add-ins now share conversation state across Excel and PowerPoint, Claude responses render charts and diagrams inline instead of punting them to an artifact panel, and Shopify product discount Functions gained a native
prerequisitesblock for BXGY. Three different surfaces, the same shape of win: a platform primitive replaces code you had to write yourself.
The theme
This week's releases all took something developers or teams had been faking and made it a first-class feature. The Office add-ins stopped pretending Excel and PowerPoint were two separate conversations. Claude stopped shunting visualizations to a side panel that nobody wanted. Shopify stopped making Functions authors reimplement prerequisite logic inside their input queries and then discover, a month later, that the cart UI silently misrepresented the state.
The through-line is that the right place to solve these problems was always the platform. Whenever you find yourself writing orchestration code to stitch together things the vendor could just expose as a primitive, you are filing a feature request by hand. When that feature finally ships, the win is rarely the headline capability. It is the custom code you get to delete and the class of bugs that disappears with it. This week that meant deleting account-to-account context stitching, deleting screenshot-to-deck workflows, and deleting a whole category of Rust that lived in Functions only because the discount engine could not see what the function already knew.
1. Claude Now Shares Context Across Excel and PowerPoint (original)
Overview
On March 11 Anthropic shipped three things to the Claude Excel and Claude PowerPoint add-ins in one release: conversation context now flows between the two apps, skills run inside the add-ins, and the add-ins speak to LLM gateways — Amazon Bedrock, Google Vertex AI, and Microsoft Foundry. Any one of those would be worth a line in the changelog. Bundled together, they say the Office surface is now a serious enterprise integration point, not an experiment tucked into a corner of the product. If your finance team works in Excel and your strategy team works in PowerPoint, the two tools are finally one conversation.
Technical
The cross-app context is the piece that changes daily work. Previously each add-in held its own thread, so an hour of financial modeling in Excel meant nothing when you opened PowerPoint to draft the board deck about that model. The new surface keys state to your account plus the document set you are on, so the PowerPoint pane sees what Excel just did. "Draft a slide about the Q1 forecast we built" now resolves.
Skills carry across the same boundary. The markdown skill files that shape Claude's behavior elsewhere now load inside the add-ins, sandboxed to the add-in surface by default. A finance team's FP&A skill — chart of accounts, fiscal-year labels, currency formatting, reporting standards — applies in Excel and follows you into PowerPoint. One skill, two apps, consistent voice. I ran a full workflow through this: raw sales data to cleaned model to forecast in Excel, then a six-slide board deck in PowerPoint generated from the same conversation. The fiscal-year naming and currency formats carried over without me restating them.
Gateway support is the enterprise unblock. Large orgs route LLM traffic through Bedrock, Vertex, or Foundry for billing, audit, content filtering, and data residency. Until this release the add-ins only authenticated directly against Anthropic's API, which made them unusable anywhere procurement had drawn a gateway line. Now an admin configures the routing at the org level and the add-ins flow through the gateway. A few hard rules: both add-ins have to be signed in with the same account (mixing personal and corp accounts splits the context), skills do not bleed into Claude Desktop or web unless you install them there too, and gateway routing is an admin setting, not a user toggle.
Takeaway
If your team lives in Office and has only been using Claude through the web app, install both add-ins this week and wire up one shared skill for the team. The cross-app context plus skills combination is the workflow win. If you are at a gateway-only org, this is the release to take back to IT — the procurement story is clean now.
2. Claude Now Draws Interactive Charts and Diagrams Inline (original)
Overview
On March 12 Anthropic moved chart and diagram rendering out of the Artifacts side panel and into the message stream. Small in the changelog, large in practice. The old flow was: ask for a chart, Claude spawns an artifact in a side panel, you screenshot it or copy the SVG, you paste it where you actually need it. The new flow is: ask for a chart, the chart appears inline beneath the paragraph that prompted it, interactive and ready to share. For anyone who uses Claude as a thinking partner in meetings, this is the moment it stopped being a chat tool and started being a whiteboard.
Technical
The rendering substrate is still Artifacts — structured specs, client-side render — but the pipeline now emits into the conversation itself. No panel, no context switch, no "open in artifact view." Three behaviors fall out of that:
Multiple visualizations per response. The old one-artifact-per-reply limit forced Claude to either pick the single most important chart or pack several into a composite image. Inline rendering removes the ceiling: a single response can carry three charts, two Mermaid diagrams, and a data table, each placed beside the paragraph it belongs to.
Visualizations interleaved with prose. A funnel chart appears between the paragraph about top-of-funnel and the paragraph about conversion. You read, see the picture, read the next bit. That is how an analyst would present the same content in a deck, and it changes the cognitive feel of Claude's longer explanations.
Interactivity preserved. Hover a bar and see the value; click a legend entry to toggle a series. These are real widgets, the Plotly/Vega-Lite class of interaction, not screenshot-grade. The usual chart types — line, bar, area, scatter, pie, heatmap — are well supported. Exotic ones like sankey and treemap render but are less polished. Diagrams go through Mermaid, so flowcharts, sequence diagrams, ERDs, gantt charts, and state machines all work and look familiar if you already write Mermaid in your docs. Visualizations travel with the transcript on export and share, and the widgets ship with alt-text and keyboard navigation out of the gate — more accessibility than I expected from a v1.
A single prompt that now works: "Show me a sequence diagram of the OAuth handshake between our Next.js app, Auth0, and the GitHub provider, and below it draw a state machine of the session lifecycle." That gives you two diagrams in one reply, each inline, each correct, each pannable.
Takeaway
The next time you reach for diagrams.net, Excalidraw, or a screenshot tool, ask Claude first. Inline rendering made the friction lower than opening another app. If your team keeps a "how we use Claude" doc, add this to it — the shape of a meeting changes when the AI in the room can draw on the wall without leaving the conversation.
3. Product Discount Functions Get BXGY Prerequisites in 2026-04 (original)
Overview
Buy X Get Y is the discount every merchant wants and every Functions author dreads. Until Shopify's 2026-04 API release, the only way to express "spend $50 on shirts, get 20% off socks" inside a product discount Function was to inspect the cart in your input query, evaluate the prerequisite yourself, and conditionally emit a target. That worked for the happy path and broke everywhere else. The discount engine never learned the prerequisite existed, so when a buyer removed the qualifying shirt the discount silently disappeared on the next cart render with no explanation. Buyers got confused. Merchants opened tickets. 2026-04 fixes this by letting the function declare prerequisites alongside its targets, and the platform takes over tracking and re-evaluation.
Technical
purchase.product-discount.run now returns a prerequisites array on each Discount, with four prerequisite types: ProductVariantQuantityPrerequisite, ProductCollectionQuantityPrerequisite, SubtotalPrerequisite, and CustomerSegmentPrerequisite. Your function emits the discount with its prerequisites and targets, and the platform decides whether to allocate value on every cart mutation. The function does not rerun when only the prerequisite state changes — Shopify just toggles allocation.
rust
output::Discount {
message: Some("Buy $50 in Tees, get 20% off Socks".to_string()),
prerequisites: vec![
output::Prerequisite::CollectionSubtotal(
output::CollectionSubtotalPrerequisite {
collection_id: "gid://shopify/Collection/55501".to_string(),
minimum_amount: "50.00".to_string(),
}
)
],
targets: sock_targets,
value: output::Value::Percentage(output::Percentage { value: "20".to_string() }),
}
The real unlock is the cart UI. Because the platform now knows the discount intent, it renders the standard "Add 1 more Tee to unlock" hint through the built-in discount validation mechanism. You get that hint for free; you do not have to ship a custom checkout UI extension to fake it. Your input query shrinks in the same move — the function only needs enough metadata to pick targets, since the platform handles prerequisite evaluation.
Two constraints worth noting. Prerequisites combine with AND, never OR. If you need OR semantics, emit two discounts and let discount_application_strategy: MAXIMUM pick the winner. And the prerequisite quantity counts every matching variant in the cart, including ones the function also targets — there is no built-in "qualifying line and discounted line must differ" switch, so filter your targets accordingly when the campaign requires it.
Takeaway
Inventory every product discount Function you run and find the places that gate allocation on cart contents. Wherever that logic lives in Rust or JS today, lift it into the new prerequisites block, pin the extension TOML to API 2026-04, redeploy, and test the cart UI with prerequisites unmet. The "Add more to unlock" hint is the win you have been writing custom checkout extensions to approximate. Keep your input query minimal — the platform is doing the work now.
Original sources
- Claude Now Shares Context Across Excel and PowerPoint — originally published 2026-03-11
- Claude Now Draws Interactive Charts and Diagrams Inline — originally published 2026-03-12
- Product Discount Functions Get BXGY Prerequisites in 2026-04 — originally published 2026-03-13
