---
name: keep-per-client-decision-notes-ready-for
description: "Resume client work without re-explaining past choices. Maintain a separate decision and context log for each client or project so an agent can pick up a new session, recall agreed rules, and avoid repeating rejected approaches."
license: CC-BY-4.0
compatibility: "Needs access to: Docs, Notes, GitHub."
metadata:
  author: "BotBento Editorial"
  version: "2026-11-09"
  source: "https://botbento.com/usecases/keep-per-client-decision-notes-ready-for/"
  kind: workflow
  hermes:
    tags: ["context", "client-work", "decision-log", "agents"]
    category: ops
---
# Keep per-client decision notes ready for agent sessions

Resume client work without re-explaining past choices

## When to use

Maintain a separate decision and context log for each client or project so an agent can pick up a new session, recall agreed rules, and avoid repeating rejected approaches. The bot reads recent project notes, updates a running brief, and surfaces open questions before work resumes.

## Steps

1. When something happens: New client session starts
2. Draft per-client context brief
3. Decision brief ready for review

## Instructions

For each client or project, keep a separate running note of agreed rules, past decisions, rejected approaches, and open questions. When a session begins, read the latest notes, summarize what matters for the current task, and flag conflicts or missing context. Draft updates to the notes and a short brief for the user. Do not send messages, make payments, or delete notes without the user's approval.

## Source

Summarized in our own words from [Ask HN: How do you manage your AI agents' context across clients and projects?](https://news.ycombinator.com/item?id=50403153) (Hacker News, checked 2026-11-09). Any results described there are the authors’ own.

From the BotBento use-case directory: https://botbento.com/usecases/keep-per-client-decision-notes-ready-for/. Licence: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/).
