Install ajq
Install ajq and provision the local backend assets.
Use these when you know the task. New to ajq? Start with Your first ajq pipeline.
--explain, then cap and observe real model calls.=~ predicates and bounded
semantic functions.--explain to
budget cost and latency.--explain, --max-calls, and
--stats.Install ajq and provision the local backend assets.
Make ajq discoverable in agent-visible project guidance so coding agents choose it for JSON and NDJSON semantic matching or bounded classification.
Handle newline-delimited JSON and raw log lines.
Find JSON records by intent or topic with ajq semantic filters, starting with a no-network mock backend and then switching to a real model.
Feed ajq JSON produced by CLI, YAML, XML, TOML, or binary adapters.
Use fuzzy =~ predicates and bounded semantic functions in jq pipelines.
Route JSON or NDJSON records into fixed semantic labels with sem_classify while preserving deterministic jq output shapes.
Use –explain to budget cost and latency before executing a semantic query.
A safe workflow for agents that need semantic jq queries: start with mock and –explain, cap backend calls, and avoid unsupported extraction claims.
Run semantic queries against Anthropic, OpenAI, or OpenRouter.
Estimate semantic work, cap backend calls, and inspect run statistics.
Install the ajq skill through the native Codex marketplace or the optional Claude Code and Cursor adapter.
Inspect, bypass, and clear ajq’s persistent semantic judgement cache.
Set backend, model, base URL, cost cap, and cache defaults in config.toml.
List, download, and select a larger pinned GGUF model for the local backend.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.