Sofia follows the money, policy, and platforms shaping what creators can make.
Step-by-step guides on prompting, styles, and getting the most out of AI image generation.
Read the guidesPick a companion and get their take on this story
Slack is launching dedicated Code channels that let teams build software alongside AI agents in a single workspace — no more toggling between a chat tool, a code editor, and a separate AI interface.\n\n## Key takeaways\n\n- Slack Code is a new channel type inside Slack purpose-built for collaborative AI-assisted software development.\n- Each Code channel gets a dedicated user tab, open project-specific threads, and support for multiple AI agents working alongside human contributors.\n- Built-in features include code-change comparison views (diffs) and HTML output previews before a project ships.\n- The launch positions Slack as a direct competitor to standalone vibe-coding tools that require context-switching outside the team's existing communication layer.\n- Teams already using Slack avoid onboarding a separate tool; the tradeoff is dependence on Salesforce's platform roadmap for future AI coding capabilities.\n\n## What Slack Code actually ships\n\nAccording to The Verge, Slack Code channels are open, project-specific spaces where AI agents participate alongside humans rather than being invoked through one-off slash commands. The dedicated user tab keeps contributors — human and AI — organized in a single view, which addresses the fragmentation problem that plagues most team coding setups: the context lives in five different places and no one has the full picture.\n\nThe diff comparison feature is the more practically significant addition. Seeing exactly what an AI agent changed, line by line, inside the same channel where the change was requested closes a loop that most vibe-coding workflows leave open. Right now, a team member typically has to leave the conversation, open a separate editor, and manually inspect output. Slack Code makes that review step native to the channel.\n\nHTML previews before shipping are a smaller but real quality-of-life gain for anyone building web-facing projects — catching layout or rendering problems without a separate browser tab or staging environment.\n\n## The platform bet underneath the feature\n\nSalesforce, which owns Slack, is making a structural argument here: that the right place for AI-assisted development is inside the communication layer teams already use, not in a dedicated coding IDE or a standalone AI tool bolted on afterward. That argument has teeth when the alternative is constant context-switching, but it also means teams adopting Slack Code are betting that Salesforce will keep pace with dedicated coding-AI providers like Cursor, Replit, or GitHub Copilot Workspace — all of which have longer track records in the space.\n\nThe competitive pressure is real. When GitHub launched Copilot Workspace in 2024, it similarly tried to collapse the distance between conversation and code. Slack's edge, if it has one, is that the conversation is already happening there — the AI agents join an existing workflow rather than requiring teams to relocate to a new one.\n\n> "With Slack Code, when you have [a coding conversation], it stays in context with the rest of your work."\n>\n> — Slack, via The Verge\n\n## Relevance for AI-art and creative tooling workflows\n\nFor creators who build custom pipelines — ComfyUI workflows, API integrations, or automation scripts that feed into image generation — Slack Code is worth watching as an alternative to the current standard of dropping code snippets into a general chat channel and hoping someone (or an AI) catches the error. The diff view alone would meaningfully reduce the back-and-forth that happens when an AI-suggested script breaks a generation pipeline and no one can quickly see what changed.\n\nCreators already exploring AI-assisted tooling can find relevant technique breakdowns in Charmloop's guides and experiment with how those tools feed into image generation. The broader pattern — AI agents embedded directly into collaborative workspaces rather than running as separate applications — is the same trajectory reshaping image and video generation platforms, where the model increasingly lives inside the creative environment rather than outside it.\n\nSlack has not confirmed a specific general-availability date beyond the current launch announcement, so the pace at which Code channels reach all Slack tiers — and which AI agents will be supported beyond the initial set — remains the key variable to watch.
