Skip to main content

Autonomy Mode

Adjutant can operate on your behalf without real-time oversight. In autonomy mode, it queries your knowledge bases on a schedule, surfaces significant signals as Telegram notifications, and keeps a machine-readable log of every action it takes. You retain full control at all times via a filesystem kill switch and a hard notification budget.


1. What autonomy mode does​

The autonomous cycle has three tiers:

TierPromptCadencePurpose
Pulseprompts/pulse.mdConfigurable (default: 2×/day)Lightweight scan of all KBs — flag anything significant
Escalationprompts/escalation.mdTriggered by pulseDeep read of a flagged insight — decide whether to notify
Reviewprompts/review.mdConfigurable (default: 1×/day at 8pm)Thorough daily synthesis across all KBs, processes pending insights

What it never does without you:

  • Send notifications more than max_per_day times (hard budget check in send_notify())
  • Act during quiet hours (enforced in the notification layer)
  • Continue when PAUSED exists (checked first in every prompt)
  • Write anything real when debug.dry_run: true

2. Enabling autonomy​

Run adjutant setup. Step 7 "Autonomy Configuration" asks:

  1. Enable autonomous pulse checks? [y/N]
  2. Maximum notifications per day? [3]
  3. Enable quiet hours? [y/N]

If you answer yes to enabling, the wizard enables the autonomous_pulse and autonomous_review schedule entries (installing their crontab entries). The default schedules are weekdays 9am/5pm for pulse and weekdays 8pm for review.

Manually in adjutant.yaml​

notifications:
max_per_day: 3
quiet_hours:
enabled: false
start: "22:00"
end: "07:00"

Enable the schedule entries:

adjutant schedule enable autonomous_pulse
adjutant schedule enable autonomous_review

3. Configuring pulse cadence and review schedule​

Pulse and review schedules are managed as regular schedule entries in adjutant.yaml schedules:. See the Schedules guide for full documentation.

To change the schedule of autonomous_pulse:

# Disable current entry and remove it
adjutant schedule disable autonomous_pulse
adjutant schedule remove autonomous_pulse

# Add it back with a new schedule
adjutant schedule add
# Name: autonomous_pulse
# Description: Scheduled autonomous pulse check across knowledge bases
# Script path: .venv/bin/python -m adjutant pulse
# Schedule: 0 12 * * * ← your new schedule
# Log file: state/pulse.log

Or edit adjutant.yaml schedules: directly and run adjutant schedule sync.

Common schedule examples:

ScheduleCron expression
Weekdays 9am and 5pm (default)0 9,17 * * 1-5
Every 4 hours on weekdays0 */4 * * 1-5
Once daily at noon0 12 * * *
Weekday evenings at 8pm0 20 * * 1-5

4. Notification budget and quiet hours​

Hard budget​

notifications.max_per_day sets the daily ceiling. Once that many notifications have been sent, send_notify() raises BudgetExceededError — no further Telegram messages are sent for the rest of the calendar day regardless of what the LLM decides.

The counter resets at midnight (it is a date-stamped file: state/notify_count_YYYY-MM-DD.txt).

notifications:
max_per_day: 5 # increase for busier workflows

Quiet hours​

When enabled, the notification layer suppresses sends between the configured hours. The agent can still run pulses and reviews — it just will not deliver Telegram messages during those hours.

notifications:
quiet_hours:
enabled: true
start: "22:00"
end: "07:00"

5. Understanding the action ledger​

Every autonomous cycle appends a JSON line to state/actions.jsonl. This file is your machine-readable audit trail — you can grep it, tail it, or process it with jq.

Schema:

// Pulse completed
{"ts":"2026-03-05T09:00:00Z","type":"pulse","kbs_checked":["work","ml-papers"],"issues_found":[],"escalated":false}

// Notification sent
{"ts":"2026-03-05T09:00:01Z","type":"notify","detail":"[work] Sprint deadline approaching in 2 days."}

// Escalation processed
{"ts":"2026-03-05T09:00:02Z","type":"escalation","trigger":"2026-03-05-0900.md","action":"notified","project":"work"}

// Daily review completed
{"ts":"2026-03-05T20:00:00Z","type":"review","kbs_checked":["work","ml-papers"],"insights_sent":1,"recommendations":["Review sprint scope"]}

// Dry-run record (no side effects)
{"ts":"2026-03-05T09:00:00Z","type":"pulse","dry_run":true,"kbs_checked":["work"],"issues_found":[],"escalated":false}

The file is gitignored (covered by state/) and lives only on your machine.


6. Pausing and resuming​

adjutant pause        # creates PAUSED and disables managed schedules
adjutant resume # removes PAUSED and restores enabled schedules

adjutant pause creates PAUSED, removes only Adjutant-managed (# adjutant:) cron entries, and suppresses autonomous notifications. It leaves unrelated user cron entries untouched. adjutant resume removes PAUSED and rebuilds enabled managed entries from the schedule registry.

Do not create or remove PAUSED manually: that bypasses managed-cron reconciliation. Use adjutant pause and adjutant resume or their Telegram equivalents.

Via Telegram​

/pause    — creates PAUSED and disables managed schedules
/resume — removes PAUSED and restores enabled managed schedules
/status — shows current state

7. Dry-run mode​

Dry-run lets you test the full autonomous cycle with zero side effects:

debug:
dry_run: true

With this set:

  • All three prompts run their full logic
  • No files are written to insights/pending/
  • No notifications are sent
  • No state/last_heartbeat.json update
  • Every journal entry is prefixed [DRY RUN]
  • state/actions.jsonl records "dry_run":true so you can verify the cycle ran

Reset after testing:

debug:
dry_run: false

8. Reading the /status output​

adjutant status (or /status in Telegram) now includes an "Autonomous activity" section:

Adjutant is up and running.

Active jobs:
autonomous_pulse — Scheduled autonomous pulse check across knowledge bases, at 09:00 and 17:00, weekdays
autonomous_review — End-of-day synthesis and review, at 20:00, weekdays

Last cycle ran Mon 05 Mar at 09:00 (pulse).

No notifications sent today (limit is 3).

Recent actions:
Mon 05 Mar at 09:00 — pulse
Mon 05 Mar at 09:00 — notify

Fields:

  • Last cycle — type and timestamp of the most recent heartbeat (pulse/review/escalation)
  • Notifications today — current count vs. daily budget
  • Recent actions — last 5 entries from state/actions.jsonl, timestamp + type