OS service

BCCLI v0.4 does not ship a dedicated systemd unit or Windows service installer. There is nothing to enable, and nothing to be surprised by: supervision is your deployment's job, the same as for any other CLI process you schedule.

What to use instead

For scheduled or event-driven work, run one task per invocation:

bccli -p "task"

That process starts, does the work, and exits. A scheduler — systemd timer, cron, Task Scheduler, or your CI platform — is a better supervisor for this shape than a long-running daemon, because there is no state to keep alive between runs.

If you supervise it anyway

Wrap the command in whatever your platform uses natively and give it the same care as any agent process:

• Set the working directory explicitly; a service usually starts somewhere else than a shell does.
• Make sure credentials exist for the service user, not just for your own account.
• Capture stdout and stderr to a file you can read, or a failed run becomes invisible.
• Do not run it as root. The agent edits files with the privileges of the user it runs as.

What is not provided

No official unit file, no Windows service wrapper, and no built-in restart policy. Those exist so that each deployment can follow its own conventions rather than override ours.

Next

• Headless automation — installing and authenticating on a machine with no session.
• Remote security — if the supervised machine is reachable from outside.