The Claude Code team at Anthropic stated in a discussion lasting about 22 minutes that 70% to 80% of their internal work is no longer done on terminals, with daily deliveries primarily relying on Claude Tag in Slack.

The terminal interface and desktop are only opened in two scenarios: refining a specific implementation or needing to micromanage multiple Claude instances. Instead of a task list, the model is given objectives; Claude Tag separates the interface from the internal transcript, with every visible message in Slack being the result of its proactive tool invocation, while internal monologues remain invisible to collaborators.

The shelf life of underlying capabilities has shortened from yearly to about two months. During the Sonnet 3.5 period, the model often abandoned tasks after completing only three out of five, prompting the team to add a to-do list, which improved completion rates; about a year later, this feature was removed as stronger models no longer required this patch. The conclusion is not to get attached to scaffolding one has built.

Many functions in the harness are explicitly described as patches for current model failure modes, which are proactively deleted as the model improves; however, the scale of tasks has also increased, necessitating the creation of entirely different new tools. It took a long time for AskUserQuestion to teach the model to invoke, but the author now more frequently lets Claude directly produce artifacts with mockups for questioning.

The division of code review has been rewritten: human reviewers previously used a few nitpicks to prove "I have read it," which is now handled by Claude; humans only address constraints that the model does not understand, such as why a certain API looks like this or why service boundaries are drawn here. Workflows evolve from code review, first fanning out to find bugs, then performing multi-faceted adversarial validation on each candidate, filtering out false positives and retaining only real issues; the orchestration layer is code, ensuring no items are missed in for loops.

In market mechanisms, this represents a shift in engineering labor from "humans monitoring terminal conversations" to "humans setting goals, with agents executing in collaboration channels" in an event-driven migration. Computing power and seat budgets have shifted from local TUI to cloud sandbox sessions; the beneficiaries are teams that can clearly articulate goals and solidify verification loops through workflows, while the pressured parties are individuals who still tie value to handwritten pixels and line-by-line patches. Funding and resources are directed towards orchestrating multiple agents rather than piling on more terminal plugins.

The discussion also mentioned that Claude Tag has taken on about 65% of the product engineering PRs for the team; performance optimizations and manually replicating multi-layer radial gradients like those in Mac OS 10.4 Aqua buttons are now considered tasks that the individuals involved can no longer perform as well as the model.

Source: Public Information