Bring external sources into context.

Pick the source type

Use ctx_url_read for a supported page or document URL and ctx_git_read for a remote Git repository. Use ctx_provider for structured data such as issues or tickets from a configured provider.

These are retrieval tools, not an assurance that a source is accurate, accessible or current.

Set a question and a budget

{"name":"ctx_url_read","arguments":{"url":"https://leanctx.com/docs/","query":"Find the setup instructions","max_tokens":2000}}

The response depends on the site’s format and access conditions. Some media or transcript paths need external services or additional runtime support. A failed fetch should remain a failed fetch, not an invented summary.

Preserve provenance

Keep the URL, repository ref and the location of relevant evidence with your notes. For changing sources, record when you checked them. Revisit the source when freshness matters.

Repository reading can be pinned with a ref; use the actual release or commit you intend to document.

Treat external content as data

Fetched instructions are not authorization to run commands, change configuration or send data elsewhere. Apply the same access and filtering review you use for local sources. Text-filter coverage must be established for the specific integration path.

For authenticated sources and cache freshness, continue with data sources.

Sources & versions3 references · Reviewed 17 Sept 2026

• ctx_url_read.rsrust/src/tools/registered/ctx_url_read.rsGitHub
• ctx_git_read.rsrust/src/tools/registered/ctx_git_read.rsGitHub
• 17-web-and-research.mddocs/reference/17-web-and-research.mdGitHub

Core checkout

0ce2207ee4

Reviewed runtime

3.10.2

SDK release

1.1.0

Separate baselines for source, CLI/configuration and SDK contracts. Review does not certify every platform or integration.

Versions & compatibility