Skip to content

Subgraphs

Subgraphs are curated collections of entities from your knowledge graph. They help you organize related knowledge for specific projects, topics, or synthesis tasks.

Your knowledge graph can grow large with entities from many projects and time periods. Subgraphs let you:

  • Focus - Isolate relevant knowledge for a specific task
  • Organize - Group entities by project, team, or topic
  • Synthesize - Generate documents from curated knowledge
  • Share - Create reusable knowledge collections

Let TeamLoop find relevant entities:

teamloop_create_subgraph:
name: "Auth System Decisions"
description: "All decisions related to authentication"
query: "authentication and authorization"
limit: 30

Include exact entities by ID:

teamloop_create_subgraph:
name: "Q4 Architecture Review"
description: "Entities for Q4 2024 architecture review"
entity_ids:
- "uuid-1"
- "uuid-2"
- "uuid-3"
teamloop_get_subgraph:
subgraph_id: "subgraph-uuid"
teamloop_get_subgraph:
name: "Auth System Decisions"

Discover connected entities you might have missed:

teamloop_expand_subgraph:
subgraph_id: "subgraph-uuid"
depth: 1

Finds entities one relationship hop away from current members.

teamloop_expand_subgraph:
subgraph_id: "subgraph-uuid"
depth: 2
include_types: ["DECISION", "COMPONENT"]

Only include specific entity types.

teamloop_expand_subgraph:
subgraph_id: "subgraph-uuid"
depth: 1
auto_add: true

Automatically add found entities to the subgraph.

Create subgraphs for specific projects to gather all relevant decisions and context.

Gather all relevant decisions for a review, then expand to find related components.

Create subgraphs per team to organize domain-specific knowledge.

After an incident, gather relevant knowledge to understand what led to the issue.

Subgraphs are the input for document synthesis:

  1. Create focused subgraph
  2. Expand to include related context
  3. Generate ADR, PRD, or brief

Use clear, specific names like “Q4 2024 Database Scaling Decisions”.

Begin with a narrow query, review results, then expand selectively.

The best subgraphs have 10-50 entities, include multiple entity types, and cover the topic thoroughly.

Add description for future reference.

  • Subgraphs are user-scoped (personal to your account)
  • Maximum 50 entities per query-based creation
  • Expansion limited to 3 hops
  • Names should be unique per user