xynthis corpus add indexes file content: chunks of code and prose that recall can retrieve by meaning. xynthis code scan extracts structure: a typed knowledge graph of functions, classes, imports, and call edges. Use both on a repo you work in daily.
Indexing content: corpus add
--ast or --regex.
Ingestion streams: files are read and chunked in windows of 64 paths at a time, ingested in batches of 128, so peak memory stays proportional to the window rather than the corpus. Chunks are deduplicated by BLAKE3 hash, which is what makes re-indexing cheap: unchanged content is skipped, not re-embedded.
The caps, and what falls outside them:
By default the folder is watched after indexing, so edits re-ingest automatically. Pass
--no-watch to skip that, or toggle later with xynthis corpus watch <name> on|off.
Give each collection a one-line description of what it is; recall uses it to route queries to the right corpus:
Managing collections
Scanning structure: code scan
code:contains_fn, code:contains_class, code:imports, code:imported_by, code:defined_in, and code:calls (call sites resolved cross-file through a symbol table).
Re-scans are incremental: each file’s extraction is cached keyed by a BLAKE3 content hash, so an unchanged file is replayed from cache instead of re-parsed. After a big refactor, pass --replace to wipe the previous scan’s triples before ingesting, which also drops that repo’s cache entries.
Defaults are 10,000 files and 50,000 triples per scan; raise them with --max-files and --max-triples (the summary warns when the triple cap was hit). --label overrides the repo name baked into entity ids, which otherwise defaults to the path basename.
What recall can answer afterward
Recall is layered: it consults the knowledge graph and the corpus chunks in the same query, so both kinds of code knowledge surface together.code:<label>::<relative-path>, and the kg_query MCP tool queries them directly if you are wiring your own client. In chat, you just ask; the agent routes to recall and the graph itself.