Skip to main content
AI News

Qwen Code Adds Agent Team for Multi-Agent Coding Workflows

The June 18 Qwen Code weekly update introduces experimental Agent Team collaboration, durable /loop tasks and in-session /cd workspace switching.

ENHE AI5 min25 views

Qwen Code's June 18, 2026 weekly update says four official versions, v0.18.0 to v0.18.3, were released that week with more than 100 PRs merged. The main update is Agent Team, an experimental opt-in feature for multi-agent collaboration inside coding workflows.

More topic tags (5)
AI NewsAuto PublishingQwen Code Agent TeamAI AgentsAI Tools
Qwen Code Adds Agent Team for Multi-Agent Coding Workflows

Key takeaways

Qwen Code published the weekly update on June 18, 2026.
The update says v0.18.0 to v0.18.3 were released that week with more than 100 PRs merged.
Agent Team enables named, long-lived teammates that can collaborate, message each other and share tasks.
Durable /loop and /cd add persistence and workspace switching to coding workflows.

Qwen Code published a weekly update on June 18, 2026, saying it released v0.18.0 to v0.18.3 during the week and merged more than 100 PRs. Key updates include Agent Team, durable /loop tasks, and an in-session /cd command.

Agent Team is experimental and opt-in. When enabled, the model can create named teams, spawn long-lived teammates, exchange messages, share task lists and consolidate a final report through a leader. This moves coding agents closer to structured team workflows rather than isolated one-shot subagents.

For ENHE users, the practical takeaway is to evaluate AI coding tools by workflow orchestration, permission handling, context recovery, logging and result consolidation, not only by model quality or code completion speed.

What this means for everyday users

The update shows AI coding tools moving toward multi-agent orchestration. Teams should review task persistence, project permissions, audit trails, API key handling and local deployment boundaries before adopting agentic coding workflows.

Tools you may use

Related reading

GitHub Copilot Enters Xcode’s Built-In Assistant Preview: Should You Switch From the Extension?

GitHub announced on 2026-11-04 that Copilot is available in Xcode’s built-in coding assistant as a public preview starting with Xcode 27.3 beta. The setup requires a Mac running macOS Tahoe 26.6 or later, and GitHub says all Copilot plans are supported. The existing GitHub Copilot for Xcode extension remains a separate option, so this is a workflow choice rather than a forced migration. This guide provides a bounded comparison: verify the beta environment, run the same small coding task in the current extension and built-in assistant, compare context, edits, permission prompts, tests, and recovery, then keep the route that produces the clearest reviewable evidence.

GitHub Copilot Cloud Sessions Are GA: How Cross-Device Work Uses Actions Entitlement

GitHub made its connected Copilot cloud experience and cloud sandboxes generally available on paid Copilot plans on October 28, 2026. A user can start a task on github.com, GitHub Mobile, Copilot CLI, the Copilot app, VS Code, Slack, or Microsoft Teams, then continue the same session elsewhere. The included Actions compute entitlement becomes one shared, dollar-based pool for standard hosted runners, cloud sandboxes, and certain larger runners. Billing for cloud-sandbox usage begins in November 2026, so cross-device convenience can affect the same budget used by builds. This article helps users check repository scope, write access, tool permissions, entitlement consumption, and stop conditions before their first cloud session.

GitHub Copilot Can Generate and Edit Images: Check Cost, Watermarks, and File Output First

GitHub introduced a public preview for generating and editing images in Copilot on October 28, 2026. A user can describe an asset in VS Code, the GitHub Copilot app, or Copilot CLI. The selected reasoning model calls a dedicated tool powered by GPT Image 2.5 Flare, previews the result inline, and saves it into the project. The preview is available to Pro, Pro+, Business, and Enterprise plans. Image tokens are billed separately from the chat model against AI credits, and the visible “Made with AI” watermark is optional and off by default. This guide provides a bounded asset test covering input, output location, review, disclosure, and cost evidence.

GitHub Copilot Sessions Can Move to VS Code With Context, Diffs, and Worktree Intact

GitHub has documented a handoff from a Copilot app session to Visual Studio Code. The workflow keeps the session context, changed-file diff, and the same isolated worktree, so a developer does not need to rebuild the task history in a new chat. This article explains the prerequisites and provides a practical review sequence: open the session, inspect the diff, edit locally, run the relevant tests, and decide separately whether to push. The feature is useful when agent work needs human judgment or local tooling, but continuity is not proof that the generated changes are correct. Repository permission, the same GitHub account in both applications, and an existing session with changes are still required.

GitHub in Slack and Teams Adds Multi-Repository Work in One Conversation

GitHub’s Slack and Teams integration can now work across multiple repositories within a single conversation. That is useful when a reported problem spans a frontend and backend, but it is a different event from the original launch of the chat integrations. This article explains the change and provides a scoped investigation request that a non-programmer project owner can give a technical collaborator. It describes what evidence to request before moving from analysis to code changes and how to distinguish an issue, a proposed pull request, a merge, and a deployment. No account-level availability test or automatic resolution is claimed, and the announcement is not treated as permission to change every repository.

Cloudflare opens a waitlist for its managed agent workspace

Cloudflare announced a waitlist for a managed version of Cloudflare OS on October 1 while continuing to describe an open-source, self-hosted path. The post highlights integrations with services including GitHub, Gmail, and Google Drive, enabling agent workflows that can touch code, files, or email. These are consequential actions, so a useful evaluation should examine the exact scopes granted, whether writes require confirmation, how credentials are isolated, and how access is revoked. A waitlist is not general availability, and a connector list does not by itself prove safe operation. Start with a test account and read-only access where possible, then add narrowly scoped actions only after logs and approval points are clear.

Summary

Qwen Code's Agent Team feature is a practical signal that coding agents are becoming workflow systems. Its value depends on controlled task splitting, shared context, permission handling and final result consolidation.

FAQ

What is this ENHE AI article about?

Qwen Code's June 18, 2026 weekly update says four official versions, v0.18.0 to v0.18.3, were released that week with more than 100 PRs merged. The main update is Agent Team, an experimental opt-in feature for multi-agent collaboration inside coding workflows.

Why is this AI update worth watching?

Qwen Code published the weekly update on June 18, 2026. The update says v0.18.0 to v0.18.3 were released that week with more than 100 PRs merged. Agent Team enables named, long-lived teammates that can collaborate, message each other and share tasks. Durable /loop and /cd add persistence and workspace switching to coding workflows.

What does it mean for everyday AI users?

The update shows AI coding tools moving toward multi-agent orchestration. Teams should review task persistence, project permissions, audit trails, API key handling and local deployment boundaries before adopting agentic coding workflows.

Where can readers continue learning on ENHE AI?

Readers can continue with ENHE AI software apps, AI skill tutorials, and AI account service guidance to turn the news signal into practical action.