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 摘要。