Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Let agents discover and message channels on peer hosts

未关闭
#57 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript

调研方向

Start from the native channels/message tools and the local catalog they read, then compare with how human channel routing already reaches peer hosts through the injected delivery boundary. Read the related issues #10, #11, #13, #15 and the review evidence comment on #5 to understand the policy and boundary constraints before designing. Done means peer channels are discoverable with stable identity, messages deliver idempotently across two hosts with clear offline/reconnect outcomes, and the verification scenario (duplicate delivery, reconnect, renamed target) passes on real channels.

由索引模型根据 Issue 内容生成。

描述

Human channel routing reaches peer hosts, but the native channels/message tools currently use the local catalog. #13 covers hosted-channel messaging; #11 and #15 cover different boundaries.

Acceptance

  • Discover reachable peer channels with stable identity and enough project/host context to select the intended destination.
  • Deliver attributed messages and optional agent invocations through the existing tailnet and collaborator-agent policy; expose a supported reply path.
  • Preserve destination-host execution, idempotent delivery, and clear offline/reconnect outcomes.
  • Verify with real channels/models on two hosts, including duplicate delivery/reconnect and a target whose name changes.
  • Keep agents in different channels as messaging peers, not parent/child owners.

This is an extension beyond #10's baseline human collaboration check. Preserve the runtime-neutral channel and injected delivery boundary.

Related: #10, #11, #13, #15. Review evidence.

Tracked by #58.

主要语言
TypeScript
星标
1
派生
0
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

githubnext/ace2 的其他 Issue

查看 githubnext/ace2 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。