operon-core
Operon Core
Operon is a capability runtime over an already reachable private network. It is not a VPN, relay, mesh router, or global routing layer. Use the CLI as the default agent surface, use the TypeScript SDK for application code, and use the gRPC protocol directly only when a custom client is needed.
Start every task by identifying the config path:
- Default:
$HOME/.operon/config.yaml. - Override:
operon --config <path> ....
Before operating on nodes, run:
operon --config <path> config explain
Use operon --config <path> --json config explain when a script or agent needs structured daemon, client, auth, policy, service, and secrets information without reading raw YAML.
Use operon <command> --help for exact syntax. Skills explain scenarios and command choice; CLI help is the source of truth for flags and arguments.
More from denghongcai/operon
operon-cli-ops
Use when an agent needs to inspect Operon nodes, capabilities, config, audit records, traces, or execution graphs through the CLI.
10operon-services
Use when an agent needs to inspect service metadata, run service health checks, or create explicit local TCP or UDP forwards to policy-allowed Operon services.
10operon-sdk-protocol
Use when an agent needs to integrate Operon from application code, the TypeScript SDK, generated gRPC clients, or the documented runtime protocol instead of shelling out to the CLI.
10operon-fs-execs
Use when an agent needs to read, write, copy, remove, or mount remote files, or run and interact with execs on Operon nodes.
7operon-fs-jobs
Use when an agent needs to read, write, copy, remove, or mount remote files, or run and interact with jobs on Operon nodes.
3