Reference

summarize daemon

summarize daemon

summarize daemon <subcommand> [options]

Manages the local HTTP daemon that the Chrome / Firefox Side Panel talks to. The daemon binds to 127.0.0.1 only and requires a shared bearer token. It autostarts via the right service manager for your platform.

PlatformService
macOSLaunchAgent (launchd)
Linuxsystemd user service
WindowsScheduled Task

If you only use the CLI, you don't need any of this.

#Subcommands

#install

Install or upgrade the autostart service and write ~/.summarize/daemon.json.

summarize daemon install --token <TOKEN>
summarize daemon install --token <TOKEN> --port 8787
summarize daemon install --token <TOKEN> --dev    # repo dev mode

--token <token> is required on first install; the extension prints one after pairing. Re-running install with a new token adds another paired browser instead of invalidating the old one.

#restart

Restart the autostart service. Useful after upgrading summarize or editing daemon.json.

summarize daemon restart

#status

Probe the autostart service and the running daemon's health endpoint.

summarize daemon status

#uninstall

Unload the autostart service. On macOS the plist is moved to Trash so you can undo.

summarize daemon uninstall

#run

Run the daemon in the foreground. The autostart entry uses this internally; use it directly inside containers, on systems without launchd/systemd, or while debugging.

summarize daemon run --port 8787

#Options

--port <n> : TCP port. Default 8787. The Side Panel reads it from ~/.summarize/daemon.json.

--token <token> : Bearer token. Required for install. Stored in ~/.summarize/daemon.json (mode 0600).

--dev : Install a service that runs src/cli.ts via tsx from the current repo. Useful while hacking on the daemon — don't ship it to users.

#HTTP endpoints

The daemon is documented in detail in Chrome extension and Agent / daemon. At a glance:

  • POST /summarize/execute — start a run. Bearer-auth required. Streams progress + final summary.
  • GET /session/{id}/status — poll an in-progress run.
  • GET /health — health probe (used by status).

#Files

~/.summarize/daemon.json : Token, port, paired browser fingerprints. Mode 0600.

~/.summarize/daemon.log : Rolling log written by the autostart service.

#Notes

  • Containersinstall starts the daemon for the current container session but does not register a Scheduled Task / unit. Run summarize daemon run from your entrypoint instead, and publish port 8787 so the host browser can reach it.
  • Token rotation — running install --token <NEW> adds a new paired browser; old browsers keep working. Edit daemon.json by hand to revoke.
  • Multiple installs — only one daemon per user. Reinstall to upgrade.

#See also