Skip to content

Arcgentic v2.2.0

Latest
Latest

Choose a tag to compare

View all tags
@Arch1eSUN Arch1eSUN released this 12 Aug 14:01
· 2 commits to main since this release
v2.2.0
e226aaf

Arcgentic v2.2.0 adds a data-driven topology engine, an MCP-UI status panel, and a native-tooling dispatch path for Claude Code V2 — on top of the v2.0.0 orchestration core.

Distribution status

  • GitHub Release: published.
  • PyPI: published as arcgentic==2.2.0.
  • npm: published as arcgentic@2.2.0.
  • Claude Code V2: real-session verified for single-session-subagent mode via the native-tooling (Agent) tier-0 broker path; multi-session-subthread mode and the hook-backed fallback remain unverified by that gate.

Highlights

  • Topology graph engine: the V2 orchestrator's role/state routing tables (ROLE_ALLOWED_CURRENT_STATES, ROLE_ALLOWED_SIGNAL_ROUTES, next_role_for_state) are now a project-configurable Topology (toolkit/src/arcgentic/topology.py), defaulting to byte-for-byte the same behavior as before for zero-config projects. Custom topologies support conditional routing and are validated at parse time (unknown role keys, dangling routes all rejected before they can wedge a project).
  • MCP-UI status panel: arcgentic ships an optional MCP server (arcgentic mcp-serve, pip install arcgentic[mcp]) exposing a round_status_panel tool that renders the current round's state, role-dispatch progress, and audit verdict as an inline MCP Apps panel in supporting hosts, with client-side auto-polling and a prompt-based "dispatch next role" action — no server-side write path. Falls back to a plain-text summary on hosts without MCP-UI support.
  • Claude Code V2 native-tooling broker: skills/claude-code-session-broker/SKILL.md now documents a concrete "tier 0" dispatch procedure using the host's own Agent/SendMessage/ListAgents tools — synchronous for a foreground dispatch, notification-driven for background — ahead of the existing hook-backed broker, which stays as a documented fallback. Dogfooded end-to-end (see tests/dogfood/gate-3-claude-code-native-broker/RESULT.md); handles both first-time (create) and repeat (reuse) role dispatch.
  • All three features shipped through a full brainstorm → design doc → implementation plan → subagent-driven execution → adversarial review cycle, documented under docs/plans/2026-08-12-*.
Assets 2
Loading