Skip to main content
This agent answers questions like “why is the web box slow?” or “what is filling the disk?”. It does not log in to your machine. It asks your program to run checks from a short, read-only list, reads the output, and explains what it found. Your program decides what runs, on which host. You will use: function tools and streaming. No sandbox, so no machine time.
This is the safe way to point an agent at your own servers on hosted Orca today. Self-hosted environments, where the agent gets a shell on your machine, are coming soon, and give the agent far more power than a list of checks.

How it works

One tool, run_check, takes the name of a check, not a command. The model can only pick from names your code knows.

The program

Examples on this page assume the settings from the shared setup. It runs each check over ssh on the host you name. Use a dedicated low-privilege account for it.

Make it yours

  • Add checks, not a shell. Need container status or a service’s log? Add a named entry to CHECKS. Never add a check that takes free text from the model and puts it in a command.
  • Keep fixes with a person. The agent suggests commands; it does not run them. If you later add an action such as restart_service, require confirmation in your program before it runs, as in the support agent.
  • Strip secrets from output. Process lists and logs can contain tokens in arguments or URLs. Filter them in run_check before they reach the model.
  • Check a fleet. Add a host parameter with an enum of your host names, and let the agent compare machines.