Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.acornops.dev/llms.txt

Use this file to discover all available pages before exploring further.

Every Linux VM that AcornOps observes runs the VM agent. The agent opens an outbound WebSocket to the control plane, reports host snapshots, and executes read-only VM tools during troubleshooting runs.

​
Register a VM

  1. Open a workspace in the management console.
  2. Go to Virtual Machines.
  3. Register a VM with a name and optional hostname.
  4. Copy the generated systemd install instructions.
  5. Run the instructions on the Linux host.
  6. Confirm the VM shows as connected.
The registration response includes { virtualMachine, agentKey, installInstructions }. Treat installInstructions.command as authoritative.

​
Agent behavior

The VM agent authenticates with the issued agent key and connects to: 
wss://acornops.dev/api/v1/agent/connect
The initial VM agent supports Linux with systemd. It is read-only: it can inspect host state and logs, but it cannot modify services, packages, files, users, firewall rules, or kernel settings.

​
Inventory and findings

VM snapshots populate:
  • host summary and OS metadata,
  • process inventory,
  • systemd service inventory,
  • listening ports,
  • metrics history,
  • findings derived from host health signals.
The management console shows this data on the VM detail page. VM logs are fetched live through the connected agent and are bounded by source and limit.

​
Tools and MCP

The VM built-in tools include:
  • get_host_summary
  • list_processes
  • get_process
  • list_services
  • get_service_status
  • get_logs
  • search_logs
  • check_port
  • list_listening_ports
VM targets also support target-scoped remote MCP servers. Add servers from the VM detail page under MCP Servers, test discovery, then enable reviewed tools.

​
Troubleshooting chat

VM chat runs are target-scoped and read-only. The execution engine and LLM gateway receive the VM target scope, and tool calls are limited to the allowed VM and MCP tools for that run. If the VM stays disconnected, verify the platform URL, WebSocket route, agent key, outbound network access, systemd service state, and agent logs.