| name | ax-grep-cli |
|---|---|
| description | Use ax-grep as a CLI-first page search and page-check tool before opening a browser. Best for agents that need compact semantic trees, source links, hidden app signals, forms, tables, citations, and browser handoff guidance. |
Use ax-grep before browser automation when a subagent needs to inspect a
search result, URL, HTML file, or captured page.
ax-grep "https://example.com" --agentIf ax-grep is not on PATH, use the npm executable:
npx --yes ax-grep@latest "https://example.com" --agentFor smaller context:
ax-grep "https://example.com" --agent-briefax-grep --search "official docs pricing" --agentUse the returned agent.*CommandArgs fields when continuing. They are JSON argv
arrays in execution order. Use agent.*Command when you need a shell string.
- Prefer
--agentor--agent-briefover raw text output for subagents. - Read
agent.executor,agent.handoff,agent.next,agent.readTargets, and any returnedagent.sourceChoicesoragent.resultChoicesbefore deciding. - If
agent.executor.decisionisreturn, answer from the referencedreadFrompayload instead of opening a browser. - If a URL follow-up is needed, run the provided
commandArgsone command at a time. - Escalate to browser automation only when
needsBrowserHtml,needsBrowserInteraction, or the executor/handoff fields say it is needed. - Do not run multiple browser-backed checks in parallel.
Inspect a result and open the best match in one step:
ax-grep --search "site:example.com api reference" --open-result best --agentIf an engine rejects best, open the top ranked result directly:
ax-grep --search "site:example.com api reference" --open-result 1 --agentCheck a page for specific terms:
ax-grep "https://example.com/docs" --find "rate limit" --find "authentication" --agentRead static HTML from another tool:
curl -fsSL "https://example.com" | ax-grep --stdin --agentax-grep --agent can expose:
- semantic headings, landmarks, links, buttons, forms, tables, and lists
- source-like links and ranked search choices
- JSON-LD schema facts, metadata, policies, topics, provenance, and citations
- hydration URLs, API endpoints, runtime hints, app config, and mobile hints
- recommended next commands and browser handoff reasons
Treat the full JSON payload as source of truth; top-level shortcuts are for fast routing.