-
Notifications
You must be signed in to change notification settings - Fork 4
CLI Companion Entities
The people, projects, places, organisations and other named things the companion has resolved, each with every spelling it has seen. Embeddings smear proper nouns, so entities are what keep one person from becoming two.
Usage:
ed companion entities [--limit <n>] [--json] [--endpoint <url>]
Aliases span scripts deliberately. A name in Devanagari, the same name romanised and the two ways you habitually misspell it resolve to one entity, which is where multilingual retrieval otherwise dies. Retrofitting that means re-resolving the whole graph, so it is done at extraction time.
--json shape: an array of {id, kind, canonicalName, aliases, mentionCount, firstSeen, lastSeen}.
Kinds are person, project, place, organisation and thing. --limit
defaults to 30 and must be positive.
Entities are also a retrieval channel: a question that names one walks from the entity to the episodes that mention it, alongside vector and keyword search.
-
ed companion search, the channels these feed -
ed companion, the rest of this group - All
edcommands
Auto-generated from docs/, edit the docs in the repo, not the wiki.
CLI reference
Companion
- Deploy
- Concepts
- Concepts Memory
- Concepts Ingestion
- Concepts Search
- Concepts Chat
- Concepts Learning
- Concepts Brain
- Concepts Friend
- Hosts
- Stack
- Status
- Doctor
- Search
- Index
- Ingest
- Episodes
- Sync
- Observations
- Reflect
- Beliefs
- Ask
- Extract
- Claims
- Corroborate
- Runs
- Chat
- Conversations
- Forget
- Export
- Import
- Erase
- Wipe
- Episode
- Nightly
- Reason
- Personas
- Council
- Lenses
- Core
- Why
- Hypotheses
- Predictions
- Commitments
- Discrepancies
- Calibration
- Inquire
- Entities
- Eval
- Standup
- Machines
- Baselines
- Connectors
- Facts
- Correct
- Weekly
- Db
Guides