Configuration is not editable from a browser, and there is no endpoint that would make it
so. Reading and writing configuration over the network is how an installation gets
repointed at a different data directory by something holding a key, so
config get and config set stay on the command line and the MCP
tool — the two surfaces a person is at.
manicule config show manicule config set rag.profile precise
What follows is the installation's posture as doctor and the index report it:
live facts about this process, not a rendering of the file.
{{ m.state(panels.doctor.data.state) }}
| Check | State | Detail |
|---|---|---|
| {{ check.name }} | {{ m.state(check.state) }} | {{ check.detail }} |
{{ panels.index.data.data_dir }}{{ panels.index.data.embed_fingerprint or 'none — the index will accept whatever the first ingest brings' }}{{ panels.index.data.chunk_fingerprint or 'none' }}{{ vectors.index_name }},
{% set partitions = vectors.num_partitions if vectors.num_partitions is not none else 'unknown' %}
{% set metric = vectors.distance_metric if vectors.distance_metric is not none else 'unknown' %}
{{ vectors.index_type if vectors.index_type is not none else 'unknown type' }} over
{{ partitions }} partition(s), {{ metric }} distance,
{{ vectors.unindexed_rows }} row(s) not yet indexed
{% endif %}
{% if vectors.detail %}manicule vector-checksum --yes
{% endif %}
The fingerprints are shown in their canonical form. A prettied identity is one nobody can compare, and comparing them is the only thing they are for.
{% else %}{{ m.failed(panels.index) }}{% endif %}Each of those is absent from the HTTP API by name, with a test asserting the absence. This surface adds no operation of its own, so it inherits every one of them.