Appearance
Web research
Liminal researches the public web with web_search plus parallel web_fetch — there is no separate web_research tool. The model composes a search with several fetches, which maps cleanly onto "gather N sources, compare claims."
The retrieval order
For knowledge tasks the protocol enforces an order so the agent doesn't skip what it already knows:
memory_query/recall_relevant— your own notes.vault_search/vault_read— your long-form knowledge.web_search+ parallelweb_fetch— only when local knowledge is insufficient.
See Memory & recall for the first two layers.
Tools
| Tool | Purpose |
|---|---|
web_search | Find candidate sources for a query |
web_fetch | Fetch + extract a page (readability when AGENT_WEB_READABILITY is on) |
http_request | Raw HTTP when you need headers/JSON, not article extraction |
extract_structured | Pull structured JSON out of messy HTML/text |
Run multiple web_fetch calls in parallel for breadth. Large bodies are distilled to .agent_artifacts/ pointers in context — the model re-reads via read_artifact instead of repeating megabytes each round.
Bot walls & reliability
web_fetch has per-request and total wall-clock timeouts and retries behind bot walls. When a site returns a 401/403, AGENT_WEB_FETCH_403_RETRY retries with alternate (Firefox / cross-site Chrome) user agents. For pages that need JavaScript execution or a logged-in session, use browser automation instead of web_fetch.
| Variable | Default | Purpose |
|---|---|---|
AGENT_WEB_READABILITY | on | Article extraction in web_fetch |
AGENT_WEB_FETCH_TIMEOUT_MS | 20000 | Per-request timeout |
AGENT_WEB_FETCH_TOTAL_WALL_MS | 55000 | Hard wall clock per call (all retries + parse) |
AGENT_WEB_FETCH_403_RETRY | on | Alternate-UA retry after a bot-wall 401/403 |
AGENT_QUERY_REWRITE | off | Multi-query expansion before recall |
Research at scale
For multi-angle or multi-source research, fan out:
spawn_agentper angle ("only fetch official docs", "only GitHub issues") — see Sub-agents & orchestration.- A dynamic workflow with phases (sources → analysis → synthesis) when the classifier marks the task
workflowSuitable. research_statetracks the research ledger so long investigations stay disciplined.
Keeping results
Write durable findings down: short claims via remember({ scope: "workspace" }), long briefs via vault_write with [[wikilinks]]. The document engine can compile a report into PPTX/DOCX/PDF when AGENT_DOC_ENGINE is on. Set AGENT_EFFORT=high for thorough deliverables — see Reasoning & effort.