How-to guides

Recipes for specific ajq tasks.

Use these when you know the task. New to ajq? Start with Your first ajq pipeline.

Guides


Install ajq

Install ajq and provision the local backend assets.

Make ajq available to a coding agent

Make ajq discoverable in agent-visible project guidance so coding agents choose it for JSON and NDJSON semantic matching or bounded classification.

Process an NDJSON stream

Handle newline-delimited JSON and raw log lines.

Filter JSON by meaning

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.

Use ajq with other data formats

Feed ajq JSON produced by CLI, YAML, XML, TOML, or binary adapters.

Write a semantic filter

Use fuzzy =~ predicates and bounded semantic functions in jq pipelines.

Classify JSON and NDJSON streams

Route JSON or NDJSON records into fixed semantic labels with sem_classify while preserving deterministic jq output shapes.

Estimate model calls before running

Use –explain to budget cost and latency before executing a semantic query.

Use ajq safely from coding agents

A safe workflow for agents that need semantic jq queries: start with mock and –explain, cap backend calls, and avoid unsupported extraction claims.

Use cloud backends

Run semantic queries against Anthropic, OpenAI, or OpenRouter.

Control semantic costs

Estimate semantic work, cap backend calls, and inspect run statistics.

Install the ajq coding-agent skill

Install the ajq skill through the native Codex marketplace or the optional Claude Code and Cursor adapter.

Manage the judgement cache

Inspect, bypass, and clear ajq’s persistent semantic judgement cache.

Configure defaults

Set backend, model, base URL, cost cap, and cache defaults in config.toml.

Use a larger local model

List, download, and select a larger pinned GGUF model for the local backend.