Core

A Core is a machine running the Actana Control daemon: the stateful half of the product. It hosts projects, tasks, and sessions; owns its SQLite, PTYs, and files; and spawns Harness CLIs against repos that never leave it. One Panel drives zero or more Cores, and every client — Panel, CLI, SDK — reaches a Core the same way, over the core link.

flowchart LR
  P[Panel] -->|core link| C[Core daemon]
  CLI[actana CLI] -->|core link| C
  C --> DB[(SQLite)]
  C --> PTY[PTYs]
  PTY --> H[Harness CLI]
  H --> R[repo on this machine]

Becoming a Core is install plus setup; being one is a daemon supervised by systemd or launchd, listening on 8443, that the Panel dials — never the reverse.

In this section

• Operating a Core — the machine verbs: status, logs, start/stop, update, rotate identity, uninstall — and their Docker equivalents in a container.
• Harnesses — the vendor CLIs a Core can run, and how they get installed under the Core's user.

See also

• Concepts — Core, Task, Session, and the rest of the vocabulary.
• Create a Pairing Code — enroll clients on this Core.
• Environment Variables — ACTANA_PUBLIC_HOST, ACTANA_HOME, the metal layout.