From the ecosystem ROADMAP (§1 Phase 2, ref #3695).
What
When a task completes, inject a "done, X unblocked" line into the agent's tmux pane (via the shared-lib tmux-inject, extracted from tg-ctl). Plus due-date reminders delivered to the agent the same way.
Why
The agent should learn that finishing task A unblocked B/C without re-querying, and should be nudged about due dates. Pushing this into the agent's tmux pane is how tg-ctl already surfaces inbound events.
Acceptance
- On a task transitioning to done, dependents are recomputed and a "done, unblocked" message is injected into the originating agent's tmux pane.
- Due-date reminders fire to the agent ahead of the due time.
- Injection respects the pending-question DEFER rule (see tg-cli decisions-as-buttons issue) — never blast text into an open interactive prompt.
- Built on the daemon (separate issue) and the shared
tmux-inject primitive.
From the ecosystem ROADMAP (§1 Phase 2, ref #3695).
What
When a task completes, inject a "done, X unblocked" line into the agent's tmux pane (via the shared-lib
tmux-inject, extracted from tg-ctl). Plus due-date reminders delivered to the agent the same way.Why
The agent should learn that finishing task A unblocked B/C without re-querying, and should be nudged about due dates. Pushing this into the agent's tmux pane is how tg-ctl already surfaces inbound events.
Acceptance
tmux-injectprimitive.