synapse-usage

synapse-usage Skill

Use the th0th Synapse cognitive modulation layer to get focused, low-noise retrieval during multi-step coding tasks. Synapse does not replace th0th_search or th0th_optimized_context — it modulates which results survive and in what order based on session context, task alignment, agent affinity, intent, recency, and result diversity.

When to Apply

Activate Synapse whenever the same task will issue more than one search in the same conversation:

• Multi-step debugging (error → handler → config)
• Code review (PR → history → tests)
• Refactor across files (usages → definitions → tests)
• Onboarding to a new module (entry point → calls → decisions)
• Any prolonged session where the same files/concepts will reappear

Skip Synapse for one-shot lookups; the overhead does not pay back.

Interface

Synapse is exposed via the tools-API at http://localhost:3333/api/v1/synapse/... (no MCP tools yet). All interaction is curl against six endpoints:

Endpoint	Purpose
POST /api/v1/synapse/session	Create a session, returns sessionId
GET /api/v1/synapse/session/:id	Inspect session state
PATCH /api/v1/synapse/session/:id	Update task context (refreshes TTL)
DELETE /api/v1/synapse/session/:id	End session
POST /api/v1/synapse/session/:id/prime	Seed buffer with known-relevant entries
POST /api/v1/synapse/session/:id/access	Record access for agent-affinity scoring
POST /api/v1/synapse/session/:id/prefetch	Plan + execute prefetch on file open
GET /api/v1/synapse/sessions	List active session count (debug)

Search integration: pass synapseSessionId on POST /api/v1/search/project (the th0th_search MCP tool maps to this endpoint).

Lifecycle (the five moves)

1. Open a session at task start

SID=$(curl -sS -X POST http://localhost:3333/api/v1/synapse/session \
  -H 'Content-Type: application/json' \
  -d '{
    "agentId":"claude-code",
    "taskContext":"investigating ECONNRESET errors in auth middleware under load",
    "enableBuffer":true
  }' | jq -r .data.sessionId)