# AI use cases for Kyb (alex09x/kyb) Repo: [alex09x/kyb](https://github.com/alex09x/kyb) | Use cases: 4 | Page: https://dedupedai.com/use-cases/alex09x-kyb/ KYB is a git-backed, searchable shared memory and incident tracker that AI agent fleets can use through a CLI, HTTP API and MCP server. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Give every agent one shared record of your infrastructure: https://dedupedai.com/use-cases/alex09x-kyb/shared-infra-memory-for-agent-fleet/ - Log an outage with its fix so the next one is faster: https://dedupedai.com/use-cases/alex09x-kyb/record-incident-with-resolution/ - Track which agent holds each task and what it waits on: https://dedupedai.com/use-cases/alex09x-kyb/hand-off-tasks-between-agents/ - Check what the knowledge said before a change: https://dedupedai.com/use-cases/alex09x-kyb/reconstruct-what-the-base-said-on-a-date/ ## How to give every agent one shared record of your infrastructure with Kyb Repo: [alex09x/kyb](https://github.com/alex09x/kyb) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Store server layout, service wiring and deploy steps once so each agent finds them instead of rediscovering them. **Who it is for:** An engineer running Claude Code, Codex or other agents on several machines who keeps re-explaining the same servers and services to each new session. **The problem:** Agents forget everything between sessions and rediscover the same infrastructure, and lessons from past work disappear when the context window closes. **The outcome:** Agents query one shared, versioned knowledge base before acting, and facts they write are searchable by every other agent. ### Steps 1. Install the server with `cargo install knowyourbusiness --locked`. 2. Start it with `kyb-server` and leave it running on 127.0.0.1:9310. 3. Install the client skill with `bash skills/install.sh` from the repository checkout. 4. Query before acting with `kyb query "nats streams"`. 5. Record a new fact with `kyb add --key nats-streams --title "..." --tags nats,infra`, then check it with `kyb history nats-streams`. ### Prompt to paste into your agent ```text Use the KYB repo at alex09x/kyb. Run `kyb query ""` against the local server and summarise the matching entries for . Expected output: a short list of keys with titles. Verify that each key returned exists by running `kyb get ` on one of them. ``` ### Caveat The README says secrets are rejected on write, but you should still store pointers to credentials rather than the credentials themselves. Risk, credentials: With KYB_AUTH left at off, anyone who can reach the listening address can write to the base, so bind to a trusted interface and set up a token book before sharing it. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/alex09x-kyb/shared-infra-memory-for-agent-fleet/ ## How to log an outage with its fix so the next one is faster with Kyb Repo: [alex09x/kyb](https://github.com/alex09x/kyb) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Capture what broke, the affected windows and how it ended as a searchable incident report. **Who it is for:** An on-call engineer or agent handling a production incident who wants the fix findable the next time the same failure happens. **The problem:** Incident lessons evaporate when the session ends, so the same failure gets debugged from scratch. **The outcome:** A structured incident report with a detection check, affected windows and a resolution that agents can search later. ### Steps 1. Print the report skeleton with `kyb incident --template`. 2. Create the report with `kyb incident --key inc-2026-07-22-orders-api-oom --title "..." --service orders_api --severity high`. (inferred, check the README) 3. Add a detection check with `--detection "check + healthy result"` and affected windows with `--affected` as a JSON list of scope, from and to. 4. Link related knowledge entries with `--knowledge ` and list hosts with `--hosts `. (inferred, check the README) 5. Check the record and its history with `kyb history inc-2026-07-22-orders-api-oom`. (inferred, check the README) ### Prompt to paste into your agent ```text Use the KYB repo at alex09x/kyb. Create an incident report for using `kyb incident` with the key inc---. Expected output: the server reply, including any hints about missing parts. Verify that the reply has no missing-field hints, or list the hints you still need to fix. ``` ### Caveat The README says closing an incident requires a resolution and archives it, so plan to write the resolution before you close it, not after. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/alex09x-kyb/record-incident-with-resolution/ ## How to track which agent holds each task and what it waits on with Kyb Repo: [alex09x/kyb](https://github.com/alex09x/kyb) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Share task status, owners and blockers across agents so work is not picked up twice or lost. **Who it is for:** A lead engineer splitting work across several agents on different machines who needs a shared view of open, blocked and finished tasks. **The problem:** Agents working in separate sessions cannot see who is doing what, so tasks get duplicated or dropped without a recorded outcome. **The outcome:** A shared task list with owners, blocked reasons and recorded outcomes, visible to every agent connected to the server. ### Steps 1. Run the server with `kyb-server` and confirm the client reaches it. 2. List the live work with `kyb tasks`. 3. Move a task to blocked or in progress with `kyb task-status`, setting an assignee and a blocked reason when needed. 4. Close a finished task with `kyb done`, giving the outcome as the resolution. 5. Review who held a task and when with `kyb history `. (inferred, check the README) ### Prompt to paste into your agent ```text Use the KYB repo at alex09x/kyb. Run `kyb tasks` and list the tasks with status blocked and their blocked_reason. Expected output: one line per blocked task. Verify each reason by opening the task with `kyb get `. ``` ### Caveat The README notes that terminal statuses done and dropped require a resolution, so a task cannot be closed with a bare status change. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/alex09x-kyb/hand-off-tasks-between-agents/ ## How to check what the knowledge said before a change with Kyb Repo: [alex09x/kyb](https://github.com/alex09x/kyb) | Difficulty: Advanced | Time: 1 hour 15 minutes | Basis: From the README Query the base as it stood on a past date and diff an entry to see what moved. **Who it is for:** An engineer debugging a regression who needs to know which infrastructure facts were true when the problem started. **The problem:** Current documentation hides what was true last week, so it is hard to tell whether a change in the base caused a failure. **The outcome:** A snapshot of the knowledge base at a chosen date and a diff of one entry between versions. ### Steps 1. Query the snapshot with `kyb query "nats streams" --as-of 2026-08-01`. 2. List what changed in a window with `kyb query "" --changed-between 2026-08-01,2026-08-07`. 3. Diff one entry with `kyb diff nats-streams`. 4. Export every key at one commit with `kyb export --out kyb.jsonl` if you need a full copy. ### Prompt to paste into your agent ```text Use the KYB repo at alex09x/kyb. Run `kyb query "" --as-of ` and report the entries that were current on that date. Expected output: a list of keys with the version that was active. Verify one result by running `kyb diff ` and confirming the change dates. ``` ### Caveat The README says the CLI refuses these time queries if the server is too old, so confirm the server version through /healthz before relying on the answer. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/alex09x-kyb/reconstruct-what-the-base-said-on-a-date/