You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prime Agent 0.7.0 already includes a built-in Herdr reporter. When it runs in a Herdr 0.8.0 pane, herdr agent list correctly shows prime-agent and its lifecycle state without installing the Pi integration.
The remaining gap is that Herdr does not recognize prime-agent as a supported agent kind. In a clean disposable session I observed:
launching prime-agent --offline creates a visible idle prime-agent through its reporter;
herdr agent explain returns agent_explain_unavailable because there is no detected agent label;
herdr agent start --kind does not offer prime-agent;
after a clean /quit, the pane can remain labelled prime-agent after the foreground process has returned to the shell;
after a Herdr server restart, the pane returns as a shell instead of resuming the reported Prime session.
Prime Agent supports prime-agent --resume <path|id> and its reporter already supplies a session path or ID. Treating Prime Agent as a distinct supported agent would complete launch, identity, cleanup, and cold session restore while retaining the built-in reporter as the lifecycle authority.
Would first-class Prime Agent support fit Herdr's direction? If so, could a maintainer define the preferred contribution path or approve an implementation issue for it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Prime Agent 0.7.0 already includes a built-in Herdr reporter. When it runs in a Herdr 0.8.0 pane,
herdr agent listcorrectly showsprime-agentand its lifecycle state without installing the Pi integration.The remaining gap is that Herdr does not recognize
prime-agentas a supported agent kind. In a clean disposable session I observed:prime-agent --offlinecreates a visible idleprime-agentthrough its reporter;herdr agent explainreturnsagent_explain_unavailablebecause there is no detected agent label;herdr agent start --kinddoes not offerprime-agent;/quit, the pane can remain labelledprime-agentafter the foreground process has returned to the shell;Prime Agent supports
prime-agent --resume <path|id>and its reporter already supplies a session path or ID. Treating Prime Agent as a distinct supported agent would complete launch, identity, cleanup, and cold session restore while retaining the built-in reporter as the lifecycle authority.Would first-class Prime Agent support fit Herdr's direction? If so, could a maintainer define the preferred contribution path or approve an implementation issue for it?
All reactions