Slack Code: Coding Agents Az Önce Team Channel'a Taşındı

Bir coding agent hakkında en önemli şey artık code'u ne kadar iyi yazdığı değil. Ne yaptığını kim görebiliyor. Bu aya kadar most teams için honest answer: bir developer, private terminal veya browser tab'de, agent'ın actually ne yaptığını sonra remember etmeyi umuyor. 20 Ağustos'ta launched Slack Code, bu answer'ı "project'teki herkes, by default" yapma konusunda en büyük attempt.

Launch announcement'ı, Slack own follow-up post'u ve coverage'ı okudum. Underlying model same Claude Code, Devin veya Copilot. Değişen work'ün gerçekleştiği room ve bunun coverage'ın düşündüğünden daha önemli olduğu ortaya çıkıyor.

Temel çıkarımlar - Slack Code "code channels" ekliyor: tagged coding agent, Claude Code, Devin, GitHub Copilot, Vercel, ChatGPT coming, open çalışıyor; diffs, live previews ve shipping öncesi human approval olan shared project spaces. - Day one'dan any Slack plan üzerinde çalışır, fakat each agent access separately bought. Channels work complete olunca auto-archive ve audit log tutar. - Real shift supervisory: agent work one person watched private session'dan team watched shared artefact'e geçiyor. Attribution/review gaps fix ediyor, yeni gaps yaratıyor, bystander apathy, approval theatre, channel context attack surface. - Distribution move da. Slack bir yıl agent plumbing built, MCP server, real-time search, Slackbot MCP client, code channels bunu visible yapan surface. - "A person approves the work before it ships" design goal olarak treat edin, guarantee değil. Review process real olmak zorunda.

Ne oldu

20 Ağustos'ta Slack, Slack Code'u all plans, free workspaces dahil launch etti. Mechanics launch coverage ve TechRepublic write-up'a göre:

• Any Slack conversation içinde coding agent tag. Agent task için dedicated code channel spin up eder, bug fix, page update veya feature build.

• Channel'daki everybody agent'ın work ettiği same conversation'ı görür, proposed code diffs review, live HTML previews check, agent'ın incorporate ettiği feedback bırakır, finished work approve. Human sign-off olmadan nothing ships.

• Work complete olunca channel auto-archive ve audit log kept.

• Launch partners Anthropic Claude, Cognition Devin, GitHub Copilot, Vercel; OpenAI ChatGPT coming announced. Slack code channel APIs'ı wider developer community'ye açmayı planlıyor, any custom agent join etsin.

Channel'a kim land configurable. Katie Steigman, Slack VP of Product, Reworked'e şöyle dedi: "You could have the agent just bring in the user who tagged the agent to make the code channel or you could configure the agent to make inferences on its own as to who should be in the channel based on the context it has." Rob Seaman, Slack EVP ve general manager, intent'i şöyle framed: "AI only creates value when it's part of how a team actually works."

Slack Code, 20 Ağustos 2026 tüm Slack plans üzerinde launched, partner coding agents, Claude, Devin, Copilot, Vercel, ChatGPT announced, shared "code channels" içine koyuyor; whole team agent conversation, diffs, live previews görür, shipping öncesi work approve ve channel auto-archive olunca audit log inherit eder, Slack announcement'a göre.

Supervision private session'dan çıkıyor

Feature list'in gizlediği şey. Most agent supervision bugün one tired person'ın maintained fiction'ı. Agent someone's IDE veya cloud sandbox'ta run, diff pull request olarak gelir, "review" o developer'ın 5pm appetite'ı kadar. Reasoning, dead ends, working one öncesi three attempts: all evaporate. Enough agent output review ettim, diff process'in least informative part'ı.

Slack Code actual proposal process'i artefact yapmak. Channel agent'ın worked-from conversation'ını, intermediate steps, received feedback, approvals tutar ve searchable record olarak archive. Genuinely different supervision model, good teams junior engineers review'üne current agent review'den closer: output değil work'ü watch.

Who supervises de değişir. Pitch explicitly PMs, designers, non-technical teammates follow. Cautiously for, reservation: room full of watchers reviewer değil. Diff literacy osmosis ile gelmez, "team can see it" quietly "nobody checked it" olabilir. Governance questions, ten people watched nobody owned approval iken accountable kim, agent governance framework içinde işlediğim şeyler ve Slack Code answer etmiyor. Visible yapıyor, honest first step.

Slack Code agent supervision'ı private session'dan shared archived channel record'a taşır: conversation, intermediate steps, feedback, approvals searchable artefact olarak persist, Slack product post'a göre. Room of watchers içinde approval kim owns accountability question customer'a kalır.

Shared context iki taraflı keser

Second big claim context. Slack argument: task context already channels'ta, bug report, spec discussion, customer complaint, agent context'in olduğu yerde work etmeli, private prompt'a copy-paste değil. Right, Slack all year shipping plumbing üstünde: MCP server ve real-time search API February generally available, agents'a governed workspace messages/files access, Slackbot MCP client June. MCP servers roundup içinde team tools MCP access neden agent context'in useful half'ı anlattım; channel model conclusion.

Ama shared context shared exposure da. Channel okuyan agent everything okur, someone pasted credential "just for a minute" message dahil, customer forwarded external content dahil. Known security researchers same: content agent can read, content can instruct it. Shared channel private session'dan bigger prompt-injection surface, full stop. Write access agent'ı busy channel'a point etmeden which channels read, tools touch deliberate. Architecture work, settings değil, agentic architecture same trade-off: capability ve blast radius together grow.

Slack Code context advantage, agent task context'in already yaşadığı yerde work, Slack'ın February 2026 generally available yaptığı MCP-based workspace access'e dayanıyor, Unite.AI report'a göre. Same shared context prompt-injection ve credential-exposure surface'i widens, launch materials address etmiyor.

Attribution ve review, unglamorous wins

Launch'ın least flashy parts benim buy edeceğim. Attribution first: code channel'da every agent action agent identity altında, everyone kim biliyor workspace, project survive audit log. Basic sounds. Basic. Most teams'in agent work için currently sahip olduğundan more attribution infrastructure, "agent did it"/"I did it" same git history blur. Regulated industries bir yıldır bu boring şeyi istiyor.

Review second. Channel diffs/live previews, agent incorporates feedback, shipping öncesi hard approval gate. Missing'e dikkat: Slack materials person approves work diyor, who must be, what shown, configured reviewer holiday olursa ne olur specify yok. Approval checkbox approval theatre: everyone learns green button click. Value alan teams approval'ı real code owner with real diff review'e wire, agent channel output evidence olarak keep, review itself değil.

Competitive context önemli. Microsoft September 2025 Teams threads içine Copilot coding agent, Block July open-source Buzz ship, Reworked coverage not ediyor. Chat window agent work contested surface oluyor, Slack advantage unglamorous: team already there. Distribution beats cleverness collaboration software, every time.

Slack Code each agent'a own identity in channels verir ve archived project başına audit log keep, TechRepublic'e göre, fakat approval gate "a person approves the work before it ships" reviewer identity veya review standards specify etmiyor. Microsoft Teams Copilot agent, September 2025, Block open-source Buzz, July 2026 direct comparables, Reworked'e göre.

Şimdi ne yapmalı

Team Slack ve coding agents kullanıyorsa three steps.

1. Bu hafta: One low-stakes, well-specified task seç, copy change veya clear reproduction small bug, two-three watchers ile code channel run. Agent test değil, team review behaviour test. Anyone actually diff reads watch.

2. Anything real ships öncesi: Every repo agent work approver kim, what required check, writing decide. Answer "whoever's in channel" ise review process yok, button var.

3. Broad rollout öncesi: Agent which channels read, environment which credentials holds scope. Channel history context, context attack surface. Narrow start, evidence ile widen.

FAQ

Slack Code nedir?

20 Ağustos 2026 launched Slack feature, teams partner coding agents, Claude Code, Devin, GitHub Copilot, Vercel, ChatGPT coming, conversation içine tag. Agent task için dedicated "code channel" açar, team work watch, diffs/previews review, shipping öncesi result approve. Done olunca channel automatically archives.

Paid Slack plan gerekli mi?

Hayır. Slack Code every plan, free workspaces dahil. Ama each coding agent access vendor'dan separately bought, practical cost already pay agents'a bağlı.

Slack Code code review replace eder mi?

Hayır, ve öyle treat etmek main risk. Review shared archived channel'a relocate ve approval gate ekler, quality named human diff read'e bağlı. Owner olmayan visible process, conscientious reviewer private process'ten worse, çünkü supervised görünür.

Agent whole channel read etmek safe mi?

Channel içeriğine bağlı. Agent can read anything can influence it, pasted credentials, forwarded external content. Read access narrow scope, agent credentials least-privilege, channel content untrusted input treat, agent perspective indeed.

Sonuç

Slack Code agents'a better code yazdırmayacak. Amaç o değil. Agent work visible, attributable, reviewable by default yapıyor, team'in already olduğu yerde, çoğu agent deployment'ın quietly missing three things. Catch visibility supervision değil. Channel record ve gate verir; anyone actually watching yine sizin problem. Teams approver nasıl configure watch, agent değil. Works veya theatre burada.

Agents'ı review control kaybetmeden team workflows'a nasıl koyacağınızı çalışıyorsanız, clients ile regular conversation. İletişime geçin.

Kaynaklar

• Salesforce, "Introducing Slack Code: Agentic Coding for Teams": https://www.salesforce.com/introducing-slack-code/ (yayımlanma 2026-08-19, erişim 2026-08-29)

• Slack, "Slack Code: Where Your Team and Agents Build Together": https://slack.com/blog/news/slack-code-channels-for-agents (yayımlanma 2026-08-28, erişim 2026-08-29)

• Unite.AI, "Slack Code Puts AI Coding Agents in Dedicated Project Channels": https://www.unite.ai/slack-code-puts-ai-coding-agents-in-dedicated-project-channels/ (yayımlanma 2026-08-20, erişim 2026-08-29)

• TechRepublic, "Slack Code: AI Coding Agents Get Shared Channels for Review and Oversight": https://www.techrepublic.com/article/news-slack-code-ai-coding-agents/ (yayımlanma 2026-08-21, erişim 2026-08-29)

• Reworked, "Slack Code Puts AI Coding Agents in Shared Channels": https://www.reworked.co/collaboration-productivity/slack-code-brings-collaborative-ai-coding-into-channels/ (yayımlanma 2026-08-20, erişim 2026-08-29)