By admin 
Slack, the ubiquitous workplace messaging platform owned by Salesforce, is boldly challenging the prevailing paradigm of individual AI coding interactions. Today, the company unveiled "Slack Code," a groundbreaking new product designed to seamlessly integrate AI coding agents directly into the fabric of team collaboration. This innovative offering embeds powerful AI tools, including Anthropic’s Claude Code, Cognition’s Devin, GitHub Copilot, and Vercel’s agent, into dedicated Slack channels. The fundamental premise is to transform the solitary act of coding with AI into a transparent, interactive, and collective endeavor where entire teams can actively observe, guide, review, and ultimately ship software together. Slack Code is accessible across all Slack plans, though users will require their own subscriptions or access to the partner AI agents they wish to utilize.
The core value proposition of Slack Code is deceptively simple yet profoundly impactful: currently, most engagements with AI coding agents occur in isolation, a private dialogue between a single developer and a single agent, invisible to the rest of the team. Slack Code aims to democratize this process, making it a "multiplayer" experience. When a user initiates a request by mentioning a coding agent within any Slack conversation, the agent dynamically creates a project-specific code channel. Within this dedicated space, the AI performs its tasks openly, providing full transparency through code diffs, live previews, and a continuously updated plan visible in dedicated tabs. Upon completion of the task, the channel is archived, leaving behind a comprehensive and searchable audit trail of the entire development process.
Rob Seaman, Slack’s interim CEO, articulated the strategic vision behind this launch during a press briefing, emphasizing a fundamental shift in how development bottlenecks are perceived. "One of the things I love about this is that code is no longer the bottleneck," Seaman stated. "Ideas, taste, judgment, craft – those are the things that are the bottleneck, and you’ve effectively extended the population that can contribute ideas, taste, judgment, and craft to anybody that exists in your Slack." This sentiment underscores Slack’s belief that by making AI coding capabilities accessible and transparent, the company can unlock a broader spectrum of human ingenuity and collaborative problem-solving, moving beyond the technical limitations of writing code to focus on the strategic and creative aspects of software development.
This launch represents a significant milestone for Slack, but its implications extend far beyond the platform itself, offering a revealing glimpse into the evolving landscape of enterprise AI. The burgeoning field of AI coding has, up to this point, largely been characterized by a focus on individual productivity gains, with developers working in isolation with tools like Claude Code or OpenAI’s Codex within the confines of a terminal window. Slack’s strategic bet is that the next evolutionary stage of AI in software development will be defined by those who can effectively orchestrate and manage the collaborative layer surrounding these powerful agents. This ambitious move comes at a critical juncture for its parent company, Salesforce, which is actively seeking to revitalize its narrative and demonstrate tangible value in the AI-driven market.
Slack Code Channels: Fostering Transparency in AI-Assisted Software Development
During an in-depth interview that also included executives from Cognition, Slack leaders elaborated on the operational workflow envisioned for Slack Code channels. This model departs from traditional pair programming, drawing parallels instead to the dynamic and collaborative environment of a newsroom.
Jeff Wang, president of new enterprise at Cognition, the creators of the Devin coding agent, provided a compelling live demonstration of this new workflow. He illustrated a scenario where a developer reports a malfunctioning feature in an engineering channel. Devin, upon acknowledging the report with an emoji, would then engage in the thread, investigate the issue, and proactively open a pull request. "It even knows the code owner, so you can see it tagged Theo into this as well," Wang explained, highlighting the agent’s contextual awareness. Crucially, Wang emphasized the operational environment of these agents: "Every time Devin is doing something like this, it does have its own computer. So here, it’s actually using Chrome and the DevTools to test if the feature is working correctly." This capability underscores the power of cloud-based agents to perform complex testing and debugging in isolated, controlled environments.
Following the initial investigation and proposed solution, the work seamlessly migrates into a dedicated code channel. This is where the "multiplayer" aspect truly shines. Any team member, regardless of their role – be it an engineer, product manager, or designer – can readily join the conversation, review the proposed changes, and offer input. Wang’s demonstration vividly portrayed this collaborative potential when a designer, mid-task, uploaded a Figma file into the channel. The AI agent, without missing a beat, incorporated the design element into its work. The agent concluded its task by submitting the code changes, accompanied by illustrative screenshots and a recorded demonstration validating the functionality of the fixed feature. This comprehensive verification loop is a cornerstone of Slack Code’s value proposition. Unlike agents operating solely on a developer’s local machine, cloud-based agents can generate an indisputable, auditable record confirming the accuracy and efficacy of their work. "Scaling things, auditing things, giving it to everybody – that is much easier with these cloud agents form factor than it is with local agents," Wang asserted, emphasizing the inherent advantages of a centralized, cloud-native approach.
The impact of Slack Code extends beyond dedicated code channels, encompassing a broader overhaul of how AI agents integrate into the Slack ecosystem. The platform is introducing AI agent Direct Messages (DMs) that function akin to conversations with a human colleague. A new "Agents" tab will serve as a central hub for all agent sessions, providing live status updates and a convenient stop button. Furthermore, an intuitive "Add to Slack" flow will empower teams to deploy agents from a wide array of platforms, including Lovable, n8n, OpenAI, LangChain, and Airtable, with minimal effort. This streamlined process automates OAuth and configuration steps, significantly reducing the technical hurdles associated with agent integration.
The Strategic Imperative: AI as a Catalyst for Human Judgment in Software Development
The underlying strategic rationale for Slack Code is rooted in the belief that artificial intelligence has fundamentally altered the economics of software development. Historically, the act of writing code was the most constrained, labor-intensive, and costly aspect of the development lifecycle. Slack’s leadership now contends that with AI’s advancements, code generation has become significantly more accessible and less expensive. Consequently, the bottleneck has shifted upstream, residing not in the ability to write code, but in the human capacity for judgment, creativity, and strategic decision-making.
"One of the things I love about this is that code is no longer the bottleneck," Rob Seaman reiterated during the press briefing. "Ideas, taste, judgment, craft – those are the things that are the bottleneck, and you’ve effectively extended the population that can contribute ideas, taste, judgment, and craft to anybody that exists in your Slack." This perspective positions AI agents not as replacements for human developers, but as powerful augmentations that democratize the ability to contribute to the software development process, fostering a more inclusive and innovative environment.
Cognition provided compelling internal data to substantiate claims of accelerated development velocity. "We’ve seen our internal merged PR count go up 10x in the last few months, versus our headcount has only gone up like 40 percent," Wang reported. He described a workflow where engineers can initiate a Devin task, seamlessly transition to another assignment, and then launch another agent, leading to a situation where "soon you have everybody working on like dozens of agents at a time." This highlights a dramatic increase in output without a proportional increase in human resources, driven by the parallel processing capabilities of AI agents.
The applicability of this model extends well beyond traditional engineering roles, as Wang pointed out. "Believe it or not, a lot of our bugs are reported by our sales team. They report it in Slack, and then someone who’s technical applies them to fix the bug." Seaman seized upon this example as a microcosm of the product’s overarching thesis: "So much of that stuff never even made its way to a product manager into a backlog because the communication vehicles weren’t there, the motivation wasn’t there, the knowledge that it could actually be fixed so quick wasn’t there – and we’ve effectively knocked all of that down." This illustrates how Slack Code can bridge communication gaps, foster proactive problem-solving, and accelerate the resolution of issues that might otherwise languish in traditional development pipelines.
Wang further elaborated on the future trajectory of AI in software development, predicting a significant reduction in what he termed "toil work" – repetitive, often undesirable tasks such as fixing bugs, maintaining CI/CD pipelines, or addressing security vulnerabilities. "Toil work – fixing bugs, fixing CI/CD, or fixing vulnerabilities, all these things engineers probably don’t want to do – we think will be automated away," he stated. The focus, he believes, will increasingly shift to tasks that "requires creativity, planning, business logic." He offered a prediction that might raise eyebrows among some engineering leaders: while human oversight remains critical for every code merge today, "I suspect maybe in the next year it’s just going to go through automatically." This bold assertion suggests a future where AI agents, with sufficient validation and trust, could autonomously manage significant portions of the development lifecycle.
Addressing the "AI Slop" Concern: The Power of Transparency and Collaboration
A primary concern surrounding the democratization of software creation through AI is the potential for a deluge of "AI slop" – output that appears plausible but is fundamentally flawed or poorly conceived, generated at scale by users lacking deep technical expertise. Slack’s executives counter this apprehension by arguing that visibility, rather than exacerbating the problem, serves as a crucial antidote.
"The multiplayer part is a guard against that, actually, because people can see your work, people can comment on your work," explained Katie Steigman, Slack’s VP of product. She contrasted this with the current state of affairs: "If I’m doing God knows what in terminal with an agent, versus being able to do it in a place where people can see my intent and actually change and shape my work – or slap my hand and tell me that’s slop, because that’s real." This emphasis on collective oversight and immediate feedback aims to foster a culture of accountability and continuous improvement, ensuring that the output of AI agents is subject to human scrutiny and refinement.
Steigman, a product manager by background rather than an engineer, offered her own workflow as a template for this collaborative approach. "When I put PRs up as a product person, I almost always tag in an engineer from my team. I don’t just send a PR and ask for an approval," she said. "Almost every time, an engineer will say something like, ‘Come on, you can make that a little bit tighter,’ or they’ll actually give it some specific technical guidance, and the agent will take one more rev and produce code that has been touched by an engineer to a certain extent." This highlights how AI agents can act as conduits for cross-functional collaboration, enabling individuals from diverse roles to contribute to the code refinement process under the guidance of technical experts.
Seaman framed the argument in broader, more philosophical terms: "I think the moral arc of multiplayer AI bends towards higher quality and less duplication." He referenced Shopify, where CEO Tobi Lütke has reportedly advocated for confining agentic coding to public channels precisely because it "immediately disseminates every single thing that’s happening in the company" and promotes a level playing field. However, skepticism regarding the widespread adoption and efficacy of AI agents is not without empirical backing.
Gartner has projected that "more than 40 percent of agentic AI projects will be canceled by the end of 2027," citing escalating costs and a lack of clear business value as primary drivers. Similarly, McKinsey’s latest "State of AI" survey revealed that while a significant majority of organizations are experimenting with AI agents, only about a third have begun scaling these initiatives, and a mere 39 percent report any tangible bottom-line impact. This persistent gap between enthusiasm for AI agents and their demonstrated value remains a defining characteristic of the market into which Slack is launching its new product.
Security and Permissions: A Foundation of User-Centric Access Control
For enterprise clients, a critical design consideration within Slack Code revolves around its permissions model. When directly questioned about the potential for agents in code channels to inadvertently expose sensitive information across teams – for instance, making a finance repository accessible to the legal department – Seaman provided a firm assurance. He emphasized that AI agents inherit the precise permissions of the human user who initiates their invocation, and no more.
"Everything is done on behalf of the user, using the user’s ACLs, both in Slack and in the systems that they’re connecting to," Seaman stated emphatically. "There’s no god permissions or bot-level permissions… Within Slack, the agent has access to information that the user has access to, and access to the channels that it’s been added to." This user-centric approach to permissions is designed to maintain existing security protocols and prevent unauthorized access.
Steigman further clarified that when an agent initiates a code channel, "the only thing that agent gets from the code channel is the context of the conversation" that triggered its activation. On the execution front, Wang explained that Devin operates within isolated sandboxes, employing "minimum viable access" principles. This includes an optional mode that completely restricts internet access, mitigating potential security risks. "You’ve heard all these stories about the agent escaping and causing havoc," Wang acknowledged, "but we have different security configurations." This layered security approach aims to build trust and confidence among enterprise users concerned about the potential for AI agents to compromise data security.
This "agents as extensions of existing users" framework represents a significant differentiator compared to standalone agent platforms. Such platforms often necessitate IT departments to provision new service identities and manage a complex web of one-off permissions. Slack Code’s approach directly addresses the "shadow IT" concerns that have historically plagued agentic tools. By generating standard pull requests into platforms like GitHub, existing release gates and established review processes remain intact. "It reduces that barrier upfront to get that initial PR up," Steigman noted. "Then the due diligence still happens in GitHub." This integration ensures that the introduction of AI-assisted code generation does not bypass established governance and quality control mechanisms.
Salesforce’s AI Pivot: Slack Code as a Strategic Lever
The introduction of Slack Code arrives at a pivotal and somewhat turbulent moment for its parent company, Salesforce. The company’s stock experienced a notable decline, lagging behind broader market indices, as investors grappled with the potential implications of AI on traditional enterprise software demand. Adding to this period of flux, Slack’s former CEO, Denise Dresser, departed to take on a chief revenue officer role at OpenAI, prompting the elevation of Rob Seaman, previously Slack’s product chief, to the interim CEO position.
In response to these market pressures, Salesforce has strategically positioned Slack as the central gateway for AI-powered work. Earlier this year, the company launched a revamped Slackbot, powered by Anthropic’s Claude, which was reportedly the fastest-adopted feature in Salesforce’s 27-year history. Slack Code represents a strategic expansion of this initiative, moving beyond simple question-answering capabilities to facilitate the direct creation of tangible assets – not just messages, but functional code, prototypes, and documents generated within the Slack environment itself.
A notable strategic shift is evident in today’s announcement. In mid-2025, reports surfaced indicating that Salesforce had initially moved to restrict rival AI firms from accessing Slack data, a defensive maneuver aimed at protecting its proprietary information. Today’s announcement, however, signals a pronounced change in strategy. Slack is now actively positioning itself as an open platform, actively courting AI companies as partners. The company plans to open the APIs for code channels to all developers, signaling a commitment to fostering an ecosystem of AI-powered collaboration. Software engineering is presented as just the initial use case, with plans to extend this model to marketing campaigns and legal document reviews within dedicated agent channels. The calculus appears to have shifted from safeguarding Slack’s data to making the platform indispensable as the central venue where AI agents, regardless of their origin, perform their work.
Industry partners have voiced enthusiastic support for this new direction. Malte Ubl, Vercel’s CTO, commented, "A whole team can gather in one code channel, watch the agent work, steer it together, and ship a preview." Mario Rodriguez, GitHub’s chief product officer, echoed this sentiment, describing Slack as "a strategic part of a broader GitHub promise: humans set direction, agents close the loop." These endorsements highlight the perceived synergy between Slack’s collaborative platform and the evolving capabilities of AI agents.
The Future of AI Coding: A Hybrid Landscape of Collaboration and Solitude
While Slack is championing a more collaborative approach to AI coding, its executives are quick to emphasize that the traditional single-player terminal is not becoming obsolete. When asked about the potential obsolescence of tools like Claude Code and OpenAI’s Codex, Seaman projected a future characterized by a division of labor. "The overwhelming majority of the work is actually going to happen in these multiplayer environments," he stated. "But there’s going to be deep, immersive, intensive, single-player thought work that’s going to happen in terminals." This suggests a nuanced future where complex architectural redesigns might still benefit from the focused, head-down engagement of a developer with an agent in a terminal, while immediate bug fixes or feature flags can be handled efficiently within collaborative Slack channels.
Seaman posited that the adoption curve for these new collaborative AI workflows will mirror the trajectory of previous automation waves. "People are going to open these things at the beginning" – meticulously reviewing every code diff and every step of the AI’s thought process – "and then build trust in the system and open it less and less over time." This gradual acclimation and increasing reliance on the AI’s capabilities, once trust is established, is a predictable pattern in the adoption of transformative technologies.
This strategic wager extends beyond a mere product launch; it represents a fundamental rethinking of how work is structured and executed. McKinsey’s research consistently highlights that organizations achieving the most significant value from AI are those that fundamentally redesign their workflows around AI capabilities, rather than simply layering AI onto existing, outdated processes. Slack Code embodies this principle, packaging a workflow redesign as a feature and aiming to make the team, rather than the individual, the primary unit of AI adoption. If successful, Slack, a platform that revolutionized workplace communication, could fundamentally alter the landscape of software creation. Conversely, if the promise of transparency fails to translate into tangible quality improvements, the increased visibility might simply result in the collective observation of mounting "slop."
Irrespective of the ultimate outcome, the era of the solitary developer engaging in hushed conversations with an AI agent in a private tab appears to be drawing to a close. As Wang eloquently put it, "The bottlenecks have shifted." The critical question that Slack Code aims to answer is whether this collective, transparent approach will genuinely diminish those bottlenecks, or merely amplify the noise.
