Package Exports
- @sensegrep/cli
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@sensegrep/cli) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
@sensegrep/cli
Command-line interface for sensegrep semantic + structural code search.
Install
npm install -g @sensegrep/cliQuickstart
sensegrep index --root .
sensegrep status --root . # fast metadata-only stats
sensegrep status --root . --verify # freshness check
sensegrep search "error handling and retry logic"
sensegrep search emit --exact --no-shake --include "src/**/*.ts"
sensegrep search "request flow" --purpose understand --json
sensegrep show <result-id> --before 10 --after 20
sensegrep literal "TODO:" --filesystem --max-output-bytes 50000 --json
sensegrep audit "regression risks" --base origin/main --require-coverage --continue-uncovered --max-total-tokens 8000 --max-output-bytes 32000 --max-batches 8
sensegrep investigate "where is access blocked before payment?" --dry-run
sensegrep daemon start
sensegrep daemon call --tool search --arguments '{"query":"request flow","limit":5}'
sensegrep survey "authentication login token" --limit 4
sensegrep cluster "checkout payment order cart" --limit 4
sensegrep detect-duplicates --cross-file-only --timeout 30s
sensegrep semantic-kinds --jsonstatus, verify, search, graph, and literal open existing indexes read-only. If the table schema is old, they report schemaCompatible: false and recommend an atomic full rebuild; they never recreate the active table. Search JSON defaults to minified minimal cards. Use --json-detail content|diagnostic|full, --diagnostic, or --pretty to opt into heavier output. Audit --batch-tokens is a strict per-batch ceiling, including explicit split ranges from large files. Duplicate JSON omits code unless --show-code is set.
--json writes parseable JSON to stdout; progress and warnings are written to stderr.
Use --log-format none when a JSON command must suppress all non-fatal logs entirely.
If an --include/--exclude scope matches no indexed files, JSON output includes a
structured warning instead of failing silently.