Background Service

Background Service

Register Codori as a background service so it starts with the host:

codori service install
codori service start
codori service stop
codori service status
codori service uninstall

Every verb except install resolves its target from the recorded install under ~/.codori/services/, so they work from any directory. Pass --root only when more than one service is registered.

Scopes and platforms

A user-scoped install uses a launchd agent on macOS, a systemd user unit on Linux, and a Task Scheduler logon task on Windows. --scope system registers a machine-wide equivalent and requires elevation.

The served project root can be changed at runtime from Settings → General, and the most recently served directory is reused the next time the service starts.

See packages/server/README.md for the platform details, root persistence, deterministic macOS install identifiers, automatic Tailscale policy, and update behavior.

Tailscale under a service

Installed services follow the same automatic Tailscale Serve policy as direct launches, described in Remote Access. Writing a Serve config needs root or a Tailscale operator, so grant the service account ongoing control once:

sudo tailscale set --operator=$USER

Linux notes

For an nvm-installed CLI under sudo, use:

sudo --preserve-env=PATH "$(command -v codori)" service install --scope system --root ~/Project

Plain sudo codori can be missing from the sudo secure_path, and an absolute script can still select an older /usr/bin/node through #!/usr/bin/env node.

Environment changes

Installed services use their own effective PATH, so restart the service after changing anything that affects which Codex executable it resolves. See Configuration for the resolution order.