Skip to content

[docs] Update README to accurately describe Soma embedding-free path#20

Open
szabta89 wants to merge 1 commit into
mainfrom
docs/update-soma-cost-and-description-2026-07-24-d1b1df27c1baa379
Open

[docs] Update README to accurately describe Soma embedding-free path#20
szabta89 wants to merge 1 commit into
mainfrom
docs/update-soma-cost-and-description-2026-07-24-d1b1df27c1baa379

Conversation

@szabta89

Copy link
Copy Markdown
Contributor

The README.md had two places that implied Repo Mind Light always computes embeddings:

  1. "What Repo Mind Light Does" — said "It also uses embeddings and a generative model to synthesize a final answer", which is inaccurate when the Soma backend is active.
  2. "Cost And Model Considerations" — listed "computes embedding vectors during indexing and refresh" as a blanket cost, and said the CAPI token is needed "for embeddings and answer generation", without acknowledging the Soma path.

Changes

  • Updated the high-level description to note that with Soma, embedding-API calls are skipped; with GraphRAG Zero (default), embeddings are still computed.
  • Rewrote the cost section to distinguish the two backends, and clarified that a CAPI token is still required for answer generation and query rewriting even when embeddings are not used.

This aligns the packaging repo README with the source repo's documentation, which documents that graph_rag_zero: null + soma: {} skips all embedding-API calls during both indexing and querying.

Generated by Repo Mind Light AW Documentation Updater · ● 13.7M ·

  • expires on Jul 31, 2026, 10:03 AM UTC

With the Soma backend, embedding-API calls are skipped entirely during
indexing and querying. The README's 'What Repo Mind Light Does' and
'Cost And Model Considerations' sections previously implied embeddings
are always computed. Update both sections to accurately describe the
embedding-free Soma path while noting that a CAPI token is still
required for answer generation and query rewriting.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant