Collaboration

Shared Context

Shared context entries are workspace-wide knowledge items that all agents can access. Use them for team decisions, project guidelines, domain knowledge, or any information that should be available across all agent conversations.

Adding context

Each entry has a unique key, content, a category, and a priority score. Higher-priority entries are injected first when the context window is limited.

bash
# Add a shared context entry
curl -X POST http://localhost:3000/shared-context \
  -H "Authorization: Bearer ${JWT_TOKEN}" \
  -H "Content-Type: application/json" \
  -d '{
    "key": "api-design-guidelines",
    "content": "All new endpoints must use Zod validation, return consistent error shapes, and include OpenAPI annotations.",
    "category": "decisions",
    "priority": 100
  }'

# Response (201 Created)
{
  "entry": {
    "id": "ctx_abc123",
    "workspaceId": "ws_abc123",
    "key": "api-design-guidelines",
    "content": "All new endpoints must use Zod validation...",
    "category": "decisions",
    "priority": 100,
    "addedBy": "uid_alice",
    "createdAt": "2026-03-07T12:00:00.000Z"
  }
}

Categories

CategoryUse case
knowledgeDomain facts, reference material, technical specifications
decisionsArchitecture decisions, style guidelines, team agreements
projectsActive project context, sprint goals, milestones
generalDefault category for uncategorized entries

Listing and filtering

Entries are sorted by priority descending, then creation date ascending.

bash
# List shared context entries (optionally filter by category)
curl "http://localhost:3000/shared-context?category=decisions" \
  -H "Authorization: Bearer ${JWT_TOKEN}"

Removing context

bash
# Remove a shared context entry
curl -X DELETE http://localhost:3000/shared-context/api-design-guidelines \
  -H "Authorization: Bearer ${JWT_TOKEN}"

Defaults

FieldDefaultRange
categorygeneralknowledge, decisions, projects, general
priority00–1000
key—1–255 characters