UXC

One CLI for tools across protocols.

Daemon

The UXC daemon exists to support reuse, lifecycle management, and background runtime features that do not fit cleanly into one-off CLI calls.

What It Handles

  • session reuse for MCP transports
  • background subscriptions
  • local runtime invocation over a stable socket
  • daemon status and session inspection

Guides

Local App Integration

UXC also ships a TypeScript daemon client for local applications:

npm install @holon-run/uxc-daemon-client

Notes

The daemon is especially useful when auth resolution, session reuse, or background subscriptions should stay outside one-off CLI processes.

Credentials for daemon-managed sources are resolved inside the daemon process, which does not inherit env vars exported in the invoking shell; see Secret Sources for the boundary and recommended alternatives.

The daemon self-terminates when it detects that its state directory or socket has disappeared (for example, after a state cleanup), so stale daemons do not linger on reused sockets. Set UXC_DAEMON_IDLE_TIMEOUT_SECS to a positive number of seconds to shut the daemon down after that much idle time; this is mainly useful for short-lived test harnesses that may skip teardown.

Daemon APIUXC exposes a stable local daemon control plane over a Unix socket using `Content-Length` framed JSON-RPC 2.0.Logging and TroubleshootingUXC uses structured logging through `tracing`. Logs go to `stderr` so JSON output on `stdout` remains machine-parseable.Run as a Managed ServiceRun `uxc` daemon under a service manager when runtime auth environment must stay stable across requests.