Give Agent Channels a Human Owner and a Weekly Review

You tag an agent into a launch channel, and it returns a plan, questions, a draft, and a link. By the next meeting, the thread has more decisions than the team has time to make. The problem is the channel: it has no owner and no review.

The speed is real. At Cognition, the internal merged pull-request count rose 10x in the last few months while headcount rose only 40 percent. That is impressive. It is also a warning. For a small founding team, that is how good tools start to create bad meetings. A channel can become a place where work appears faster than the team can absorb it. The fix is to run the channel as a new operating unit: named owner, clear scope, and a standing review.

A channel without an owner becomes an inbox

Slack Code moves agent-assisted coding into a shared channel where the team can watch progress, steer the agent, and inspect changes before release. It makes AI coding work visible to the whole team in a dedicated channel rather than a private tab. A user can summon a coding agent from a conversation, and the agent opens a channel for the work. Direction is a meeting. It needs an agenda, a decision owner, and a timebox. If nobody owns the channel, the channel owns the team.

In a Cognition demonstration, Devin tagged a code owner named Theo while investigating a broken feature. The agent did not just produce output. It pulled a human into the loop. If your team does not know who that human is before the initial message, the agent will improvise a workflow around whoever answers.

Slack Code requires a human to approve high-stakes actions, including merging code to production. Approval tells you a risky step happened. Review tells you the work is worth doing.

The charter is the operating contract

Before the initial tag, write a short agent channel charter. It should fit in a channel description. It is the minimum set of facts that lets a new teammate understand the job, not a policy document.

• Name the channel's purpose in a single sentence.
• Name the agent's role and what it must not do.
• Name a human owner who can answer questions and stop the work.
• Name the standing sync it replaces or feeds.
• Write a weekly review question the owner will answer.
• Set a stop condition that ends the channel or escalates it.
• Set a handoff point where the output becomes a real deliverable.
• Set an archive rule for when the channel closes and where the trail lives.

Purpose keeps the agent from drifting into general assistance, and role keeps it from becoming a help desk. Owner makes someone accountable when the output is wrong. Sync ties the work to a meeting that already exists. The review question makes the owner check the work, not just watch it. Stop condition ends open-ended work, handoff turns the channel output into a real deliverable, and archive rule preserves the record for later review.

Slack Code archives each agent project channel after the work is finished, leaving a searchable audit trail for later review. An archive alone is not a decision. If the team never reviews the trail, the trail becomes evidence that nobody checked.

Weekly review is the brake

Put a weekly review slot on the calendar before the agent posts. A brief review is enough. The owner answers the charter question, checks the channel for unresolved asks, and decides what stays, what closes, and what escalates. The review is a control point, not a status update.

Agent work can move faster than a small team's operating rhythm. If output grows faster than review capacity, the team will spend cycles cleaning up work it never chose to keep.

62 percent of organizations have tried AI agents in some form, roughly one-third are scaling AI, and 39 percent see bottom-line impact. The gap between trying and scaling is often operational. The agent is rarely the weak point. The channel fails when it has no owner, no scope, and no review.

Over 40 percent of agentic AI initiatives are forecast to be abandoned by the end of 2027, driven by rising costs and unclear business value. Make the operating cost visible before the agent starts posting. A named owner and a weekly review slot are the cheapest controls you can install.

Before the first tag, put the owner in the channel description and the review on the calendar.