Slack History → Living Status Docs

Move the channel's knowledge out of chat scrollback into one living status document per project, enforced by rules the agent follows and a scheduled watchdog that costs nothing to run.

Continuous, with scheduled checks

What was getting in the way.

An AI agent in a busy Slack channel re-reads an ever-growing conversation on every reply. The scrollback silently balloons until each answer costs dollars instead of cents — and nobody notices until the bill.

Context

Run across every project channel of an AI agent deployment at a marketing-services company.

How the work runs.

  1. 01

    One status doc per project channel

    Decisions, current state, next actions, maintained as plain text the agent owns.

  2. 02

    Read-first rule

    At every task start the agent reads the doc, not the chat history. The doc is the memory; scrollback is disposable.

  3. 03

    Write-back-before-reply rule

    Results and decisions land in the doc before the agent answers in channel, so the conversation can be reset at any moment with zero loss.

  4. 04

    Zero-cost watchdog

    A scheduled job measures actual cost per reply from usage logs (no AI involved) and posts an alert in the channel when a conversation crosses the spend threshold, prompting a write-back and a fresh start.

Evidence from the workflow.

Screenshot coming soon

Each system has a role.

  • Signal (channel conversations + alerts)

    Slack

  • Record of truth

    Plain-text status documents

  • Action (scheduled watchdog)

    Cron scheduler

  • Signal (cost per reply)

    Usage-log cost measurement

Why this is Operator.

Owns a workflow end to end, running the process inside the authority you set.

  1. 01

    The watchdog is read-only and alerts humans rather than acting; thresholds are set by the team; the status docs are human-readable and auditable at any time.

Impact / Outcomes

Replies that had crept past $1.50 each returned to cents after a reset.

Resetting the conversation became free and routine because nothing important lives in scrollback.

Context now survives restarts, new sessions, even agent upgrades.

← All use cases

Find where a workflow like this fits.

Start with the systems, work, constraints, and authority already present in your operation.