Kilo Code, the open-source AI coding startup backed by GitLab cofounder Sid Sijbrandij, is launching a Slack integration that enables software program engineering groups to execute code modifications, debug points, and push pull requests instantly from their group chat — with out opening an IDE or switching functions.
The product, referred to as Kilo for Slack, arrives because the AI-assisted coding market heats up with multibillion-dollar acquisitions and funding rounds. However relatively than constructing one other siloed coding assistant, Kilo is making a calculated wager: that the way forward for AI improvement instruments lies not in locking engineers right into a single interface, however in embedding AI capabilities into the fragmented workflows the place choices really occur.
"Engineering groups don't make choices in IDE sidebars. They make them in Slack," Scott Breitenother, Kilo Code's co-founder and CEO, stated in an interview with VentureBeat. "The Slackbot means that you can do all this — and extra — with out leaving Slack."
The launch additionally marks a partnership with MiniMax, the Hong Kong-based AI firm that lately accomplished a profitable preliminary public providing. MiniMax's M2.1 mannequin will function the default mannequin powering Kilo for Slack — a choice the corporate frames as an announcement in regards to the closing hole between open-weight and proprietary frontier fashions.
How Kilo for Slack turns group conversations into pull requests with out leaving the chat
The combination operates on a easy premise: Slack threads typically comprise the context wanted to repair a bug or implement a function, however that context will get misplaced the second a developer switches to their code editor.
With Kilo for Slack, customers point out @Kilo in a Slack thread, and the bot reads all the dialog, accesses related GitHub repositories, and both solutions questions in regards to the codebase or creates a department and submits a pull request.
A typical interplay would possibly appear to be this: A product supervisor studies a bug in a Slack channel. Engineers talk about potential causes. As an alternative of somebody copying the dialog into their IDE and re-explaining the issue to an AI assistant, a developer merely varieties: "@Kilo based mostly on this thread, are you able to implement the repair for the null pointer exception within the Authentication service?"
The bot then spins up a cloud agent, reads the thread context, implements the repair, and pushes a pull request — all seen in Slack.
The corporate says all the course of eliminates the necessity to copy data between apps or soar between home windows — builders can set off advanced code modifications with nothing greater than a single message in Slack.
Why Kilo says Cursor and Claude Code fall quick when builders want multi-repo context
Kilo's launch explicitly positions the product in opposition to two main AI coding instruments: Cursor, which raised $2.3 billion at a $29.3 billion valuation in November, and Claude Code, Anthropic's agentic coding device.
Breitenother outlined particular limitations he sees in each merchandise' Slack capabilities.
"The Cursor Slack integration is configured on a single-repository foundation per workspace or channel," he stated. "In consequence, if a Slack thread references a number of repositories, customers have to manually change or reconfigure the mixing to tug in that further context."
On Anthropic's providing, he added: "Claude Code documentation for Slack reveals how Claude might be added to a workspace and reply to mentions utilizing the encompassing dialog context. Nevertheless, it doesn’t describe persistent, multi-turn thread state or task-level continuity throughout longer workflows. Every interplay is dealt with based mostly on the context included on the time of the immediate, relatively than sustaining an evolving execution state over time."
Kilo claims its integration works throughout a number of repositories concurrently, maintains conversational context throughout prolonged Slack threads, and allows handoffs between Slack, IDEs, cloud brokers, and the command-line interface.
Kilo picks a Chinese language AI firm's mannequin as its default—and addresses enterprise safety issues head-on
Maybe essentially the most provocative component of the announcement is Kilo's alternative of default mannequin. MiniMax is headquartered in Shanghai and lately went public in Hong Kong — a lineage which will elevate eyebrows amongst enterprise prospects cautious of sending proprietary code via Chinese language infrastructure.
Breitenother addressed the priority instantly: "MiniMax's current Hong Kong IPO drew backing from main world institutional traders, together with Baillie Gifford, ADIA, GIC, Mirae Asset, Aspex, and EastSpring. This speaks to robust world confidence in fashions constructed for world customers."
He emphasised that MiniMax fashions are hosted by main U.S.-compliant cloud suppliers. "MiniMax M2-series are world main open-source fashions, and are hosted by many U.S. compliant cloud suppliers akin to AWS Bedrock, Google Vertex and Microsoft AI Foundry," he stated. "In actual fact, MiniMax fashions had been featured by Matt Garman, the AWS CEO, throughout this 12 months's re:Invent keynote, displaying they're prepared for enterprise use at scale."
The corporate stresses that Kilo for Slack is basically model-agnostic. "Kilo doesn't power prospects into any single mannequin," Breitenother stated. "Enterprise prospects select which fashions they use, the place they're hosted, and what suits their safety, compliance, and danger necessities. Kilo gives entry to greater than 500 fashions, so groups can all the time select the proper mannequin for the job."
The choice to default to M2.1 displays Kilo's broader thesis in regards to the AI market. In accordance with the corporate, the efficiency hole between open-weight and proprietary fashions has narrowed from 8 p.c to 1.7 p.c on a number of key benchmarks. Breitenother clarified that this determine "refers to convergence between open and closed fashions as measured by the Stanford AI Index utilizing main basic benchmarks like HumanEval, MATH, and MMLU, to not any particular agentic coding analysis."
In third-party evaluations, M2.1 has carried out competitively. "In LMArena, an open platform for community-driven AI benchmarking, M2.1 achieved a number-four rating, proper after OpenAI, Anthropic, and Google," Breitenother famous. "What this reveals is that M2.1 competes with frontier fashions in real-world coding workflows, as judged instantly by builders."
What occurs to your code once you @point out an AI bot in Slack
For engineering groups evaluating the device, a essential query is what occurs to delicate code and conversations when routed via the mixing.
Breitenother walked via the info move: "When somebody mentions @Kilo in Slack, Kilo reads solely the content material of the Slack thread the place it's talked about, together with fundamental metadata wanted to grasp context. It doesn’t have blanket entry to a workspace. Entry is ruled by Slack's normal permission mannequin and the scopes the client approves throughout set up."
For repository entry, he added: "If the request requires code context, Kilo accesses solely the GitHub repositories the client has explicitly related. It doesn’t index unrelated repos. Permissions mirror the entry stage granted via GitHub, and Kilo can't see something the person or workspace hasn't licensed."
The corporate states that information isn’t used to coach fashions and that output visibility follows current Slack and GitHub permissions.
A very thorny query for any AI system that may push code on to repositories is safety. What prevents an AI-generated vulnerability from being merged into manufacturing?
"Nothing will get merged mechanically," Breitenother stated. "When the Kilo Slackbot opens a pull request from a Slack thread, it follows the identical guardrails groups already depend on at this time. The PR goes via current overview workflows and approval processes earlier than something reaches manufacturing."
He added that Kilo can mechanically run its built-in code overview function on AI-generated pull requests, "flagging potential points or safety issues earlier than it ever reaches a developer for overview."
The open-source paradox: why Kilo believes making a gift of its code received't kill the enterprise
Kilo Code sits in an more and more widespread however nonetheless tough place: the open-source firm charging for hosted companies. The entire IDE extension is open-source beneath an Apache 2.0 license, however Kilo for Slack is a paid, hosted product.
The plain query: What stops a well-funded competitor — or perhaps a buyer — from forking the code and constructing their very own model?
"Forking the code isn't what worries us, as a result of the code itself isn't the toughest half," Breitenother stated. "A competitor might fork the repository tomorrow. What they wouldn't get is the infrastructure that safely executes agentic workflows throughout Slack, GitHub, IDEs, and cloud brokers. The expertise we've constructed working this at scale throughout many groups and repositories. The belief, integrations, and enterprise-ready controls prospects count on out of the field."
He drew parallels to different profitable open-source firms: "Open core drives adoption and belief, whereas the hosted product delivers comfort, reliability, and ongoing innovation. Prospects aren't paying for entry to code. They're paying for a system that works day by day, securely, at scale."
Contained in the $29 billion "vibe coding" market that Kilo desires to disrupt
Kilo enters a market that has attracted extraordinary consideration and capital over the previous 12 months. The apply of utilizing giant language fashions to jot down and modify code — popularly often known as "vibe coding," a time period coined by OpenAI co-founder Andrej Karpathy in February 2025 — has develop into a central focus of enterprise AI funding.
Microsoft CEO Satya Nadella disclosed in April that AI-generated code now accounts for 30 p.c of Microsoft's codebase. Google acquired senior workers from AI coding startup Windsurf in a $2.4 billion transaction in July. Cursor's November funding spherical valued the corporate at $29.3 billion.
Kilo raised $8 million in seed funding in December 2025 from Breakers, Cota Capital, Basic Catalyst, Quiet Capital, and Tokyo Black. Sijbrandij, who stepped down as GitLab CEO in 2024 to deal with most cancers therapy however stays board chair, contributed early capital and stays concerned in day-to-day technique.
Requested about non-compete concerns given GitLab's personal AI investments, Breitenother was transient: "There aren’t any non-compete points. Kilo is constructing a basically totally different strategy to AI coding."
Notably, GitLab disclosed in a current SEC submitting that it paid Kilo $1,000 in alternate for a proper of first refusal for 10 enterprise days ought to the startup obtain an acquisition proposal earlier than August 2026.
When requested to call an enterprise buyer utilizing the Slack integration in manufacturing, Breitenother declined: "That's not one thing we are able to disclose."
How a 34-person startup plans to outmaneuver OpenAI and Anthropic in AI coding
Probably the most important menace to Kilo's place could come not from different startups however from the frontier AI labs themselves. OpenAI and Anthropic are each constructing deeper integrations for coding workflows, and each have vastly larger assets.
Breitenother argued that Kilo's benefit lies in its structure, not its mannequin efficiency.
"We don't assume the long-term moat in AI coding is uncooked compute or who ships a Slack agent first," he stated. "OpenAI and Anthropic are world-class mannequin firms, and so they'll proceed to construct spectacular capabilities. However Kilo is constructed round a distinct thesis: the exhausting downside isn't producing code, it's integrating AI into actual engineering workflows throughout instruments, repos, and environments."
He outlined three areas the place he believes Kilo can differentiate:
"Workflow depth: Kilo is designed to function throughout Slack, IDEs, cloud brokers, GitHub, and the CLI, with persistent context and execution. Even with OpenAI or Anthropic Slack-native brokers, these brokers are nonetheless basically model-centric. Kilo is workflow-centric."
"Mannequin flexibility: We're model-agnostic by design. Groups don't must wager on one frontier mannequin or vendor roadmap. That's troublesome for firms like OpenAI or Anthropic, whose incentives are naturally aligned with driving utilization towards their very own fashions first."
"Platform neutrality: Kilo isn't making an attempt to tug builders right into a closed ecosystem. It suits into the instruments groups already use."
The way forward for AI-assisted software program improvement could belong to whoever solves the mixing downside first
Kilo's launch displays a maturing part within the AI coding market. The preliminary wave of instruments centered on proving that enormous language fashions might generate helpful code. The present wave is about integration — becoming AI capabilities into the messy actuality of how software program really will get constructed.
That actuality includes context fragmented throughout Slack threads, GitHub points, IDE home windows, and command-line classes. It includes groups that use totally different fashions for various duties and organizations with advanced compliance necessities round information residency and mannequin suppliers.
Kilo is betting that the winners on this market is not going to be the businesses with the very best fashions, however those who greatest resolve the mixing downside — assembly builders within the instruments they already use relatively than forcing them into new ones.
Kilo for Slack is offered now for groups with Kilo Code accounts. Customers join their GitHub repositories via Kilo's integrations dashboard, add the Slack integration, and may then point out @Kilo in any channel the place the bot has been added. Utilization-based pricing matches the charges of no matter mannequin the group selects.
Whether or not a 34-person startup can execute on that imaginative and prescient in opposition to rivals with billions in capital stays an open query. But when Breitenother is correct that the exhausting downside in AI coding isn't producing code however integrating into workflows, Kilo could have picked the proper struggle. In spite of everything, the very best AI on the earth doesn't matter a lot if builders have to go away the dialog to make use of it.
[/gpt3]
