Expand description
Herdr’s socket, typed.
Newline-delimited JSON over $HERDR_SOCKET_PATH. Two shapes of use: a
request/response Client for one-shot calls, and Events which holds a
connection open and yields events as they arrive.
Deliberately hand-written rather than generated from herdr api schema --json: plugins touch a dozen of the 89 methods, and a generated surface
would be mostly dead code that still has to compile.
Re-exports§
pub use cwd::Cwd;pub use cwd::CwdSource;pub use events::Event;pub use events::EventKind;pub use events::Events;pub use model::Agent;pub use model::AgentSession;pub use model::Pane;pub use model::PluginContext;pub use subagents::Subagent;pub use subagents::SubagentRoster;pub use subagents::SubagentStatus;
Modules§
- cwd
- Where an agent is actually working, and how sure we are.
- events
- A held-open connection that yields Herdr events.
- model
- The slice of Herdr’s schema plugins actually touch.
- subagents
- The in-process subagents running inside one agent.
Structs§
- Client
- One request, one response, one connection — Herdr’s rule, not a choice.
Functions§
- herdr_
bin - The Herdr binary, as Herdr itself reports it.
- notify
- Send
methodand do not wait to be told it worked. - plugin_
context - The invocation context Herdr passes to a plugin as JSON in the environment.