-
Notifications
You must be signed in to change notification settings - Fork 4
CLI Extensions Verify
Runs every readiness check for one extension without changing anything.
ed extensions verify <id> [--json]
The human form prints the readiness phase, runtime phase, and summary followed
by every check, its status and its detail. A failed check prints a recovery
command when one is available. The JSON form contains id, title, verified,
state, checks, and remediation.
verified is true only when the extension is enabled and every required check
passes. False is a valid report and exits 0. Unknown extension ids exit 3.
Verification includes the extension's live adapter, so a valid preference and
running helper do not hide corrupt storage, a missing service, invalid
configuration, or an empty content source.
ed extensions verify quinjet
ed extensions verify calendar --json
ed extensions verify machines --json | jq '{verified, state, remediation}'
-
ed extensions setupto enable an extension and plan setup -
ed extensions doctorto diagnose the complete registry - Extension runtime detection for adapter inputs and recovery commands
-
ed extensions, the shared state and check contract - 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