# Headless (/academy/headless)



Headless means the work happens and nobody has a window to screenshot.

Most software has a face: buttons, a dashboard, a page a judge can lean toward. **Headless** software keeps the part that does the job and skips the face. No monitor. No GUI. A [CLI](/academy/cli), a [worker](/academy/worker), a [server](/academy/server) in a warehouse. It wakes, does the [job](/academy/job), reports back in text.

The face was never the work. It was the front desk.

**Where the word shows up**

* **Headless browser.** Chrome with no window. It loads pages, clicks, fills forms. That's how an [agent](/academy/agent) reads a site or a [test](/academy/test) walks a flow faster than a human with a mouse.
* **Headless CMS.** The content lives in one place. The website is just one face that reads it. Same words can feed an app and a newsletter.
* **"Run it headless."** Skip the dashboard. Type the order. Get the result. The CLI version of a thing you'd normally click.

This is how automation actually runs. A nightly backup. A [cron](/academy/cron) that scores repos. An agent that files mail while you sleep. None of them need a person hitting refresh, so none of them need a screen.

[SSH](/academy/ssh) is often how you talk to a headless machine. The [builder](/builder) still gives you a face, because hackathon judges have eyes. If the important work is headless, give it a small face or a [log](/academy/log) they can read. A [process](/academy/process) with no URL is a magic trick you cannot demo.

Agents live here. They don't have hands for a mouse. They have sentences for a CLI. The same instinct as the phone on the kitchen wall: if you can type it, you can hand it over.

**What this unlocks**

A button needs a finger. A screen needs eyeballs. The second a task can run with neither, you can put it on a server, on a schedule, a hundred at a time, and not one of them needs a chair. Your demo still needs a face. The product can keep working after the face goes dark.