Skip to content

zeph-agent-tools: re-evaluate AgentChannel dispatcher-extraction plan if revived #6536

Description

@bug-ops

Description

crates/zeph-agent-tools originally contained scaffolding for an AgentChannel trait meant to support a ToolDispatcher extraction from zeph-core (Phase 2 of issue #3516, closed). That plan was abandoned: no zeph-core adapter ever implemented the trait, and no ToolDispatcher extraction landed.

#6480 confirmed the scaffolding (channel.rs, error.rs, sealed.rsAgentChannel, ChannelSinkError, ToolEventOutput, ToolEventStart, ToolDispatchError, Sealed) had zero implementors or consumers anywhere in the workspace, and removed it entirely (PR #6535). zeph-agent-tools now exposes only doom_loop_hash, its sole real production consumer.

This issue is the fresh tracking issue that the crate's own (now-removed) module docs said was required before the AgentChannel dispatcher-extraction work could be reopened.

Reproduction Steps

N/A — this is a tracking issue for future design work, not a bug.

Expected Behavior

If a ToolDispatcher/AgentChannel-style abstraction is still desired, it should be redesigned from scratch against the current zeph-core tool-execution architecture (post-#6534 split into agent/tool_execution/{confirmation,retry_reformat,quota,exfiltration,causal_probe,focus_compression,shadow_events,doom_loop}.rs), with a real zeph-core adapter implementing it from day one — not spun up as unconsumed scaffolding ahead of the adapter, which is what caused #6480.

Actual Behavior

No such abstraction currently exists in the codebase. zeph-agent-tools is now a minimal, single-function crate (doom_loop_hash).

Environment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P4Long-term / exploratoryresearchResearch-driven improvement

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions