@nocoo/eagle-agent
v0.9.0
Published
Report all local Herdr spaces and machine resources to Eagle
Readme
@nocoo/eagle-agent
Agent 0.9.0 improves realtime secret redaction and adds native history-key input. Optional macOS GPU, temperature, fan and traffic observations remain read-only. Install macmon separately and include it in the service PATH for hardware readings; no sudo or fan control is used.
Read-only Herdr inventory, task evidence, machine resources and named TCP port checks for Eagle. Requires Node.js 24+ and the Herdr CLI on macOS or Linux.
Download and install
Check node --version, npm --version and herdr --version first. Install Node.js 24+ from https://nodejs.org/en/download if needed, and have Herdr installed and running. No Eagle repository checkout, TypeScript compiler or npm login is required to install this public package.
Install Agent v0.9.0 from npm. Website releases are independent:
npm install -g @nocoo/[email protected] --registry=https://registry.npmjs.orgIf npm downloads time out, use the Tencent Cloud mirror / 下载超时时首选腾讯云镜像:
npm install -g @nocoo/[email protected] --registry=https://mirrors.cloud.tencent.com/npm/--registry applies only to this installation; it does not change your global npm configuration. Mirrors may lag (404 / ETARGET); retry later or use the official registry when reachable. Keep the pinned version, HTTPS and certificate verification. Eagle credentials are unrelated to npm and must never be sent to a registry.
Verify the installation before configuring the agent:
eagle-agent --version # expected: 0.9.0
eagle-agent --helpIf the command is missing, ensure npm's global bin directory is on your PATH. Use a user-owned Node/npm installation if global installation fails with EACCES.
Connect a machine
When an Agent is already configured, check the service's EAGLE_CONFIG, machine
ID and URL origin first. Only a matching ID and origin permits token-only
rotation. Moving to another deployment requires a separate private config
directory and explicit new spoolDir; preserve, but do not replay, the old queue,
cache or Manager state. Verify the new destination before switching the service,
and set its EAGLE_CONFIG explicitly. See docs/AGENT.md in the repository for
the rotation/migration procedure. Do not overwrite a different machine identity.
Open Eagle's Connect page, create a machine and copy its onboarding prompt. Give the prompt to the management agent on that machine. It contains a machine-scoped credential shown only once.
Store configuration at ~/.config/eagle/agent.json (directory 0700, file 0600). EAGLE_CONFIG selects another file. eagle-agent init reads JSON from stdin and creates this file securely; it refuses to overwrite an existing file. Never pass a token in command arguments, commit it, print it, or include it in reports. Rotation requires updating the token in the existing secure configuration.
eagle-agent once
eagle-agent watch
eagle-agent collect /private/path/report.json
eagle-agent upload /private/path/report.json
eagle-agent heartbeatonce collects all running Herdr sessions and sends a complete snapshot. watch repeats every 30 seconds by default. Set up a user launchd or systemd service to keep it running across restarts, with the correct absolute executable paths and PATH for Node and Herdr. Do not run overlapping collectors for one configuration.
The machine's Durable Object maintains current state. Unacknowledged reports remain in a private local spool; retries preserve their IDs. Older reports cannot roll back current state. Semantic changes are retained independently in DO UTC hourly buckets and replicated to D1; whole-report archives and hourly AI aggregation remain paused.
Optional watchPorts: [{ "name": "Raven", "port": 7024 }]. Only loopback TCP checks are supported; a listening port does not prove service or task health. CPU, RAM, disk and uptime are sampled automatically. Task status combines terminal summaries, goals, Git, tests, processes and deployment evidence; pane lifecycle badges are weak hints.
Detailed configuration and manager evidence format: https://github.com/nocoo/eagle/blob/main/docs/AGENT.md
Environment resources
Agent 0.8.0 adds 30-second CPU/load/memory and OS network/VPN samples,
with configurable disk/temperature sampling (slowIntervalSeconds, default 300,
range 60–3600). intervalSeconds must be 30; update any previous custom value
explicitly before upgrading. Cached slow observations keep their original times.
Agent 0.8.1 reads macOS hardware through optional unprivileged
macmon. A
tun/utun interface alone never proves VPN connectivity. No addresses,
connection details or profile names are uploaded. The machine page displays
24-hour CPU/memory/load history from the same report stream.
The receiving Worker must support the additional telemetry fields before upgrading an installed collector. Publishing a package does not upgrade or restart existing services. Preserve the configured identity, credentials and spool when explicitly upgrading. Full contract: https://github.com/nocoo/eagle/blob/main/docs/RESOURCES.md
Optional reporting proxy
Direct connections are the default. Set NODE_USE_ENV_PROXY=0 in the service environment and leave proxy addresses unset. A local proxy is not a prerequisite for Eagle.
Only when the machine needs a proxy, set NODE_USE_ENV_PROXY=1 and HTTPS_PROXY to the user's verified HTTP(S) proxy URL. Use HTTP_PROXY for HTTP destinations and NO_PROXY for destinations that should bypass the proxy. Do not assume a host or port. These are Node environment settings, not fields in agent.json; no new Agent package is required. Node.js 24.5+ is required for proxying the realtime-watch WebSocket connection.
Apply the selected environment to each Eagle service (watch, manager-watch, and realtime-watch) and to any foreground verification command. On macOS, use the LaunchAgent's EnvironmentVariables; on Linux, use the user systemd unit's environment. Keep proxy credentials, if needed, in protected service configuration, never in command arguments or reports.
To return to direct connections, remove the service's proxy address variables and set NODE_USE_ENV_PROXY=0. Reload the service definition and restart it; restarting alone does not reload a changed launchd plist. Wait until the old service has fully stopped before registering it again. Preserve the secure Agent config, spool and Manager state. Confirm a fresh successful report and an empty pending spool; a running process alone does not prove connectivity. An explicitly selected proxy remains required until disabled; there is no automatic direct fallback.
Continuous Pane summaries
Eagle is agent-neutral. Reuse the machine's existing management Agent; Hermes Agent is recommended, not required. Cherry is one machine's local Hermes profile/alias, not a product or dependency to install. Do not search for or install an unrelated Cherry package. If no suitable Agent is configured yet, keep eagle-agent watch running and report that semantic setup is pending.
Set manager.command explicitly in the existing secure config, preserving its other fields. The command is an argv array, executed without a shell: it receives a UTF-8 instruction followed by bounded input JSON on stdin and must return the requested JSON array on stdout. Use the existing model/provider/profile, disable tools and avoid interactive prompts. A small adapter script can normalize another Agent's input/output. Eagle does not install an Agent or change its model configuration.
For an already configured Hermes, inspect hermes chat --help, locate its executable and replace the example path below. Only use flags supported by that installed version. The official project is https://github.com/NousResearch/hermes-agent; follow its installation instructions only if Hermes is actually needed. A working alternative Agent needs no Hermes installation.
{
"manager": {
"id": "manager",
"command": ["/absolute/path/to/hermes", "chat", "--query-file", "-", "--oneshot", "--quiet", "--toolsets", "none", "--ignore-rules", "--source", "tool", "--max-turns", "1", "--run-budget", "55"],
"minIntervalSeconds": 120,
"batchSize": 8
}
}This is a config fragment, not a replacement for agent.json. For a named Hermes profile, use its existing launcher/wrapper or documented profile selection; retain the same provider credentials and service environment. The example does not pass model/provider overrides or --ignore-user-config. For another Agent, replace the entire command array with its verified stdin/noninteractive invocation or adapter; do not reuse Hermes flags blindly. Keep credentials out of argv and model input.
Run eagle-agent manager-once, verify actual summaries, then supervise eagle-agent manager-watch separately from watch using absolute paths and the required PATH/profile environment. Alternatively schedule manager-once with the machine's existing cron/scheduler; verify that scheduler's syntax and do not run both schedulers. A single successful cycle does not provide continuous coverage.
Manager has a 65-second subprocess deadline and a persistent 120-second minimum per Pane/task. It interprets changed inputs only; stable inputs refresh freshness without another model call or history entry. Each summary describes task, phase, progress, outcomes, blocker, next step and rationale with deterministic evidence references. Neither Agent output nor a terminal completion claim certifies tests or deployment.
Preserve the existing manager.id and manager-MACHINE_ID/ directory across upgrades, even if its old ID is cherry: IDs are durable writer identities, not executable names. Keep sequence, pending batches and cached summaries. When upgrading from 0.4.0's implicit Cherry default, explicitly configure the already working command and keep ID cherry; do not reset identity or install a different Agent.
Protocol, independent DO streams, hourly history and retention: https://github.com/nocoo/eagle/blob/main/docs/PANE-SUMMARIES.md Reusable Skill: https://github.com/nocoo/eagle/blob/main/skills/eagle-report/SKILL.md
Space realtime control
Run eagle-agent realtime-watch as a separate user service using the same secure configuration. This enables authenticated web control through an outbound WebSocket; the collector remains read-only. Open a Space in Eagle and select 实时模式, then 接管输入. Unwatched Spaces consume no screen polling. Leaving/hiding the page releases the subscription; input is never replayed after a disconnect. Details and limits: https://github.com/nocoo/eagle/blob/main/docs/REALTIME.md
Realtime upgrade
Agent 0.9.0 preserves ordinary status labels while masking wrapped and quoted credentials in both plain and styled terminal output. Bounded redaction avoids repeated scanning of long whitespace, base64 and Bearer sequences.
Up/down history keys require Kitty disambiguation or report-all-keys mode; unsupported cursor modes fail closed. Explicit Ctrl+P/N remain separate actions, not automatic substitutes. Deploy the matching Worker before restarting existing bridges. Preserve the machine configuration, spool and Manager identity/state; installing the package does not start or restart services automatically.
