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
{{ message }}
Repository navigation
[idea] let a pane choose who may send it prompts or keys
#5638
I run a few agent crews across machines through herdr. This is about misrouted input from well-meaning agents, not malicious code.
herdr's skill teaches agents to prompt each other, including across machines. Right now any agent can prompt, send keys, run in or attach to any pane. I want one way in per machine: a bridge pane that only takes prompts from a local background service and one ssh entry point. Orchestrators and workers should only take input from me. Today I find out an agent typed into the wrong session after it already acted.
requested change
Per pane: who may send it input, and optionally who may read its output. A refusal clear enough that an agent stops instead of trying another route. Off by default. I can always type into and attach to any pane myself.
why you want this
It turns a routing convention into something herdr enforces for cooperative agents, which makes running several autonomous agents across machines a lot safer.
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.
idea / problem
I run a few agent crews across machines through herdr. This is about misrouted input from well-meaning agents, not malicious code.
herdr's skill teaches agents to prompt each other, including across machines. Right now any agent can prompt, send keys, run in or attach to any pane. I want one way in per machine: a bridge pane that only takes prompts from a local background service and one ssh entry point. Orchestrators and workers should only take input from me. Today I find out an agent typed into the wrong session after it already acted.
requested change
Per pane: who may send it input, and optionally who may read its output. A refusal clear enough that an agent stops instead of trying another route. Off by default. I can always type into and attach to any pane myself.
why you want this
It turns a routing convention into something herdr enforces for cooperative agents, which makes running several autonomous agents across machines a lot safer.
All reactions