Knowledge Hub

The HQ Knowledge Hub

Plain-English guides to HQ, from your first install to rolling it out across your whole team.

On this page

Teams & Cloud

Outposts: Your Always-On HQ Computer

5 min read Updated Nov 2026

Anyone who wants HQ to keep working when their laptop is closed: scheduled jobs, overnight checks, or a small app that stays online. Company owners and admins setting up a company Outpost.

An Outpost is a computer in the cloud that runs HQ for you. It stays on, so the jobs you give it keep running on schedule even when everyone's laptop is closed. You might have it write a summary of new support tickets every morning, check a dashboard every hour, or host a small app.

There are two kinds:

Personal OutpostCompany Outpost
Who it's forYouYour whole company
Who sets it upYouA company owner or admin
Who adds jobsYouOwners and admins. Members can see the jobs but can't change them.

You can set one up by asking in Claude Code or Codex, or from the HQ console. Owners and admins can also add a company Outpost in the desktop app. A company can have up to 5 Outposts.

Before you start#

  • HQ installed and signed in, with Claude Code or Codex. See Using HQ with Claude Code.
  • An up-to-date HQ. Company Outposts need a recent version of HQ's command-line tool. If HQ says your version is too old, update HQ and try again.
  • Outposts are a paid add-on, billed monthly. HQ asks you to confirm the charge before it creates one. See HQ's pricing page for current prices.

Setting up a personal Outpost#

In Claude Code or Codex, say:

  • "Set up a personal Outpost for me."

HQ asks which coding tool the Outpost should use (Claude Code or Codex), shows you the monthly charge, and waits for your okay. Then it creates the Outpost.

Scheduling jobs on your personal Outpost#

Use /schedule, or just describe the job:

  • "Every weekday at 9am, have my Outpost summarize new support tickets and DM me."
  • /schedule list to see your jobs.

HQ asks a few short questions, one at a time: which company the job is for, which secrets it needs (by name only), how long it can run, and where to send alerts. Then it repeats the schedule back in plain words so you can confirm it. Alerts arrive as HQ messages.

If you don't have an Outpost yet, /schedule offers to set one up first.

You can also pause a job, turn it back on, run it once now, or remove it:

  • "Pause my morning ticket summary." / "Run it once now."

Setting up a company Outpost#

A company owner or admin sets this up once for the whole company. In Claude Code or Codex, say:

  • "Create a company Outpost for Acme."

HQ shows the monthly charge and waits for your okay. Setup takes about 7 minutes. Then you sign the Outpost in to one Claude account that the company's jobs will share.

In the desktop app, open your company, then Settings → Outposts. Owners and admins can click Add Outpost, and use Add a job, Edit, Pause, Resume, Run now, and Remove on company jobs. Members can see them.

Adding company jobs#

Owners and admins can add, change, pause, and remove company jobs:

  • "Add a company job on the Acme Outpost that writes a pipeline summary every Monday at 8am New York time."
  • "Pause the Monday summary." / "Run it once now."

A job can run:

  • On an interval, every 5 minutes or longer.
  • At set times, like weekdays at 9am, in the time zone you choose.
  • Once, at a set date and time.

Each job writes its results as files on the Outpost. To see them on your computer, ask HQ to sync.

If a job needs a company secret, like an API key, share that secret with the company Outpost first. It gets read access only. See the Secrets Guide.

Checking on company jobs#

Ask:

  • "How are the Acme Outpost jobs doing? Any missed runs?"

Each job shows a health state:

StateWhat it means
Waiting for first runIt hasn't run yet.
Ran on timeIt ran on time.
MissedIt didn't finish successfully within its time limit.
Out of dateIt ran, but didn't update its results file.
BlockedSomething is stopping it from running.
PausedSomeone paused it.
UnknownHQ can't tell yet.

Recent runs and their results also show in the desktop app.

Alerts. Every owner and admin gets an HQ message when a job misses a run, when a run finishes without updating its file, or when the Outpost stops checking in. They get another message when it recovers. See Messaging in HQ.

Hosting an app on your Outpost#

An Outpost can also serve a small website or app and give you a public link. On the Outpost, run /outpost-host. It asks for a name, and whether you're serving a folder of files or an app that's already running. Before it publishes, it checks that you really want the app to be public.

For others to reach it, the app's port has to be opened on the Outpost's firewall. If you're not sure how, ask the HQ team.

To share pages and apps without an Outpost, use /deploy instead. See Sharing Your Work.

In the desktop app#

Click Outpost on the left rail to see your personal Outpost's status. Open console opens it in the HQ console. If you don't have one yet, Set one up opens the HQ console.

Good to know#

  • Company Outposts use Claude. Choosing Codex or a custom disk size only applies to personal Outposts.
  • Alerts come as HQ messages, not Slack or email.
  • Members can view company jobs but can't change them. Ask an owner or admin.

Common questions#

What's the difference between an Outpost and a cloud bot?

A cloud bot is an AI teammate you talk to in HQ, Slack, or email. An Outpost is a computer that runs scheduled jobs and can host apps. See Cloud Bots.

Do company jobs stop if the person who set them up leaves?

No. Company jobs run as the Outpost, so they keep running. All of the company's owners and admins can manage them, and alerts go to every current owner and admin.

Can a company have more than one Outpost?

Yes, up to 5.

If you get stuck#

See The "I'm Stuck" Guide, or report it with /hq-bug. It packages the details for the team automatically.