Your Website Bug Doesn't Need a Developer Ticket Anymore

Every small business has a bug it has stopped bothering to report.

Not because it does not matter. Because reporting it never felt worth the trouble.

You email the web agency. The web agency opens a ticket. The ticket sits behind four other tickets. Three days later someone replies asking you to "confirm the issue is still reproducible." By then you have worked around it, told your team to just tell customers to call instead, and moved on. The bug stays.

Priya runs a nine-person plumbing and heating company outside Manchester. Last month, an update to her website quietly broke the "book a callout" form. The dropdown for service type stopped loading, which meant nobody could submit a request without also typing their postcode into the wrong field. Her web agency's retainer covers fixes like this, technically. Practically, it meant a five-day turnaround and an invoice line for "minor bug fix, 0.5 hr." She did not report it. She just told her office manager to keep an eye on the phone.

That is the real cost of small bugs. Not the bug itself. The queue behind it.

What Is Slack Code?

Slack Code is a new kind of Slack channel, launched by Salesforce on August 20, 2026, where an AI coding agent does the work of fixing or building something while your whole team watches it happen in real time.

You tag a supported agent, Anthropic's Claude, Cognition's Devin, GitHub Copilot, or Vercel's agent, from any conversation. That agent opens a dedicated "code channel" scoped to the task, pulls in the people it needs, and gets to work. Everyone in the channel sees the plan, the code changes as a diff, and a live preview of what the fix actually looks like. Nobody has to open a separate tool, learn to read raw code, or wait for a status update. Slack says over 70% of these code channels open and close within a single day, from the first tag to a shipped fix.

That number matters more than it sounds. It means the bottleneck was never the coding. It was the queue, the handoff, and the days spent waiting for someone with the right login to have five spare minutes.

The Way Small Business Website Fixes Actually Work Right Now

Here is the current process, for almost every small business without a developer on staff:

• Someone notices something is broken.
• They decide whether it is worth reporting.
• If yes, they email or message a freelancer or agency.
• The freelancer or agency triages it against everyone else's tickets.
• Days pass. Nobody on the team can see what is actually being changed.
• A fix arrives, or does not, with no visibility into what happened in between.

Notice what is missing at every step: your team. The people who spotted the bug, who know the customer impact, who could approve a two-line fix in ten seconds, are locked out of the actual work. They are stuck waiting for someone else to finish, then hoping the fix matches what they meant.

You are not slow because your team is small. You are slow because the work happens somewhere you cannot see.

How a Code Channel Actually Works

The easiest way to understand the shift is to compare it to a chatbot.

A chatbot answers a question and stops. You ask "why is the booking form broken," it might explain what a broken dropdown looks like in the code, and then it is on you to fix it, test it, and ship it yourself.

A code channel finishes the job. You tag Claude and say "the service dropdown on the booking page isn't loading, customers can't select a service type." Claude opens a channel, reads the actual page, proposes a fix, and shows the before-and-after as a diff alongside a live preview of the fixed form. Your office manager, who has never opened a code editor in her life, can look at the preview, click the dropdown, confirm it works, and give a thumbs up. Someone technical, or Priya herself, approves the change, and it ships.

Nobody read a line of code to make that decision. They read a working preview, the same way they would judge a photo of a finished repair.

Why This Is Happening Now

Coding agents got good enough to trust with real changes over the last two years. Claude Code, GitHub Copilot's coding agent, and Devin can already read a codebase, write a fix, and open a pull request on their own. That part is not new.

What was missing was a place for a whole team, not just one developer, to watch that work happen and sign off on it together. Anthropic's product lead for Claude, Cat Wu, put it plainly at launch: "So much engineering work already starts as a conversation in Slack. Slack Code gives teams a dedicated channel where the people, the context, and Claude work together from the start."

Slack is betting that the bottleneck in AI-assisted work was never the AI. It was the fact that only one person could see it happening.

Isn't This Just Claude Code or Devin With Extra Steps?

No, and the difference matters if you are deciding whether this is worth your time.

A terminal-based coding agent like Claude Code is built for deep, heads-down execution inside a codebase: running commands, editing dozens of files, testing changes. That is still the right tool for a solo developer doing serious, technical work.

Slack Code is built for the coordination around that work, the part small teams actually struggle with. It brings the original request, the people affected, the agent's questions, the diff, the preview, and the final approval into one place everyone can already see. For a nine-person plumbing company with no developer, that coordination layer is the entire problem. There is no codebase to go deep into alone. There is a broken form, a team that needs to confirm it is fixed, and an owner who needs to sign off before it goes live.

Slack Code does not make the agent smarter. It makes the agent's work visible to people who were never going to open a terminal in the first place.

How to Fix Your First Bug in Slack Code, Step by Step

1. Connect one coding agent. Slack Code launched with Claude (Anthropic), Devin (Cognition), GitHub Copilot, and Vercel's agent, with OpenAI's ChatGPT coming later. Pick whichever one your team, or your web agency, already uses. It is available on every Slack plan, including free workspaces, at no extra charge from Slack. Access to the agent itself is a separate subscription.
2. Describe the problem where it already lives. Do not open a new tool. In the Slack channel where someone already mentioned the bug, tag the agent and describe what is broken in plain language, a screenshot helps.
3. Let the code channel open. The agent spins up a dedicated channel for that task, pulls in relevant people, and gets to work, reading the actual page or repository rather than a secondhand description.
4. Watch the diff and the live preview. The channel shows the proposed change as a before-and-after diff and, for anything web-facing, a live preview you can click through exactly as a customer would.
5. Ask for changes if something looks off. Anyone in the channel can redirect the agent mid-task: "that field should be optional," or "keep the old label." This is the step most small teams skip when working with a developer, because interrupting someone else's work feels awkward. Here it is built in.
6. Approve, and let it ship. A person still has to sign off before anything goes live. Once approved, the fix ships and the channel archives itself, leaving a searchable record of what was asked, what changed, and who approved it.

Priya's team did exactly this with the booking form. Her office manager tagged Claude with a screenshot of the broken dropdown. Claude opened a code channel, found the field that had lost its options after the last update, and posted a working preview inside twenty minutes. Two people in the channel clicked through it on their phones, confirmed the postcode field worked properly again, and Priya approved the fix from her van between callouts. No ticket. No invoice line. No week of workaround.

Fixing a website bug: three ways, compared

Approach	Who can review the fix	Typical turnaround	Cost per small fix
Agency retainer ticket	Whoever the agency assigns, later	2–5 business days	Hourly rate, often 0.5–1 hr minimum
Hire a part-time developer	One person, if available	Depends on their workload	Salary or contract rate, ongoing
Slack Code with an existing agent	Anyone in the channel, in real time	Minutes to a few hours	Cost of the agent subscription only

What You Have After This

A week in, you have fixed the bugs you had stopped bothering to report, because reporting them now takes one tagged message instead of an email you have to word carefully.

A month in, your team has stopped treating small website and workflow problems as things that need a specialist. Your office manager, your ops lead, your most detail-oriented salesperson, they can all spot a problem, describe it, and watch it get fixed, without ever learning to code.

Six months in, the backlog you were quietly carrying, the broken dropdown, the confusing confirmation email, the form field nobody updated since 2024, is gone. Not because you hired anyone. Because the distance between noticing a problem and fixing it collapsed from a week to an afternoon.

Same team. Same tools. A completely different relationship with the small things that used to just sit there broken.

If you want help figuring out which of your own recurring bottlenecks, not just website bugs, are ready for an agent to take off your plate, that is exactly what we map out in the 14-Day AI Readiness Sprint.