Conversation management service for agents, conversations, messages, resources, vectors, tools, prompts, and search.
- index.js: standalone HTTP entrypoint
- app.js: application interface used by direct callers
- service.js: local composition
- http.js: shared HTTP composition root
- remote.js: HTTP client for remote mode
- core/: conversation-service and domain logic
- http/: route families and HTTP helpers
- scripts/: operational scripts such as vector reindexing
The service root shows the runtime boundary; the capability code is grouped under core/ and http/.
Standalone CMS mounts its routes under /api/v1.
Route families:
- agents:
/agents - conversations and summaries:
/conversations,/summarize - messages:
/conversations/:conversationId/messages,/messages/:id - resources:
/resources,/agents/:agentId/resources,/conversations/:conversationId/resources - vectors and search:
/vectors,/resources/:resourceId/vectors,/search/messages,/search/vectors,/search/chunks - tools and prompts:
/tools,/prompts
server mounts the same shared CMS routers for the public API, with browser/session-aware request context in front of them.
server composes CMS in-process through cms/service.js. This is the simpler local path.
Set CMS_URL for server, or run standalone CMS directly. The edge server will use cms/remote.js, while the service serves cms/http.js.
From the repo root:
npm start -w cmsThe standalone service defaults to port 3002.
PORTGATEWAY_URLPGHOST,PGPORT,PGDATABASE,PGUSER,PGPASSWORDDB_STORAGEDB_SKIP_SYNC
- The old root-level
conversation.jsshim is gone. The underlying service implementation now lives at core/conversation-service.js. cms/http.jsis only the composition root now; the actual route families live in http/.- If docs drift again, trust http.js, core/conversation-service.js, and the route tests under server/test/routes.