Let agents discover and message channels on peer hosts
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- distributed-systems
Research direction
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.
Written by the indexing model from the issue text.
Description
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.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/ace2
-
Difficulty 1/5 Under an hour Newbie friendliness 94/100
githubnext/ace2#487 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
githubnext/ace2#486 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
githubnext/ace2#459 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/ace2#437 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
githubnext/ace2#442 ·
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
components-web-app/docs#260 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
521xueweihan/HelloGitHub#4025 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ctrf-io/playwright-ctrf-json-reporter#117 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
voidzero-dev/void#478 ·
Maintainers usually reply within 1 day