DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to give every agent one shared record of your infrastructure with Kyb

Store server layout, service wiring and deploy steps once so each agent finds them instead of rediscovering them.

Authorization notice. Kyb is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

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.

Who it is forAn 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 problemAgents forget everything between sessions and rediscover the same infrastructure, and lessons from past work disappear when the context window closes.

The outcomeAgents query one shared, versioned knowledge base before acting, and facts they write are searchable by every other agent.

What you need first

  • A Rust toolchain with cargo, to run cargo install knowyourbusiness --locked
  • A host or Docker setup where the kyb-server process can keep its data directory
  • Network access from agent machines to the server port, default 127.0.0.1:9310
  • Optional: a model directory with model.onnx and tokenizer.json for hybrid search; without it the server runs lexical-only

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 for your agent

Use the KYB repo at alex09x/kyb. Run `kyb query "<topic>"` against the local server and summarise the matching entries for <topic>. Expected output: a short list of keys with titles. Verify that each key returned exists by running `kyb get <key>` 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.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for alex09x/kyb and "Give every agent one shared record of your infrastructure"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer