AI is becoming the new front door to search, shopping, browsing and decision-making, raising urgent questions about trust, choice and who controls what we see online.
PC makers should focus on outmaneuvering direct competitors, prioritizing build quality and design aesthetics over chasing the absolute lowest prices.
The Nintendo 64 turns 30 this year and 8BitDo is celebrating with some very blue peripherals.
While many enterprises have already begun integrating AI-generated images, visuals, graphics and videos into their production workflows — there is also a growing pool of data and subjective commentary indicating AI imagery ultimately looks non-distinct, monotonous, and too unoriginal to ensure a brand and its assets stand out from the pack. That it’s “AI slop,” in other words.
AI creative tools startup Krea is hoping to change that trend by opening up the weights to its new frontier AI image model Krea 2 as two versions, “Krea 2 Raw” and “Krea 2 Turbo,” under a custom license that requires firms with more than 50 seats to pay for Enterprise usage, and mandates all users of any size to implement technical safeguards to prevent the generation of illegal materials, non-consensual intimate imagery (NCII), child sexual abuse material (CSAM), or defamatory assets.
Both models are available for public download on Hugging Face. The company says the models provide more visual variety than typical AI generators, while maintaining high prompt accuracy, fidelity, and quality. Importantly, they also offer enterprises and users the ability to customize the generative outputs much more than typical proprietary or even other open source models.
And, for those seeking to generate imagery at high-throughput, Krea 2 Turbo’s generation speed is only 2 seconds, making it among the fastest now available across open and proprietary AI image generation models.
|
Model / Generator |
Developer / Platform |
Avg. Generation Time |
Licensing & Commercial Use |
Key Characteristics |
|
FLUX.1 [schnell] (fast) |
Prodia |
0.5 seconds |
Open Weights (Apache 2.0). Fully permissive for free commercial use. |
Highly optimized endpoint utilizing step distillation to deliver sub-second generation times, representing the absolute floor for current API latency. |
|
Z-Image Turbo |
Replicate / fal.ai |
1.8 seconds |
Proprietary. Commercial rights require active API usage contracts. |
Designed for instantaneous inference bursts. Both Replicate and fal.ai achieve identical 1.8-second median times on this model. |
|
Krea 2 Turbo |
Krea |
2.0 seconds |
Open Weights / Proprietary Hybrid. Available via platform trial or API. |
Maintains the base model’s compatibility with style references and LoRAs while utilizing Trajectory Distribution Matching (TDM) to accelerate the creative ideation loop. |
|
Midjourney v8.1 (Turbo Mode) |
Midjourney |
3 – 6 seconds |
Proprietary. Commercial use requires an active Standard, Pro, or Mega tier subscription. |
Delivers generation speeds “three times faster than v8” while maintaining the model’s signature “painterly realism with sophisticated lighting,” though it requires a “higher credit cost”. |
|
FLUX.2 [klein] 4B |
Black Forest Labs |
3.9 seconds |
Open Weights. Permissive commercial use. |
The lightweight 4-billion parameter variant of the FLUX.2 architecture, balancing prompt adherence with high-speed generation. |
|
FLUX.2 [klein] 9B |
Black Forest Labs |
4.6 seconds |
Open Weights. Permissive commercial use. |
The medium-weight 9-billion parameter open model. It scales up compositional intelligence while keeping generation firmly under the 5-second barrier. |
|
MAI Image 2 Efficient |
Microsoft |
4 – 7 seconds |
Proprietary. Commercial use requires consumption-based API billing via Azure AI Foundry. |
A throughput-optimized variant explicitly designed to “out-pace Google’s Imagen Flash”. It makes a slight trade-off in detail for “substantially lower latency” that suits “automated pipelines” perfectly. |
|
Midjourney v8.1 (Fast Mode) |
Midjourney |
5 – 9 seconds |
Proprietary. Commercial use requires an active Standard, Pro, or Mega tier subscription. |
The standard operational mode for v8.1. Average wait times “consistently lands below 10 seconds for most prompts” while offering “excellent handling of complex multi-element scenes”. |
|
FLUX.2 [dev] |
fal.ai / DeepInfra |
6.1 – 6.4 seconds |
Open Weights (Non-Commercial). Strictly for research and non-commercial development. |
The developer-focused research model. API endpoint optimizations cause slight variance, with fal.ai operating at 6.1 seconds and DeepInfra at 6.4 seconds. |
|
Midjourney v8.1 (Relax Mode) |
Midjourney |
8 – 14 seconds |
Proprietary. Commercial use requires an active Standard, Pro, or Mega tier subscription. |
Processes standard 1024×1024 resolution images without consuming fast GPU hours. The model retains “strong compositional instincts” and “consistent color grading and mood”. |
|
FLUX.2 [pro] |
Black Forest Labs |
11.1 seconds |
Proprietary. Commercial rights require paid API consumption. |
The closed, professional-grade tier. It drops extreme step-distillation to prioritize high-fidelity commercial rendering and strict spatial alignments. |
|
Seedream 4.0 |
BytePlus |
11.6 seconds |
Proprietary. Commercial use via BytePlus enterprise contracts. |
The base commercial generation model for the Seedream architecture, focused on reliable, standard-resolution outputs. |
|
MAI Image 2 Standard |
Microsoft |
12 – 20 seconds |
Proprietary. Commercial use requires consumption-based API billing via Azure AI Foundry. |
Operates as a “full-quality output optimized for photorealism”. It acts as a literal renderer, delivering “high-fidelity skin tones and material textures” and “strong literal prompt adherence”. |
|
Nano Banana Pro (Gemini 3 Pro Image) |
Google DeepMind |
17.7 seconds |
Proprietary. Commercial rights granted via Gemini API terms. |
Prioritizes exact semantic accuracy and prompt adherence through an extended reasoning phase, trading raw speed for complex contextual execution. |
|
Seedream 4.5 |
BytePlus |
18.2 seconds |
Proprietary. Commercial use via BytePlus enterprise contracts. |
The upgraded high-fidelity variant, requiring an additional 6.6 seconds of compute time over the 4.0 version to refine complex textures and text rendering. |
|
Krea 2 Large |
Krea |
23.7 seconds |
Proprietary / Open Weights. Commercial rights depend on deployment. |
The un-distilled foundation model. It ignores the speed-focused Trajectory Distribution Matching of the Turbo variant to maximize aesthetic polish and structural stability. |
|
FLUX.2 [max] |
Black Forest Labs |
25.6 seconds |
Proprietary. Closed enterprise API. |
The heaviest parameter model in the FLUX lineup. It operates exclusively as a deep reasoning renderer for complex commercial assets. |
|
GPT-Image-2 |
OpenAI |
200.8 seconds |
Proprietary. Full commercial usage under standard OpenAI terms. |
A massive outlier in the latency landscape. It dedicates over three minutes to complex, multi-step semantic reasoning, likely utilizing an expansive chain-of-thought process prior to finalizing pixel outputs. |
Sources: Artificial Analysis, Krea, MindStudio.AI
At the technical core of the release sits an architectural framework built entirely from scratch: a Diffusion Transformer scaled to 12 billion parameters.
Rather than deploying a single, heavily fine-tuned model for all downstream tasks, Krea open-sources two highly differentiated checkpoints captured at distinct milestones of the model’s training lifecycle.
Departing from multi-stream configurations for structural clarity, the core engine standardizes on a single-stream transformer block architecture wherein attention and MLP layers are shared natively between text and image tokens.
To maximize computational efficiency, Krea incorporates a SwiGLU MLP layer operating at a 4x expansion factor alongside Grouped-Query Attention (GQA) combined with gated sigmoid attention layers to stabilize training dynamics.
Timestep conditioning is heavily optimized; the network replaces traditional per-block MLP modules with a lightweight, per-block tunable bias term, successfully cutting total block modulation parameters by 20% to 30% and reallocating that parameter budget directly into core layers.
Positional encoding is managed via a 3D Axial Rotary Position Embedding (RoPE) scheme mapping across individual frame, height, and width coordinate
Krea 2 Raw represents an undistilled base release checkpoint taken directly from the mid-training stage of the larger Krea 2 Medium development cycle.
Because it lacks post-training alignment, reinforcement learning from human feedback (RLHF), or final aesthetic distillation, Krea 2 Raw functions as a blank canvas.
It retains a vast, uncurated latent space that makes it poorly suited for immediate out-of-the-box prompting, but highly optimized for structural training.
Operating this model via the Hugging Face `diffusers` library requires a heavy compute footprint, executing via `Krea2Pipeline` in `torch.bfloat16` precision across 52 inference steps with a guidance scale of 3.5.
To accelerate early-stage architectural convergence during the first epoch of this 256px baseline training phase, Krea applied internal Representation Alignment (iREPA) techniques before decoupling them to let the underlying model develop independent structural representations.
The second checkpoint, Krea 2 Turbo, represents the opposite end of the optimization spectrum.
It is a distilled, post-trained variant derived from Krea 2 Medium. Through knowledge distillation, the network’s complex multi-step generation sequence is compressed into an incredibly lean operational profile.
Krea 2 Turbo slashes the required generation cycle down to just 8 inference steps with a guidance scale of 0.0, enabling it to render native 2k resolution imagery on standard consumer-grade hardware in approximately 2 seconds.
The underlying latent representations for both models are optimized through the integration of the Qwen Image VAE and the FLUX 2 VAE to guarantee rapid convergence while maintaining high reconstruction fidelity.
The underlying dataset strategy for the Krea 2 family relies on a hybrid blend of publicly harvested data, third-party licensed image repositories, and highly curated synthetic datasets built via proprietary generation methods.
Prior to final training, Krea processed these collections through rigorous algorithmic filters designed to strip out duplicative frames, low-resolution media, and explicit or harmful material, ensuring high fidelity and strong prompt compliance across both models.
Krea enforces a zero-synthetic data policy within its primary pretraining mix.
To prevent the upper-bound quality limitations and output biases induced by AI-generated data, the engineering team deployed custom in-house filtering classifiers built on top of DINOv3 and SigLIP-2 architectures to completely purge synthetic images at scale.
Furthermore, rather than using traditional model-based aesthetic filters that inadvertently strip away artistic intents like motion blur, Krea preserves wide stylistic boundaries.
The team trained a Sparse Autoencoder (SAE) on SigLIP-2 embeddings to isolate and filter out genuine visual artifacts using an unsupervised tagging framework.
The release establishes a highly deliberate operational paradigm for professional studios and independent creators: “train on Raw, generate with Turbo.” This workflow leverages the unique architectural properties of both open-weight files to optimize both training accuracy and rendering speed.
In creative production pipelines, engineers can use Krea 2 Raw to train custom Low-Rank Adaptations (LoRAs) or domain-specific fine-tunes.
Because the Raw checkpoint contains no baked-in stylistic opinions or aggressive post-training constraints, it absorbs unique aesthetic directions—such as architectural drafting styles, specific brand assets, or complex lighting designs—with high fidelity and zero stylistic interference.
Once the training phase is complete, creators can port those exact LoRAs directly over to Krea 2 Turbo.
This methodology is reflected in Krea’s own development ecosystem, which hosts an in-house collection of custom LoRAs trained entirely on the Raw foundation model but optimized for execution within Turbo workflows.
On the user-facing application layer, Krea integrates this dual-engine setup with a powerful style transfer system. Rather than relying on erratic text descriptions to achieve an artistic look, users can feed multiple style reference images directly into the system.
Krea 2 maps these references across its latent space, allowing creators to isolate individual aesthetic components, combine distinct moodboards, adjust style strength via generative sliders, and fine-tune batch variation levels to maintain visual cohesion across large-scale design iterations.
To address the gap between raw textual training captions and brief user inputs, Krea paired this suite with an advanced LLM Prompt Expander. Refined via Generalized Deep Q-Network Preference Optimization (GDPO) and trained on synthetic thinking traces to preserve intent reconstruction, the expander applies a photographic-medium bias to photorealistic requests and integrates an active DINOv3 embedding diversity score across rollout groups to prevent automated prompting routines from collapsing into a singular house style.
While Krea 2 Medium and Krea 2 Large remain the company’s flagship models for high-fidelity composition and absolute stylistic adherence, Turbo fills the critical role of rapid visual ideation.
It serves as an interactive scratchpad for early concept creation, quick prompt experimentation, and iterative art direction where near-instantaneous feedback loops are required to maintain creative momentum.
The open-weight assets deploy under the Krea 2 Community License Agreement operating alongside an official Acceptable Use Policy.
At a macro level, this legal framework mirrors recent industry trends toward commercial-use permissions that target small businesses while restricting large enterprise exploitation.
The license explicitly permits individuals, independent creators, and small commercial companies to build applications, monetize generated imagery, and integrate the open weights directly into commercial software products without royalty obligations.
Furthermore, Krea states that it “does not claim copyright or other intellectual property rights over content generated by users of this model,” leaving output ownership entirely in the hands of the operator.
For organizations scaling beyond this baseline, the ecosystem shifts into a paid, custom-tier structure.
While Krea’s official documentation lacks a rigid revenue threshold defining a “large enterprise,” the company structurally demarcates the boundary based on organizational footprint: standard commercial usage caps at a “Business” tier accommodating up to 50 seats.
Therefore, any entity requiring more than 50 seats, Single Sign-On (SSO) integrations, guaranteed Service Level Agreements (SLAs), or custom Data Processing Agreements (DPAs) qualifies as an Enterprise.
These larger entities fall outside the free Community License scope and must pay for a custom commercial license—operating under “Custom Terms of Service”—negotiated directly with Krea’s sales team.
Additionally, developer access to Krea’s official API remains entirely decoupled from the open-weights release; API usage operates as a distinct, paid service billed dynamically on a per-generation basis (measured in microdollars) and requires a prepaid USD balance independent of standard monthly compute subscriptions.
However, a close examination reveals a significant structural shift regarding legal and behavioral compliance for all self-hosted deployments.
Unlike traditional open-source permissions like the MIT or Apache 2.0 licenses—which grant unconditional usage rights and completely waive liability—the Krea 2 Community License implements strict downstream behavioral guardrails.
Because Krea relinquishes centralized control over the downstream deployment of its open weights, the contract legally binds deployers to enforce content moderation protocols at the infrastructure layer.
Under the terms of the agreement, any developer or platform hosting Krea 2 models must implement active input/output classifiers or equivalent content filtering mechanisms to actively prevent the generation of illegal materials, non-consensual intimate imagery (NCII), child sexual abuse material (CSAM), or defamatory assets.
Developers who fail to deploy these defensive safety layers stand in immediate breach of contract, giving Krea the explicit right to update model weights or revoke access to the model family entirely.
Founded in 2022 by audiovisual systems engineering dropouts Víctor Perez and Diego Rodriguez Prado, San Francisco-based Krea initially captured market traction as a highly fluid user interface layer built to orchestrate disparate, third-party AI generative engines.
The startup’s rapid scaling via product-led adoption culminated in an aggregate $83 million in disclosed venture capital funding from major VCs including Andreessen Horowitz and Bain Capital Ventures, as well as early-stage institutional backers including Pebblebed, Abstract Ventures, and Gradient Ventures.
The company’s user base surpassed 30 million individuals across 191 countries as of June 2026, according to its website.
The open-weights launch of the Krea 2 model family represents the culmination of Krea’s deliberate evolution from a multi-model SaaS aggregator into a self-sustaining media research lab.
Early in its lifecycle, Krea focused on building workflow tools, editing systems, and a node-based automation pipeline that allowed digital artists to unify models from competitors like Runway, Midjourney, and Adobe under a single subscription.
However, to insulate itself against upstream platform dependencies and supplier margin pressures, the company aggressively shifted toward developing proprietary architectures. This transition began taking public shape in July 2025 with the open-weights release of the custom-curated FLUX.1 Krea checkpoint, followed in October 2025 by Krea Realtime 14B—an autoregressive video model distilled from Wan 2.1 capable of rendering 11 frames per second on localized enterprise hardware.
This underlying technical maturation parallels Krea’s accelerating push into high-end enterprise workflows. Large-scale creative production operations have shifted toward treating Krea as core creative infrastructure; for example, the digital creative services platform
Superside reported migrating workflows from fragmented open-source setups to route roughly 80 percent of its total AI generative production through Krea.
Furthermore, Krea established a strategic co-development partnership with Copenhagen-headquartered architecture firm Henning Larsen to build highly restricted, domain-specific design tools tuned to meet the compliance frameworks mandated by the EU AI Act.
By releasing Krea 2 Raw and Turbo as open weights, Krea is continuing its expansion from an AI tools provider to being a model provider in its own right.
Creators are focusing heavily on the structural freedom offered by the unaligned Raw checkpoint, viewing it as an important alternative to the locked-down APIs provided by closed-source models.
Through the official announcement on X, Krea emphasized the foundational shift this launch represents for open AI workflows.
Developers note that by treating AI as an “actual creative medium” that feels “raw, flexible, unopinionated, and unconstrained,” Krea is intentionally providing an infrastructure that creators can “break if [they] want to,” moving far away from the rigid safety guardrails that frequently limit the visual range of competing enterprise tools.
As independent model builders begin compiling the Hugging Face repositories, the practical value of the release will be determined by how effectively the open-source community can scale customized LoRAs using Krea 2 Raw.
By providing clear commercial terms and lowering hardware entry barriers via Turbo’s 8-step inference pipeline, Krea has introduced a highly competitive alternative to the open-weights market, challenging dominant models by prioritizing artistic control over centralized corporate alignment.
When will the first folding iPhone arrive? A new report says earlier suggestions of delays may have been exaggerated.
Foundational web development practices still shape how websites and web applications perform, protect users and hold up when real-world conditions aren’t ideal.
Google Photos code uncovers eight new adaptive ‘Moods’ filters and a revamped Video Remix tool.
After a European launch last month, the portable aircon device is now available for pre-order in the U.S., and at a lower price than predicted.
Anthropic on Tuesday launched Claude Tag, a new product that embeds its most advanced AI model directly inside Slack as a persistent, shared teammate that anyone on a team can delegate work to by simply typing @Claude.
The product, available today in beta for Claude Enterprise and Team customers, replaces Anthropic’s existing Claude in Slack app and represents the company’s most aggressive move yet to colonize the enterprise collaboration layer — the place where decisions get made, work gets assigned, and institutional knowledge accumulates in real time.
For enterprise technology leaders who have spent the past two years evaluating where AI fits into their operational stack, Claude Tag reframes the question entirely. This is not a chatbot, a coding assistant, or a search tool bolted onto a messaging platform. It is an AI agent designed to function as a standing member of a team — one that builds memory, takes initiative, works asynchronously, and interacts with every person in a channel rather than serving a single user. The implications for enterprise workflow, governance, and vendor strategy are significant.
Anthropic says 65% of its own product team’s code is now created by its internal version of Claude Tag, and the company runs internal support and data insight channels through the same system. The claim is striking: Anthropic is asserting that the majority of its own product engineering output already flows through the tool it just put in customers’ hands.
At its core, Claude Tag works like this: an administrator pairs it with a Slack workspace, grants it access to specific tools and data sources, sets spending limits, and defines which channels it can operate in. From that point on, any team member in those channels can tag @Claude with a request — write a pull request, pull sales numbers, run a data analysis — and Claude will break the task into stages, execute them using the tools it has access to, and respond in a Slack thread with the result. The product runs on Claude Opus 4.8, the model Anthropic released less than a month ago.
Four capabilities differentiate Claude Tag from its predecessors and from competing integrations. First, it is multiplayer. Within a given Slack channel, there is one Claude that interacts with everyone, not a separate instance per user. Anyone can see what it is working on, and anyone can pick up the conversation where the last person left off. This is a direct contrast to most existing AI integrations in Slack, which tend to operate as single-player tools.
Second, it learns over time. As Claude follows along with its channel, it accumulates context about the work happening there. Users do not need to re-explain projects from scratch. If granted permission, Claude can also pull context from other Slack channels and data sources, though Anthropic says it will not report from private channels. Third, it takes initiative. With ambient behavior enabled, Claude will proactively surface relevant information from across the channels it monitors and the tools it is connected to, and will follow up on threads or tasks that have gone quiet without resolution. This is a notable expansion of agency: Claude is not just responding to requests but monitoring the information environment and deciding what its human teammates need to know. Fourth, it works asynchronously, pursuing projects autonomously over hours or days. Anthropic says its own teams “now spend much more of our time delegating tasks to many Claudes in parallel.”
Anthropic has designed the system with enterprise-grade isolation at its center. System administrators define separate Claude identities for different uses, scoped to specific channels with specific tools and data access. Everything, including Claude’s accumulated memories, stays within those boundaries. A Claude configured for sales work will not share memories or data access with one configured for engineering.
Administrators can set token-spend limits at both the organizational and channel level, and can review a complete log of every action Claude has taken and which user requested each task. For organizations managing compliance, audit, or regulatory requirements, this logging and scoping architecture is table stakes — and its absence has been a dealbreaker for many enterprises evaluating AI collaboration tools over the past year.
Migration from the existing Claude in Slack app requires an administrator opt-in within 30 days, and Anthropic says it is issuing introductory launch credits to eligible Enterprise and Team organizations. The four-step setup process — pair with Slack, connect tools, set spend limits, test in a private channel — is designed to reduce friction for IT teams already managing sprawling SaaS portfolios.
Claude Tag arrives in the middle of what has become the most fiercely contested territory in enterprise AI: the Slack channel. Slack itself has been aggressively positioning the platform as an “agentic operating system,” and the major AI players have responded by racing to plant their flags.
Salesforce, which acquired Slack for $27.7 billion in 2021, announced more than 30 new capabilities for Slackbot in March — the most sweeping overhaul of the platform since the acquisition — transforming it from a simple conversational assistant into a full-spectrum enterprise agent. OpenAI introduced “Workspace Agents” in April, allowing enterprise subscribers to design agents that take on work tasks across third-party apps including Slack, Google Drive, Microsoft apps, Salesforce, and Notion. Perplexity launched its enterprise “Computer” agent with direct Slack integration, letting employees query @computer directly inside Slack channels. Cognition’s Devin, the autonomous AI software engineer, has been built around Slack as a primary interface since its early days. Even Microsoft has brought GitHub Copilot into Teams.
The logic driving this convergence is straightforward: the average enterprise juggles over 1,000 applications, and employees waste countless hours on context switching, draining productivity by up to 40%. Whichever AI system becomes the default presence in the communication layer where work is coordinated gains an enormous distribution advantage — and, critically, an enormous data advantage. The AI that lives in the channel where work happens absorbs the institutional context that makes it increasingly difficult to replace.
To understand Claude Tag’s strategic significance, it helps to trace the product arc that led to it. Anthropic first integrated Claude with Slack in October 2025, offering two-way connectivity: users could invoke Claude from within Slack or connect Slack as a data source for Claude’s chatbot. The initial integration was focused on individual productivity — direct messages, AI assistant panels, and thread participation. In January 2026, Anthropic expanded Claude’s Slack presence when it launched interactive Claude apps, which included workplace tools like Slack, Canva, Figma, Box, and Clay.
In parallel, Anthropic was building out its enterprise infrastructure stack. In August 2025, the company bundled Claude Code into enterprise plans, a move its product lead Scott White called “the most requested feature from our business team and enterprise customers.” In April 2026, Anthropic launched Claude Managed Agents, a suite of composable APIs for building and deploying cloud-hosted AI agents at scale, with early adopters including Notion, Rakuten, Asana, and Sentry.
Then came Claude Opus 4.8 in late May, which Anthropic described as “a more effective collaborator” with “sharper judgement, more honesty about its progress, and the ability to work independently for longer than its predecessors.” Benchmark improvements included a jump in agentic coding scores from 64.3% to 69.2% and a knowledge work score increase from 1753 to 1890. Claude Tag is the synthesis of all of these threads — combining the Slack channel presence, the enterprise security architecture, the Managed Agents infrastructure, and the Opus 4.8 model’s improved agentic capabilities into a single product that Anthropic frames as “the beginning of an evolution of Claude Code.”
The financial stakes behind this launch are enormous. Anthropic raised $65 billion in Series H funding in late May at a $965 billion post-money valuation, and its run-rate revenue crossed $47 billion earlier this month. Claude Code’s run-rate revenue alone has grown to over $2.5 billion, more than doubling since the beginning of 2026, and enterprise use has grown to represent over half of all Claude Code revenue.
Those numbers explain why Anthropic is investing so heavily in channel-level presence. Every enterprise customer who grants Claude persistent access to a Slack channel — with connected tools, accumulated context, and ambient monitoring enabled — represents a dramatically deeper integration than a chatbot conversation or an API call. The usage patterns become stickier, the token consumption grows, and the switching costs rise. Deloitte’s deployment of Claude across more than 470,000 employees in 150 countries — reportedly its largest-ever enterprise AI deployment — illustrates the scale at which these dynamics play out.
The broader market trajectory reinforces the bet. Fortune Business Insights projects the global agentic AI market will grow from $9.14 billion in 2026 to $139 billion by 2034, and Gartner forecasts that 40% of enterprise applications will feature task-specific AI agents by 2026, up from less than 5% in 2025. Anthropic is not alone in seeing this future, but with Claude Tag it is making one of the most direct plays yet to own the enterprise agent layer.
Claude Tag raises several questions that enterprise buyers will need to evaluate carefully. The first is vendor dependency. As VentureBeat reported when analyzing Claude Managed Agents earlier this year, once an organization’s agents, operational configurations, and monitoring run on Anthropic’s managed infrastructure, switching costs increase significantly. Claude Tag deepens this dynamic: a Claude that has accumulated months of channel context and institutional memory becomes very difficult to replace. Enterprise procurement teams accustomed to negotiating multi-cloud flexibility will need to think hard about what it means to give a single vendor’s AI persistent access to the communication layer where institutional knowledge lives.
The second is governance around ambient monitoring. The proactive behavior mode — in which Claude monitors channels and surfaces information it decides is relevant — represents a meaningful expansion of what enterprise AI systems do. Organizations will need to develop clear frameworks for an AI agent that is not just responding to requests but actively surveilling information flows and making editorial judgments about what humans need to know. For regulated industries, this raises questions that existing AI governance policies may not yet address.
The third is pricing. Anthropic has not published detailed pricing for Claude Tag beyond noting that it runs on token-based spending with administrative controls. For an agent that monitors channels continuously, builds memory, and works asynchronously over hours or days, the token consumption profile could look very different from traditional AI usage. And the fourth is reliability: Anthropic has been candid in recent months about infrastructure strain caused by surging demand, and for a product positioned as an always-on team member, downtime carries a different kind of cost than it does for a tool invoked on demand.
Anthropic says its goal is to expand Claude Tag beyond Slack “so that teams can tag @Claude in the many other places they work.” The company is clearly eyeing the full collaboration surface — Microsoft Teams, email, project management tools, and beyond. If Claude Tag succeeds, it will validate a model of enterprise AI that looks less like a tool and more like a new category of worker: one that never sleeps, never forgets what was discussed in the channel last Tuesday, and never needs to be onboarded twice.
But the deeper significance of this launch may be what it reveals about the competitive dynamics reshaping enterprise software. For decades, the most valuable real estate in business technology was the system of record — the database, the CRM, the ERP. The current AI arms race suggests that the next era of enterprise value will be captured not by the system that stores the data, but by the agent that sits in the room where the work happens and understands what to do with it. Anthropic just gave that agent a name, a permanent seat in the channel, and permission to speak up when it thinks it has something to say. The question for every enterprise technology leader is no longer whether that agent will arrive. It is whether they are ready to manage it when it does.
The update isn’t just restricted to its 2026 models, either.