Skip to content

feat(cli): add daemon relay and coordination docs for turn-boundary context injection#3

Open
sampurnamo wants to merge 12 commits intoagentralabs:mainfrom
sampurnamo:pr-mailman-relay-context
Open

feat(cli): add daemon relay and coordination docs for turn-boundary context injection#3
sampurnamo wants to merge 12 commits intoagentralabs:mainfrom
sampurnamo:pr-mailman-relay-context

Conversation

@sampurnamo
Copy link

Summary

  • add one-shot �comm chat poll/send CLI commands
  • add daemon TCP relay support plus backlog seeding on connect
  • add generic coordination docs for watcher lifecycle and UserPromptSubmit hook-based turn-boundary context injection
  • add verified pub/sub delivery example and clarify recipient-scoped delivery semantics

Why

Triveni now uses a layered runtime path:

  1. �gentic-comm store + CLI substrate
  2. optional watcher / notifier for human awareness
  3. daemon relay for idle-gap capture
  4. hook-driven turn-boundary prompt injection in the host runtime

This PR upstreams the reusable substrate and generic docs only. The Triveni-specific PowerShell glue and Claude path wiring remain in Triveni.

Validation

  • cargo build passes on the PR branch

Covers verified patterns from live multi-session testing:
- channel semantics: direct/group (recipient:null) vs pub/sub fan-out
- cross-session delivery: store-level, confirmed with live message IDs
- three-layer awareness model: store delivery, human-terminal watcher,
  agent-session explicit polling
- poll-before-respond discipline for preventing parallel-reply blindspots
- watcher channel scope and dynamic channel resolution
- summary table of patterns and routing behavior

All commands and behaviors verified against live triveni.acomm store.
…a plugin

Previous text stated MCP resources/subscribe was the only path to auto-injection.
Corrected: the UserPromptSubmit hook pattern (Mira/MemSearch) achieves the same
outcome today without any MCP protocol changes. A proper acomm plugin can be built
using this pattern. MCP resources/subscribe remains aspirational for true mid-turn push.
A UserPromptSubmit hook script outputting acomm deltas is sufficient.
No MCP plugin architecture needed. Peer messages become ambient context,
same mechanism as task list / code snippet injection already in use.
…to summary

- Replace meera/ishika subscriber/recipient examples with generic agent-a/agent-b
- Replace real probe message content in cross-session table with generic placeholders
- Add UserPromptSubmit hook row to summary table — the ambient context injection pattern
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant