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

How to map your services and runbooks for an agent with Open Index

Define doc_types like service and runbook, add entities with related_to edges, and index them.

Who it is forAn SRE who wants an incident agent to know which runbook belongs to which service.

The problemAgents guess at infrastructure relationships from scattered docs.

The outcomeA searchable brain where every service links to its runbooks.

What you need first

  • Python
  • Docker optionally, for a shared brain

Steps

  1. Start with open-index init my-brain
  2. Add a type with open-index add-doc-type customer --brain my-brain (use service for infra)
  3. Write entity JSON files under my-brain/entities with related_to edges
  4. Run open-index index --brain my-brain and open the UI

Prompt for your agent

Create an Open Index brain with doc_types service and runbook, add entities for <services>, index it, and list each service's runbooks. Confirm every service has at least one edge.

Caveat. With storage: file the Git files are the source of truth; the default index storage is DB-owned.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for DrDroidLab/open-index and "Map your services and runbooks for an agent"

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