Enable the Farther Shore Agent
Turn on the Operator, verify its work, inspect a run, and stop it safely.
Turn on the Operator, verify its work, inspect a run, and stop it safely.
The business's Operator is enabled, its state is observable, and you know how to inspect or stop it. The first run happens on the platform-managed cadence; enabling it does not synchronously force a run.
farthershore CLI with an authenticated sessionBUSINESS=<business-id-or-slug>
farthershore agents enable "$BUSINESS" --format json
Enabling schedules the Operator. It does not force an immediate run.
farthershore agents status "$BUSINESS" --format json
The status response should show enabled: true. A newly enabled Operator may
have no lastRunAt or recent runs yet. That is expected until its first cadence
window.
After a run appears, inspect its paper trail:
farthershore agents status "$BUSINESS" --format json
farthershore agents runs-show "$BUSINESS" <runId> --format json
Review these fields:
The Operator periodically studies the business and writes useful output to the Bulletin. It does not modify the repo or product contract. Customer-facing actions remain unavailable unless their separate platform gate is enabled.
| Symptom | Meaning | Recovery |
|---|---|---|
| No runs immediately after enable | Runs are scheduled, not forced by enable. | Wait for the cadence and check status again. |
needsAttention: true | Repeated failed or degraded runs triggered quarantine. | Inspect recent runs, then re-enable to acknowledge and clear it. |
An action receipt says denied | A config gate, payload, or exact permission check rejected it. | Treat the receipt as final; do not retry around governance. |
| The agent requests a product change | Product state is repo-owned. | Give the Bulletin request to the coding agent for a normal PR. |
Disable the Operator whenever you do not want new runs or further agent-work billing:
farthershore agents disable "$BUSINESS" --format json
farthershore agents status "$BUSINESS" --format json
Disabling is reversible and preserves history. Re-enable later with the same command used above. If a run is already executing, use status and its durable run record to confirm the terminal outcome; do not delete receipts or audit history.
Inspect the Farther Shore Agent for business <business-id-or-slug>.
1. Run `farthershore agents status <business> --format json`.
2. If it is disabled, report that fact and ask before enabling it.
3. If it is enabled, summarize the latest run status, usage, and errors.
4. Inspect the latest run with `farthershore agents runs-show`.
5. Separate Bulletin insights from executed platform-action receipts.
6. Never translate a product change request into an API mutation; make a repo PR.
7. If the Operator has `needsAttention`, explain the failed runs before re-enabling it.